Book a call

The same job, in every harness.

Most of what people argue about is naming. Once you know a harness has a memory file, a permission model and a way to run headless, you know what to look for in the next one — this is that mapping, and where we've written the lesson, the cell links to it.

HARNESS COMPARISON
JOBCLAUDE CODECODEX CLIGITHUB COPILOT CLICURSORANTIGRAVITY CLIKIMI CODE CLI
Persistent project instructionsCLAUDE.mdAGENTS.mdAGENTS.md.cursor/rulesGEMINI.md / AGENTS.mdAGENTS.md
Reusable procedure you invoke.claude/skills/.agents/skills/gh skill.cursor/commands/.agents/skills//skill:<name>
External toolsMCPMCPMCPMCPMCPMCP
Delegated sub-sessions.claude/agents/~/.codex/agents/?Subagents.agents/agents//swarm
Draft a plan before writingPlan mode/plan?Plan Mode--mode=plan--plan
Per-tool permission controlallow / ask / denygranular?allow / deny listsallow / ask / deny[[permission.rules]]
OS-level sandboxingSeatbelt / bubblewrapSandbox modes?Sandboxed terminalsTerminal sandbox—
Lifecycle hooksHookshooks.jsonHooks.cursor/hooks.jsonHooks[[hooks]]
Headless / CI runclaude -pcodex exec?cursor-agent -pagy -pkimi -p
Resume a session--resumecodex resume?--resume/resume--continue
Undo / rollback/rewindcodex apply?Checkpoints/rewind/undo
Background / async workAgent View/psCoding agentCloud Agents/tasksBackground tasks
Cost and usage reporting/cost/usage?Usage dashboard/usage/usage

An em-dash means we checked and there's no first-class equivalent we'd point you at — not that the harness can't be made to do it. A question mark means we haven't checked yet.