Skip to content

Tool map: Claude Code, Cursor, and Codex

The tool map keeps intent.md, spec.md, plan.md, verification evidence, review findings, and incident records portable across Claude Code, Cursor, and Codex. The lifecycle and human gates remain identical; only the harness surface changes. Use the table to choose an implementation without duplicating or weakening the canonical stage procedure.

Commands and product surfaces were checked on 4 September 2026 against the installed CLIs and official vendor documentation. Model names and prices are deliberately absent: route by evaluated task quality, latency, and completed-work cost, then check the current picker or vendor pricing page.

PlayClaude CodeCursorCodex
Capture intentInteractive repository session or Claude web surface; commit the reviewed intent.mdAsk mode for discovery; Agent mode to save the accepted fileInteractive /plan or app chat; commit the reviewed intent.md
Spec from intentProject skills in .claude/skills/ plus repository context in CLAUDE.mdProject skills in .cursor/skills/ or .agents/skills/; rules in .cursor/rules/*.mdcProject skills in .agents/skills/; repository guidance in AGENTS.md
UI evidenceImage input, browser or design MCP chosen by the teamImage input, browser tools, or Figma MCP chosen by the teamImage input, browser/computer use, or an approved MCP tool
Plan before build--permission-mode plan, /plan, or Shift+Tab; save the accepted plan in the repoPlan mode in IDE or cursor-agent --plan; save the accepted plan in the repo/plan before the active run; save the accepted plan in the repo
Parallel isolationclaude -w NAME or explicit Git worktreesAgents Window worktrees, /worktree, /best-of-n, or explicit Git worktreesWorktree in the desktop app or explicit Git worktrees; no CLI --worktree flag in 0.146.0
Deterministic controlsHooks in .claude/settings.json with scripts under .claude/hooks/; permission modesProject or enterprise hooks, sandboxing, rules, and worktree setupHooks in .codex/hooks.json or config.toml; sandbox and approval policy
Session feedbackCommands in CLAUDE.md; tests, builds, browser and screenshotsCommands in rules; terminal, browser, checkpoints, screenshotsCommands in AGENTS.md; tests, terminal, browser and screenshots
Non-interactive runclaude -p with explicit permission and output formatcursor-agent --print with sandbox and output formatcodex exec with explicit sandbox; --json or --output-schema when needed
Pull-request reviewManaged Code Review or claude-code-actionBugbot on the PR; /review and /review-bugbot on supported surfacescodex review locally or openai/codex-action@v1 in CI
Background workBackground sessions, routines, CI schedules, or the Agent SDKCloud Agents and AutomationsApp scheduled tasks, cloud tasks, CI schedules, Slack or Linear intake
Production authorityExternal release gate and credentials unavailable to the agentExternal release gate and credentials unavailable to the agentExternal release gate and credentials unavailable to the agent
Terminal window
# Claude Code 2.1.258
claude --permission-mode plan
claude -w feature-slug
claude -p --output-format json "Review the current diff."
# Cursor Agent 2026.01.28-fd13201
cursor-agent --plan "Propose an implementation plan."
cursor-agent --print --sandbox enabled --output-format json "Review the current diff."
# Codex CLI 0.146.0
codex
# Then enter /plan before the agent starts working.
codex review --uncommitted
codex exec --sandbox workspace-write --json "Run the documented checks."

Verify against the local installation before automation:

Terminal window
claude --version && claude --help
cursor-agent --version && cursor-agent --help
codex --version && codex --help
codex exec --help
codex review --help

A vendor has no equivalent control. Keep the control in Git, CI, identity, or the deployment platform. Do not rename an advisory prompt and present it as enforcement.

A copied CLI flag fails. Compare the command with the installed --help output and the dated verification note above. Update both language versions and the relevant adapter.

A tool-specific artifact becomes the only source of truth. Copy the accepted result into the repository or explicitly link the authoritative external record and commit SHA.

Start with the artifact chain, adopt the sequence through Plan, and measure it with SDLC metrics.