Skip to main content

​
Editing and curating memory

Good memory is short, accurate, and current. Stale memory wastes tokens and can actively mislead the agent. Treat memory like project documentation for Qodex: review it when the product changes, remove old facts, and keep recurring rules in the right file.

​
Review cadence

Review memory after major product changes such as:
  • Auth flow changes.
  • Route or endpoint renames.
  • Role and permission changes.
  • New critical workflows.
  • Large findings cleanup.
  • Major UI redesigns.
Start with business.md and rules.md, then skim the files Qodex writes, api.md and ui.md, and any documents you uploaded.

​
Resolve conflicts

If two memory files disagree, fix one and delete the stale version. Conflicting context is worse than missing context because the agent may follow the wrong one. Common examples:
  • Old auth endpoint in api.md.
  • Test account changed in business.md but not in an uploaded doc.
  • A soft preference should become a hard rule in rules.md.
You cannot edit api.md or ui.md directly. Write the correct fact in business.md or rules.md, which Qodex reads on every turn.

​
Rename or delete a file or folder

Open Knowledge under Context in the left navigation. On the file or folder’s row, click Rename to rename it, or click the Delete (trash) icon and confirm Delete. The built-in files (business.md, rules.md, api.md, and ui.md) and linked-repository overviews cannot be renamed or deleted here.
Deleting a file removes it from the knowledge base permanently. Deleting a folder also deletes everything inside it. Neither action can be undone.

​
Keep entries terse

Write memory as facts, not essays. Bad:
Better:

​
Review rules sources

An uploaded document marked Use as a source of rules is something Qodex may report your software broken against. Turn the setting off for drafts, outdated specs, or documents that describe plans rather than current behavior.

​
Avoid these anti-patterns

  • Storing credentials in memory.
  • Keeping old account details after rotation.
  • Duplicating the same fact across multiple files.
  • Turning memory into a long wiki page.
  • Deleting agent discoveries before checking whether they are still true.

​
Promote recurring rules

If you tell the agent the same instruction repeatedly, add it to memory:
Rules the agent must always obey belong in rules.md. General project facts belong in business.md.

business.md

Edit the main memory file you write.

Memory overview

See every memory file Qodex uses.

How memory works

Learn which files load every turn.

Memory concept overview

Read the short conceptual explanation.