HarnessMatch

Search 73 product records by name, workflow, interface, or documented capability.

Quick access
Use ↑ ↓ to move, Enter to open, Esc to close.

Quick access links shown.

Menu

Coding agent

Zoo Code

Roo successor for controlled, model-agnostic coding inside VS Code.

Status
Active
License
Apache-2.0
Evidence
Documented + code-verifiable, 28 sources
Product record checked
2026-08-10
Compare harnessesInspect sources

At a glance

An Apache-licensed VS Code agent continuing the Roo Code lineage, with broad provider and subscription access, local models, custom modes, hierarchical subtasks, MCP, semantic indexing, worktree workflows, task history, and shadow-Git file checkpoints.

Good choice if

  • Vibe coders who want proposed tools and diffs visible in VS Code before they run
  • Roo Code users who need a maintained migration path with compatible settings and task history
  • Model-agnostic IDE workflows using modes, MCP, local models, semantic indexing, subtasks, and worktrees

Check before choosing

  • Commands and file tools run with the local user's host permissions; worktrees and .rooignore scope work but are not an OS or container sandbox
  • Extension actions ask by default, but auto-approval can be enabled and sending a queued message implicitly approves the next pending tool, file, or command action even when auto-approval is disabled
  • The 3.76 Destructive Command Guard is an opt-in command filter rather than process isolation; it can reduce repeated prompts for recognized safe commands but does not turn host execution into a sandbox
See 5 more considerations
  • Shadow-Git checkpoints restore task-scoped file state and are enabled by default, but they are not created before commands and cannot reverse external command side effects
  • The new_task tool suspends the parent and opens one child as the sole active task; simultaneous work instead uses separate user-managed VS Code windows and Git worktrees, not an automatically parallel delegated swarm
  • The public website says Zoo works headless, but the inspected CLI package is private, still uses Roo names and upstream Roo install URLs, and has no Zoo-owned CLI release asset; it is not counted as a dependable public CI interface
  • No built-in browser controller was found in the tool registry; web access depends on a browsing-capable provider or an external Playwright or Puppeteer MCP server
  • The repository has extensive engineering and end-to-end tests but no coding-harness evaluation suite, independent benchmark, or direct scientific paper; inherited release-note model scores are not Zoo Code harness evidence

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.
Reusable skills
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
Local models
DocumentedLocal or self-hosted model pathSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
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
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.
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.

Getting started

Install the Zoo Code VS Code extension, migrate or configure provider profiles, choose a mode, and review approvals, .rooignore, checkpoint, index, MCP, and worktree settings before granting broader tool access.

Open official documentation

Classification and operating model

Category fit and technical mechanisms are evidence records, not product-quality scores.

Category fit
Qualifies, 4/4 criteria
Operating model
7/7 layers documented
Inspect category criteria and operating mechanismsFirst-party records

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.

    EvidenceZoo Code documentation overview

  • Repository tool execution

    Documented

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

    EvidenceTool workflow

  • Task-aware context management

    Documented

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

    EvidenceCodebase indexing

  • Model-independent runtime control

    Documented

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

    EvidenceAuto-approval policy at inspected commit

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 & stateManaged contextDocumented 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 & permissionsApproval promptsDocumented mechanism, not a performance score.

Measured and public context

Configuration-specific measurements and source-native activity stay separate from general product capability.

Inspect code audit, measured configurations, and ecosystem signalsContext, not a product score

Public code audit

4/5public artifacts present
Security policy
Present at inspected commit
CI workflow
Present at inspected commit
Automated tests
Present at inspected commit
Evaluation assets
Not found
Contributor documentation
Present at inspected commit

The repository contains 754 unit, integration, and end-to-end test files, but no coding-harness evaluation suite or independent benchmark. CONTRIBUTING describes evals as a future goal; the source CLI remains private and Roo-branded despite a public headless claim.

Inspect commit d27153a251d2051b6a8e73d305b06ffbc5ac6970, 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
Context, not quality

Public ecosystem signals

Source-native observations for exact mapped artifacts and reviewed stable release trains. Different units and populations stay separate, and missing coverage is never treated as zero.

View this harness in Usage
  • Latest stable releasev3.82.0Released 2026-09-05; 13 stable releases in 90 daysOpen release
  • Release asset downloads2.16K20 stable releases; 20 matched assetsOpen artifact
  • VS Code installs85.5KExtension: ZooCodeOrganization.zoo-codeOpen artifact
  • Open VSX downloads129.43KExtension: ZooCodeOrganization/zoo-code; latest 3.83.100460Open artifact
  • GitHub stars1.81KFull-source repository; 269 forksOpen artifact

Routing, package retrievals, release downloads, editor installs, and repository interest observe different populations. They are never added together and never affect capability evidence, classification, or measured results.

Interpretation rulesSignals checked

First-party evidence

Each capability claim links to the first-party record that supports it.

28 first-party sourcesProduct record checked

Execution and control

1 source

Additional first-party sources

27 sources
View 26 more sources

Ecosystem context

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