Working agreements
Keep repository conventions and task boundaries explicit so the next session does not need to guess.
Make decisions, instructions and useful outputs easier to find. Leave the next session with a starting point, not a pile of disconnected tabs.
A code change captures what happened, but not always why it happened or what was intentionally left out. Session history and project artifacts can preserve that missing context.
Qodarium's project memory direction is practical rather than magical: useful instructions, retained conversations, discoverable files and a clear link back to the task. An agent should not be treated as an infallible memory system.
Keep repository conventions and task boundaries explicit so the next session does not need to guess.
Capture the alternatives considered and the reason for an important choice.
Keep plans, notes and results with the project when they will matter after the conversation ends.
Record tests not run, unresolved questions and follow-up work in plain language.
When instructions conflict, the current code and environment must be inspected. Old notes are useful context, not proof that the project still behaves the same way.
The most reusable artifact is often a short, current handoff: the goal, relevant files, verification and next action. Explore the handoff guide for a concrete structure.
No. The architecture direction keeps code and session content on customer infrastructure by default. Exact data flows must be checked for the installed release and enabled integrations.
No. Keep secrets in an appropriate secret-management workflow, outside prompts and shared artifacts wherever possible.
A workspace that holds the context while you focus on what comes next.