project.md
project.md is the main project memory file you control. Qodex reads it on every agent turn so the agent understands your app before it starts testing.
Use it for stable context: what the app does, how auth works, which accounts exist, what to focus on, and what to avoid.
What belongs in project.md
| Section | What to include |
|---|---|
| App overview | What the product does and who uses it. |
| Stack | Frameworks, database, hosting, important services. |
| Test accounts | Emails and roles. Put passwords in environment variables, not memory. |
| Known quirks | Expected behavior that might look broken. |
| Focus areas | Product flows Qodex should test carefully. |
| Skip areas | Routes or actions Qodex should avoid. |
| Team conventions | Rules the agent should respect. |
Example structure
What does not belong
Keep these out ofproject.md:
- Passwords, API keys, tokens, or secrets.
- PII or customer data.
- Long chat transcripts.
- Per-scenario setup steps.
- Large architecture documents that belong in a wiki.
How updates work
Editproject.md from the Knowledge tab. Changes apply on the next agent turn. There is no rebuild step.
Sub-agents get the same project.md context as the main agent, so these facts apply across scenario authoring, review, and verification.
Related
Editing and curating memory
Keep memory small and accurate.
How memory works
Understand prompt loading and on-demand files.
Projects
See how project boundaries scope memory.
Skills
Learn how skills use memory while authoring tests.