Skip to main content

business.md

business.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 business.md

Example structure

What does not belong

Keep these out of business.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

Open Knowledge under Context in the left navigation, click business.md, edit it, and save. Changes apply on the next agent turn. There is no rebuild step. Onboarding seeds a minimal business.md with your project name, target, and focus. Fill in the rest as you go. Sub-agents get the same business.md context as the main agent, so these facts apply across scenario authoring, review, and verification. business.md is a rules source. When Qodex claims your software broke a rule, it can cite what you wrote here. Put hard, always-obey rules in rules.md.

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.