Memory
Memory is the project knowledge Qodex keeps between sessions. It helps the agent remember your app, auth patterns, workflow rules, API behavior, UI behavior, and previous findings. Without memory, the agent would rediscover the same context every time it writes or runs tests.Memory files
| File | Owner | Loaded every turn | Purpose |
|---|---|---|---|
project.md | You | Yes | App overview, stack, accounts, focus areas, and team rules. |
workflow_rules.md | You and agent | Yes | Rules the agent must obey on every run. |
api_behavior.md | Agent | On demand | API patterns and endpoint behavior. |
ui_behavior.md | Agent | On demand | Page behavior and UI observations. |
findings_digest.md | Agent | On demand | Summary of important findings. |
Why memory is markdown
Markdown is editable, inspectable, and easy to curate. Memory is meant to be project documentation for the agent, not an opaque vector database. This makes it easier to answer: “Why did Qodex know this?”What to put in memory
- Stable auth flows and test accounts.
- Routes or pages that need special handling.
- Team rules such as “never run destructive tests on production.”
- Known quirks that look like bugs but are expected.
- Product areas that need extra coverage.
Explore this section
project.md
Learn what belongs in the main user-managed memory file.
Editing and curating memory
Keep memory accurate, compact, and useful.
How memory works
See what is loaded every turn and what is loaded on demand.
Memory concept overview
Read the shorter conceptual intro.