Memory

Memory retains information that remains useful across tasks, such as communication preferences, project background, and recurring collaboration conventions. Open Settings → Memory to display and manage long-term memory stored by Qoder CN on this device.

​

What belongs in memory

Use memory for information that should still be useful in a later task:

• stable development or communication preferences;
• long-lived project background and conventions;
• tools, validation methods, or reference locations used repeatedly.

Keep one-off instructions, temporary debugging state, and the current task's acceptance criteria in the task or project files instead. Memory should not become the only record of a requirement that must be reviewed or versioned.

​

Choose the memory scope

Manage the following two types independently:

• Global memory: Personal preferences, habits, and long-term context used across projects.
• Project memory: Repository rules, experience, and long-term context maintained per project.

You can turn each type on or off independently. The page shows the number of memory files and the latest update time for each group. Use the folder action to inspect its contents or the delete action to remove that memory group. Remove outdated or incorrect information, and do not store passwords, verification codes, API keys, or temporary task state. Turning a memory type off stops Qoder CN from reading or updating it in later tasks; it does not remove the existing files. Use the folder action to review what is stored, and delete a memory group only when you no longer need its contents.

​

Review memory over time

Return to Settings → Memory when Qoder CN repeatedly applies an outdated preference or project assumption. Check the affected global or project memory, remove inaccurate information, then state the corrected requirement in the next task. If a rule must be shared, reviewed, or kept with the repository, store it in the project rather than relying only on personal memory.

​

Choose the right source