Extensible harness

Amp

Opinionated hosted agent for local work, durable cloud orbs, and scheduled automation.

Status
Active
License
Proprietary
Evidence
Documented, 21 sources
Product record checked
2026-08-02

At a glance

A proprietary multi-model coding agent with terminal, editor, and web control, non-interactive and runner modes, durable cloud orbs, schedules, event-driven webhooks, live multiplayer threads, MCP, skills, plugins, and built-in or programmable subagents.

Good choice if

  • Hands-off vibe coding in disposable managed cloud orbs
  • Long-running, scheduled, event-triggered, collaborative, or remotely controlled agent work
  • Teams extending one hosted thread system with MCP, skills, plugins, SDK calls, and delegated agents

Check before choosing

  • Local tools run with host privileges and without approval by default; permission plugins or managed policies must be configured explicitly
  • Orbs are paid managed cloud sandboxes, while the SDK's orb executor ignores local-only permission and tool settings in favor of project configuration
  • No harness checkpoint or file rollback was verified; diff review, Git, and durable thread resume are different mechanisms
See 3 more considerations
  • The service is proprietary and not self-hostable, with no documented local open-weight model path
  • Workspace thread visibility and administrator access require deliberate governance for sensitive code and prompts
  • Multiplayer exposes the thread, portal, file changes, and shared terminal to joined workspace members until it expires; webhook URLs are credentials, and event payloads remain untrusted input

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
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
DocumentedBrowser-capable local or managed agent workflowSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Isolated execution
Depends on surfaceManaged cloud orbs; local tools run on the hostSource · checked 2026-07-27The source establishes the mechanism, not its quality or availability in every mode.
Undo file changes
Not documentedNo first-class support established by the current recordAbsence of current documentation is not proof that the capability is impossible.

Getting started

Install the Amp CLI, sign in, then run `amp` locally, `amp -x` for one-shot execution, `amp -ox` in a managed orb, or `amp --no-tui` as a remote runner; add policies before trusting unattended local work.

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.

  • 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 & isolationSandbox availableDocumented mechanism, not a performance score.
  • Tooling & integrationsExtensible + browserDocumented mechanism, not a performance score.
  • Context & statePersistent stateDocumented mechanism, not a performance score.
  • Lifecycle & recoveryManaged recoveryDocumented mechanism, not a performance score.
  • ObservabilityStructured tracesDocumented mechanism, not a performance score.
  • VerificationTool-assistedDocumented mechanism, not a performance score.
  • Governance & permissionsHost accessDocumented 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

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

The public repository is an older supplemental collection of examples and workflow guides with a Markdown lint workflow; it does not expose the proprietary Amp client, durable execution service, orb runtime, or product test suite.

Inspect commit 435ffc0b4d82dfcb083848088411afb44b1ff55f, 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

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.

21 first-party sourcesProduct record checked

Additional first-party sources

21 sources
View 20 more sources