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
The always-loaded files stay small and universal. The larger behavior files are indexed and read when needed.
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?”Browse project knowledge
The Knowledge tab gives memory a file-browser style surface. Use it to import product notes, read indexed knowledge, edit project context, and keep testing rules organized by topic. Qodex can search the indexed knowledge when it needs project context, but the source files remain readable so your team can correct or remove anything that is outdated. Use folders for stable areas such as auth, billing, checkout, onboarding, or known limitations. Keep sensitive values out of knowledge even when the file is private to the project.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.