Back to .md Directory

CODEX.md - Agent Entrypoint

Defines the CLI commands and operating conventions for an AI agent to bootstrap and work inside a Decapod-managed repository.

May 2, 2026
0 downloads
0 views
ai agent
View source

What this file does

Defines the CLI commands and operating conventions for an AI agent to bootstrap and work inside a Decapod-managed repository.

When to use it

  • Setting up an agent entrypoint for a Decapod project
  • Establishing a standard agent workflow with workspace and session management
  • Defining agent capabilities and context scoping for task execution
  • Creating a quick-start reference for agent CLI operations

Assumes this stack

RustDockerdecapod CLI

CODEX.md - Agent Entrypoint

You are working in a Decapod-managed repository. See AGENTS.md for the universal contract.

Quick Start

cargo install decapod

decapod validate
decapod docs ingest
decapod session acquire
decapod rpc --op agent.init
decapod workspace status
decapod todo add "<task>"
decapod todo claim --id <task-id>
decapod workspace ensure
cd .decapod/workspaces/<your-worktree>
decapod rpc --op context.resolve

Control-Plane First

decapod capabilities --format json
decapod rpc --op context.scope --params '{"query":"<problem>","limit":8}'
decapod data schema --deterministic

Operating Mode

  • Use Docker git workspaces and execute in .decapod/workspaces/*.
  • Call decapod workspace status at startup and before implementation work.
  • request elevated permissions before Docker/container workspace commands.
  • .decapod files are accessed only via decapod CLI.
  • DECAPOD_SESSION_PASSWORD is required for session-scoped operations.
  • Read canonical router: decapod docs show core/DECAPOD.md.
  • Use shared aptitude memory for human-taught preferences across sessions/providers: decapod data memory add|get (aliases: decapod data aptitude).
  • Operator reference: decapod docs show docs/PLAYBOOK.md.
  • Capability authority: decapod capabilities --format json.
  • Scoped context feature: decapod docs search --query "<problem>" --op <op> or decapod rpc --op context.scope.

Stop if requirements are ambiguous or conflicting.

What's inside

1 quick-start block, 1 control-plane block, 1 operating-mode list with 11 items, 1 stop condition

Change this for your project

  • Replace DecapodLabs/decapod with your own repository name
  • Replace decapod CLI commands with your own tool name if different
  • Replace .decapod/workspaces/<your-worktree> with your actual workspace path pattern

Where it goes

Keep it in your repository where the agent or team that needs it will read it.

Related Documents