Coding agent

Command Code

Terminal-first harness with policy controls, subagents, and checkpoints.

Status
Active
License
Proprietary
Evidence
Documented, 21 sources
Product record checked
2026-07-27

At a glance

A multi-model terminal harness with interactive and headless modes, parallel subagents, MCP, policy-based permissions, worktrees, session checkpoints, hooks, skills, and IDE context integration.

Good choice if

  • Terminal users who need explicit allow, ask, and deny policy rules
  • Parallel exploration and implementation with constrained subagents
  • Headless CI runs that must fail closed instead of waiting for approval

Check before choosing

  • Project path controls and Git worktrees constrain file organization but do not provide an OS security boundary for shell execution
  • Headless editing requires `--yolo`, which enables writes and shell commands together rather than granting a narrow mutation capability
  • Checkpoints are per-session, omit files over 10 MB, and cannot reverse shell or external-service side effects
See 2 more considerations
  • Goal completion is judged inside the product workflow rather than independently replicated evidence; unattended goals still need explicit budget and stop policies
  • Monitors, cron schedules, background commands, and background subagents inherit the host execution boundary unless the user supplies an external sandbox

Why it qualifies as a coding harness

This confirms category fit, not product quality. Every required criterion links back to first-party evidence.

Qualifies4 of 4 required criteria evidenced
  • Adaptive agent loop

    Documented

    The system repeatedly observes results and chooses the next action instead of following a fixed one-pass graph.

  • Repository tool execution

    Documented

    The system can use tools to inspect and change a repository or its execution environment.

  • Task-aware context management

    Documented

    The runtime assembles, updates, compacts, retrieves, or persists task-relevant context while work proceeds.

  • Model-independent runtime control

    Documented

    Permissions, budgets, interruption, policy, or stop controls operate outside the model's own text generation.

Membership establishes category fit only. It does not score quality, safety, autonomy, model capability, or benchmark performance. · Read the membership rule.

How it works under the hood

Seven mechanisms mapped from first-party records. These labels describe what the harness provides, not how intelligent its model is.

7/7layers documented
  • Execution & isolationWorkspace isolationDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible toolsDocumented mechanism, not a performance score.
  • Context & statePersistent stateDocumented mechanism, not a performance score.
  • Lifecycle & recoveryCheckpoint/rewindDocumented mechanism, not a performance score.
  • ObservabilityLogs/transcriptsDocumented mechanism, not a performance score.
  • VerificationTool-assistedDocumented mechanism, not a performance score.
  • Governance & permissionsPolicy controlsDocumented mechanism, not a performance score.

Public code audit

Unrankedsupport-only repository
Security policy
Not found
CI workflow
Not found
Automated tests
Not found
Evaluation assets
Not found
Contributor documentation
Present at inspected commit

The public tree contains a product readme, documentation links, and issue configuration but no tags, core agent implementation, CI workflow, tests, security policy, or evaluation suite. The shipped npm package therefore cannot be source-audited from this repository.

Inspect commit a774fe8cbe71697d115d4660de299c9c1b286cea, checked 2026-07-27

Measured configurations

No benchmark run passes the full metadata admission policy for this harness yet. Missing data is not scored as zero.

Benchmark policy and all runs

Capability support

Documented first-class product support, checked against the sources below.

External tools (MCP)
DocumentedProduct-supported MCP integrationSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Local models
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Agent parallelism
DocumentedDelegated or parallel agent workflowSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Runs without an open UI
DocumentedNon-interactive or automation surfaceSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Browser control
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Isolated execution
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Undo file changes
DocumentedProduct-supported file or session rollbackSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.

Primary evidence

Each capability claim is tied to a first-party record and a verification date.

Product record checked 2026-07-27
View 13 additional sources
Product and interfaces1 sources
Execution and control2 sources
Agents, state and recovery4 sources
Automation and extensions2 sources
Enterprise and operations2 sources
Releases and public code audit2 sources

Ecosystem discovery

OpenRouter coding apps Discovery signal only; usage rank is not used as a quality or capability score. Observed 2026-07-27.