Amp review

Amp is an AI coding agent and development environment built around work that can continue beyond a single active session. Amp says its agents can keep working after you close your laptop, then let you pick up the thread from your phone or share it with teammates. That makes it more than a prompt-and-response coding assistant: the pitch is an agent that can stay involved across longer development tasks.

Amp describes a workflow where agents can run tests, rebase changes, ship to main, and monitor rollouts. You can also send a screen recording or dictate a prompt, and schedule agents to wake up and check production. Those are product capabilities, not guarantees that an agent can safely complete every task without review. The practical fit depends on whether you want persistent agent work and are comfortable supervising what it changes and ships.

The clearest advantage is continuity. If an agent can keep working while your laptop is closed, and you can resume from a phone or share a thread with teammates, the work is less tied to one developer’s open editor. Scheduled checks and rollout monitoring also suit tasks that need follow-up after code is written, rather than another round of manual prompting.

Amp’s listed capabilities cover several steps in a development workflow: multimedia prompts, test runs, rebasing, shipping changes to main, and production monitoring. We’d treat that breadth as useful when evaluating it, while still checking what review and approval controls your team needs before allowing changes to ship.

The entry point is inexpensive if your work can use self-hosted orbs. According to the pricing page, Hobby costs $0 per month and includes unlimited self-hosted orbs, free use of your own runners, and no Amp token fees or limits. Individual is $20 per month and includes 45,000 minutes of Amp-hosted orb time, plus unlimited self-hosted orbs and bring-your-own-key support. Teams can share threads, tools, billing, and pooled credits at no extra charge.

The main pricing catch is hosted usage. Hobby includes pay-as-you-go Amp-hosted orbs, but the pricing page does not publish their rates. That makes the free plan’s actual cost hard to forecast if you need hosted capacity. Individual is more specific at $20 per month for 45,000 minutes of Amp-hosted orb time; the page does not state what happens if you need more. Annual billing prices are not published either.

The $0 Teams price should not be read as unlimited agent usage. Teams can share billing and pooled credits, while members use Hobby, Megawatt, or Gigawatt tiers; the published pricing details do not give credit amounts or those tiers’ prices. Enterprise pricing is custom, with pooled credits only and no paid user seats, but the price and higher quota levels are not published. Before switching, confirm hosted-orb rates, credit rules, and any usage limits that apply to your intended tier. The advertised workflow is broad, but the published details do not specify how much human approval is required before shipping changes.

Amp’s listed entry price is $0 for Hobby. Individual costs $20 per month and includes 45,000 minutes of Amp-hosted orb time. That is the clearest paid step up, but it is not the only option: Hobby includes unlimited self-hosted orbs and lets you use your own runners for free. Hosted orbs on Hobby are pay-as-you-go, and their rates are not published, so the free plan does not guarantee a predictable bill.

Teams is listed at no extra charge for teams of any size, with shared billing and pooled credits; members can use Hobby, Megawatt, or Gigawatt tiers. Enterprise pricing is custom. Its page lists monthly prices but does not publish annual rates. Before choosing a plan, check how your hosted usage and pooled credits will be billed: Amp does not publish hosted-orb add-on rates. The $20 Individual plan includes bring-your-own keys, unlimited repositories, and hosted minutes; the page does not list a paid-user-seat charge for Teams.

The published product information does not describe a migration tool, supported imports, or a data-export format. Before moving active work into Amp, confirm whether you can export threads, agent context, and any generated changes in a form you can use elsewhere. Those details are not published in the material we have, so we can’t judge how much effort a switch would take or how portable your work will be.

Amp is aimed at persistent coding work: agents can keep working after you close your laptop, and you can continue from your phone or share work with teammates. That may make its thread-sharing, billing, and hosted-orb setup part of a team’s workflow; check the export and handoff options before depending on them. The published sources contain no Reddit posts or comments, so we can’t responsibly say what tends to make users leave Amp based on Reddit. The practical reasons to investigate are the unpublished hosted-orb rates and whether the data and workflows you need can move with you.