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 files are indexed and read when needed.
Past findings are not copied into memory. When a task needs them, the agent reads the live findings list.
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
Open Knowledge under Context in the left navigation. The page is a file browser for everything Qodex reads: business context, API and UI notes, imported docs, endpoints, and code. Each row shows who wrote it: You, Qodex, Imported, or System. Files Qodex may hold your software to carry a Rules source chip. Use the actions at the top of the page:
Click a folder to open it, or a file to read it. You can edit the files you own, such as
business.md and rules.md. Files Qodex writes, generated code overviews, and uploaded documents are read-only on this page.
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.
Rules sources
business.md and rules.md are always rules sources. An uploaded document is read for context only until you open it and turn on Use as a source of rules. Qodex then treats statements in that document as rules and may report your software broken against them. Click Turn off to go back to context only.
Uploading a new version of a document with different content turns the setting off again, so a rule nobody reviewed never inherits an earlier approval.
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
business.md
Learn what belongs in the main memory file you write.
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.