RAAV Logo
Paste this to your coding agent

One codebase. Many agents. One shared memory.

RAAV gives Claude Code, Codex, Cursor, and other coding agents the same project memory, task queue, file claims, run history, and decisions. It makes agents coordinate before they edit.

RAAV is not a coding agent and does not spend LLM tokens by default. Your coding agent does the reasoning; RAAV stores the shared memory, workflow, claims, and audit trail.

Pick your agentView memory console

What RAAV creates

  • .raav/config.json
  • Shared memory ledger
  • Tasks, tickets, and file claims
  • Branch/worktree swimlanes
  • Runs, events, decisions, and verification
  • AGENTS.md, CLAUDE.md, Cursor and Copilot rules

Paste the setup prompt

Use Claude Code, Codex, Cursor, or another MCP-capable coding agent. The agent initializes RAAV from inside the repo.

Workflows guide the agent

Onboarding, planning, start-work, handoff, review, and release-check prompts keep the founder experience consistent.

Agents share one state

RAAV writes local project memory, tasks, claims, events, decisions, verification status, and agent instructions.

Work without collisions

Each agent claims tasks and files before editing, then submits results into the same project ledger.

Founder sees what matters

The brief turns scattered agent work into next tasks, launch blockers, conflicts, and decisions.

Choose the agent you use.

Paste the matching prompt into your coding agent. RAAV will make that agent read the same memory, claims, tasks, and decisions as every other agent on the repo.

Claude Code prompt
Claude Code: set up RAAV in this repository before editing code.

RAAV is persistent product and project memory for coding agents. You provide the reasoning and coding. RAAV provides memory, workflows, tasks, lanes, claims, decisions, and audit trail.

Please:
1. Run `raav status` from the repository root.
2. If RAAV is missing, install it with `npm install -g raav-cli`.
3. If RAAV is not initialized, run `raav init`.
4. Run `raav sync-instructions`.
5. Run `raav overview`.
6. Run `raav product`.
7. Run `raav product handbook`.
8. Run `raav workflow show onboard-and-plan --agent claude` and follow it to draft product memory and backlog task proposals for founder confirmation.
9. Run `raav doctor` and `raav repair` if setup health reports issues.
10. Run `raav guide` to confirm setup gaps are resolved.
11. Run `raav lanes`.
12. Run `raav lane brief --agent claude_code`.
13. Run `raav next --agent claude_code` and report the top task.
14. Do not edit product code until you have claimed a task.
15. Tell me the product brief, confirmed facts, assumptions, open founder questions, next task, branch/worktree lanes, current risks, active claims, and any setup issues.
Setup prompt
Set up RAAV in this repository.

RAAV is not a coding agent. It is persistent product and project memory for AI coding agents. You provide the reasoning and coding. RAAV provides memory, workflows, tasks, lanes, claims, decisions, and audit trail.

Please:
0. If the founder does not have a RAAV account yet, send them to https://raav.ai/signup?plan=local&next=/cli/connect.
   After signup, link this machine with `raav login` using the token from https://raav.ai/cli/connect.
1. Check whether the RAAV CLI is available by running `raav status`.
   If it is missing, install it with `npm install -g raav-cli`.
2. If RAAV is not initialized, run `raav init`.
3. Run `raav sync-instructions` so every agent gets the same project rules.
4. Run `raav overview` to get the founder-readable project snapshot.
5. Run `raav product` to inspect product brief, goals, requirements, epics, and releases.
6. Run `raav product handbook` to read the founder-facing Product Handbook.
7. Run `raav workflow show onboard-and-plan --agent <your-agent-name>` and follow it to draft product memory and backlog task proposals for founder confirmation.
8. Run `raav doctor` and `raav repair` if setup health reports issues.
9. Run `raav guide` to confirm setup gaps are resolved.
10. Run `raav lanes` to inspect active branches and worktrees.
11. Run `raav lane brief --agent <your-agent-name>`.
12. Run `raav next --agent <your-agent-name>` and report the top task.
13. Do not change product code yet.
14. Tell me:
   - what RAAV knows about the project
   - what RAAV knows about the product
   - what is confirmed, inferred, and still needs founder review
   - the top active risks
   - which branch/worktree lanes exist
   - the next recommended task
   - whether another agent has claimed conflicting files
Agent working rules
Before editing this repository, use RAAV as shared memory.

Follow this workflow:
1. Run `raav overview`.
2. Run `raav product`.
3. Run `raav product handbook`.
4. Run `raav workflow show start-work --agent <your-agent-name>`.
5. Run `raav lane brief --agent <your-agent-name>`.
6. Pick a task with `raav next` or ask me which task to create.
7. Initialize or update the lane:
   `raav lane init --branch <branch> --owner <your-agent-name> --goal "<goal>"`
8. Claim the task before editing:
   `raav claim <task-id> --agent <your-agent-name> --files <file1,file2> --branch <branch>`
9. If RAAV reports conflicting claims or lane risks, stop and ask me before editing those files.
10. After the work, run relevant verification commands.
11. Run `raav workflow show handoff-work --agent <your-agent-name>`.
12. Submit the result:
   `raav submit <task-id> --agent <your-agent-name> --status completed --summary "<what changed>" --files <file1,file2> --branch <branch>`
13. Attach durable facts as memory candidates with `raav submit <task-id> --candidate "workflow:<fact>"`.
14. Propose product or architecture decisions with `raav propose decision --text "<decision>"` for founder confirmation.

Rules every agent should follow

  • Read RAAV context before editing.
  • Use RAAV Workflows for onboarding, planning, work, handoff, review, and release checks.
  • Claim tasks and files before changing them.
  • Avoid files claimed by another active agent.
  • Submit every result back into RAAV.
  • Attach durable facts as memory candidates for founder promotion.
  • Propose product and architecture decisions for founder confirmation.
  • Run verification before calling work complete.

RAAV Workflows

onboard-and-plan

Seed product memory, V1 plan, and backlog tasks in one agent pass.

onboard-product

Create a Product Handbook draft from repo context.

plan-v1

Turn product memory into requirements, epics, tasks, and release criteria.

start-work

Read context, check lanes, claim files, then begin.

handoff-work

Submit summary, verification, risks, and next action.

review-work

Explain whether completed work is safe and what needs review.

release-check

Check CI, package, docs, security, and launch blockers.

explain-project

Explain the current product/project state to the founder.

CLI reference
npm install -g raav-cli
raav install-agent --agent codex
raav init
raav status
raav overview
raav product
raav product handbook
raav workflow list
raav workflow show onboard-and-plan --agent codex
raav workflow show onboard-product --agent codex
raav workflow show plan-v1 --agent codex
raav workflow show start-work --agent codex
raav workflow show handoff-work --agent codex
raav propose brief --icp "Non-coding solo founders" --problem "Agents lose product context" --promise "Every agent gets the same product truth" --source codex --review-status inferred --confidence 0.7 --assumptions "Founder is using coding agents today" --unknowns "Final team packaging" --agent codex
raav propose goal --id GOAL-001 --title "Ship Product OS V1" --status active --priority critical --metric "Founder can coordinate two agents"
raav propose milestone --id MILE-001 --title "Agent PM V1" --goal-ids GOAL-001 --target-date 2026-07-01
raav propose requirement --id REQ-001 --title "Product brief appears in every agent brief" --type ux --criteria "Agent brief includes ICP,promise,goals"
raav propose epic --id EPIC-001 --title "Founder Product OS" --requirement-ids REQ-001 --branch feature/product-os
raav propose release --id REL-001 --title "Product OS V1" --version v1 --epic-ids EPIC-001 --verification-status unknown
raav review proposals
raav confirm PROP-001 --agent founder
raav doctor
raav repair
raav audit export
raav guide
raav guide --write-tasks
raav lanes
raav lanes feature/install
raav lane init --branch feature/install --owner codex --goal "Improve install flow" --ticket-id RAAV-12
raav lane brief --branch feature/install --agent codex
raav ticket add RAAV-12 --title "Fix onboarding" --tasks TASK-001 --branch feature/install --owner codex
raav ticket status RAAV-12
raav brief --agent codex
raav next
raav propose task --title "Fix onboarding" --description "Make first-run setup reliable" --priority HIGH --files apps/web/app/install/page.js --branch feature/install --ticket-id RAAV-12 --criteria "Install page explains proposal-first workflow"
raav claim TASK-001 --agent codex --files apps/web/app/install/page.js --branch feature/install
raav conflicts apps/web/app/install/page.js
raav submit TASK-001 --agent codex --status completed --summary "Added install page" --files apps/web/app/install/page.js --branch feature/install --candidate "workflow:The install page is the primary onboarding surface."
raav lane close --branch feature/install --merged
raav propose decision --text "RAAV stays a neutral memory layer, not a coding agent."
raav events --limit 20