> ## Documentation Index
> Fetch the complete documentation index at: https://qodex.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# business.md

> business.md is the project memory file you write and Qodex reads on every agent turn. Learn what to store there and how to maintain it.

# 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

| 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

```markdown theme={null}
# Project

## App overview

Qodex is an autonomous AI QA platform. Customers run it against their APIs
and web apps to find bugs before they ship.

## Stack

- Frontend: React + Vite
- Backend: Node.js + Hono
- Database: Postgres

## Test accounts

- Admin: admin@example.com, password from AUTH_PASSWORD
- Member: member@example.com
- Viewer: viewer@example.com

## Known quirks

- The dashboard can take a few seconds to warm up after deploy.
- /admin/reset is destructive. Never test it outside local dev.

## Focus areas

- PR review walkthroughs.
- Scenario authoring across API and UI.
```

## 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`.

## Related

> [card] [Editing and curating memory](https://qodex.ai/docs/memory-editing-and-curating.md)
>
> Keep memory small and accurate.

> [card] [How memory works](https://qodex.ai/docs/kb-how-memory-works.md)
>
> Understand prompt loading and on-demand files.

> [card] [Projects](https://qodex.ai/docs/concepts-projects.md)
>
> See how project boundaries scope memory.

> [card] [Skills](https://qodex.ai/docs/concepts-skills.md)
>
> Learn how skills use memory while authoring tests.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.