Skip to main content

Decision brief

Amp Review: The Coding Agent That Moved Into Orbs

Pilot Amp with teams that hand whole tasks to cloud machines. The US$20 plan, orb minutes, and controls sold only on Enterprise set what it costs.

Reading time
3 min read
Sources
25 cited

GILD verdict

Pilot Amp if engineers will run several agents at once on cloud machines and review the finished work.

Roll it out wider once a workspace plugin controls what agents run and every project ships to a branch.

Amp

AI Coding Agent by Amp Frontier Corporation

+69 Strong positive
Product page

Fit and limits

Who it fits

  • Engineers want to start agents, close the laptop, and follow each thread from the web or a phone.
  • You want Amp to pick and pair models per task, with a second model, the Oracle, checking plans and reviews.
  • You want to choose who pays for tokens through Model Routing, with Amp credits at API prices, provider keys, or linked ChatGPT and Claude plans.
  • Your team works in the terminal or the browser and does not need the agent inside an IDE.

Where it falls short

  • Amp runs tools without approval by default. Gating them takes a plugin your team writes and maintains.
  • Per-user spend limits, SCIM, model allowlists, and authentication audit logs are Enterprise features.
  • Amp has had no editor extension since March 5, 2026, and sells no self-hosted deployment. Self-hosted orbs, added October 22, 2026, run on your compute and connect back to their threads on ampcode.com.
  • Amp retires features it stops using, including the editor extension, handoff, and Amp Free. When four new modes replaced smart, deep, rush, and large on July 9, 2026, Amp shipped the old modes as plugins a team can reinstall.

Implementation reality

  1. Gate tool calls before the first thread

    Write a tool.call plugin that allows, rejects, or modifies calls by command and path, and have an admin distribute it workspace-wide. Add amp.mcpPermissions rules for MCP servers, and enforce an MCP registry on Enterprise.

  2. Set Ship Behavior per project

    The default Ship button commits, rebases, runs tests, and pushes to the base branch. If the team merges through pull requests, set Ship Behavior to Push to Branch, which reports the pull request URL, or write a custom ship prompt.

  3. Decide whose tokens pay

    Pick Amp credits or provider keys as the default payer. Linked ChatGPT plans cover OpenAI roles, and Claude plans cover Claude Code mode. Check the training and retention terms of any linked personal plan. Enterprise can forbid personal keys to enforce one routing policy.

  4. Budget orbs and modes

    Set the default orb size and a mode policy before rollout. Orbs bill by the minute. Projects default to a1.medium at US$0.33 per hour, and personal projects on Megawatt default to a1.small at US$0.17. Your own runners cost nothing. Amp reports that self-hosted orbs are free for individuals and teams, and Enterprises pay standard orb pricing for them from October 29, 2026. A thread keeps its starting mode. Use low for small fixes and medium by default, and save high or ultra for costly misses.

  5. Write AGENTS.md once

    Keep shared instructions in a versioned AGENTS.md. Amp reads it in the working directory, its parents, and subtrees, plus a workspace file an admin sets. Where no AGENTS.md exists, Amp reads CLAUDE.md, so one file serves Amp and Claude Code.

What to measure in your pilot

  • GILD found no public team bill on the July 2026 subscriptions or September 2026 free tier; log amp usage --details per engineer weekly, and price Enterprise if one engineer doubles the median.
  • Amp publishes no roadmap for orbs, runners, or modes past 2026; list which ones your workflow depends on and check Amp's news page for retirements before each quarterly renewal.
  • Westpac's August 2026 release sets a goal of delivering in weeks and reports no results yet; measure your own ticket-to-merge time before and during the pilot.

Sources

Official documentation
24
Public source
1
  1. Amp pricingOfficial documentationampcode.com
  2. Amp docs: PricingOfficial documentationampcode.com
  3. Amp docs: Orb sizes & costsOfficial documentationampcode.com
  4. Amp: Modes & modelsOfficial documentationampcode.com
  5. Amp docs: The DialOfficial documentationampcode.com
  6. Amp docs: IntroductionOfficial documentationampcode.com
  7. Amp docs: OrbsOfficial documentationampcode.com
  8. Amp docs: CLIOfficial documentationampcode.com
  9. Amp docs: ToolsOfficial documentationampcode.com
  10. Amp docs: PluginsOfficial documentationampcode.com
  11. Amp docs: CLI configurationOfficial documentationampcode.com
  12. Amp docs: Shipping changesOfficial documentationampcode.com
  13. Amp docs: Model routingOfficial documentationampcode.com
  14. Amp docs: AGENTS.mdOfficial documentationampcode.com
  15. Amp docs: WorkspacesOfficial documentationampcode.com
  16. Amp docs: Workspace entitlementsOfficial documentationampcode.com
  17. Amp security referenceOfficial documentationampcode.com
  18. Amp news: The Coding Agent Is Dead (Feb 19, 2026)Official documentationampcode.com
  19. Amp news: Amp Frontier Corporation (Dec 2, 2025)Official documentationampcode.com
  20. Amp news: Free Agent (Sep 13, 2026)Official documentationampcode.com
  21. Amp news: The Dial (Jul 9, 2026)Official documentationampcode.com
  22. Amp news: Banking on the Frontier (Jul 29, 2026)Official documentationampcode.com
  23. Westpac: Westpac and Amp Frontier to partner on AI engineering (Aug 7, 2026)Public sourcewestpac.com.au
  24. Amp news: Self-Hosted Orbs (Oct 22, 2026)Official documentationampcode.com
  25. Amp news: Explain Usage (Aug 21, 2026)Official documentationampcode.com