77 sources from practitioners, by month and sentiment.
Across the 56 sources that give an opinion the read is strongly positive, led by praise for model routing, result quality, and orbs. Cost is the most discussed concern. Most engineers who compared agents keep Amp as their main agent, and 9 use another.
Positive, mixed and negative sources
42113
The score counts them as 38 positive, 10 mixed and 3 negative votes, one per author. See How the numbers work.
Ran Amp and Claude Code with the same models, repository, and AGENTS.md; Amp was faster, cleaner, and needed fewer fixes, but only its free tier made it affordable.
Published Jan 21, 2026self-described: Professional web development; over 95 percent of their code is AI-generated
Used Amp for a real open-source documentation task that was merged; it fixed a database bug from logs on the first try for US$4.10, though drafts needed trimming.
Published Jul 30, 2025self-described: Open-source documentation task for the Air web framework
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
Ranking AI coding agents on the Every podcast, Klaassen puts Amp in the S tier under Claude Code, saying it is very good at just getting work done, with pretty good ergonomics and good tools already.
"Yes. It's very good at just getting work done. The ergonomics are pretty good, good tools already."
Excerpt, Kieran Klaassen
Published Jun 11, 2025Two-engineer team building Cora, an AI email product at Every, running several coding agents side by side
Practitioner account, self-described; direct use; counts toward Delivered outcomes
Calls Amp the best coding agent used so far and by far the most expensive, at US$15 in two hours. It was the first test where all the tasks got done, yet the author finds the return hard to justify against Claude Code Max at US$100 a month.
"…could be interesting. But I still think I think I still think it's hard to justify this cost compared to like just giving everybody Claude Max, for example, you know, the 5x or even the 10X. Again, I spent $15 in two hours."
2Oracle & Model RoutingAll 14 sources on it praise itWhether Amp's mix of models, the Oracle, the Librarian, and subagents produces better plans and reviews.
Calls Amp an amazing product they love recommending, praising handoff, threads and sharing, and the Oracle. Says people sign up right away once told about the free, ad-supported plan.
Published Feb 11, 2026
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
A co-founder's starter guide for Octoco's senior engineers: keep threads short, plan with the Oracle, hand off phases, and expect cost to grow with long threads.
Published Oct 28, 2025self-described: Octoco, senior engineering staff being introduced to Amp
Practitioner account, self-described; direct use; counts toward Reliability, Operational control, Cost predictability and limits
Built a Ghostty feature with Amp over 16 sessions totalling US$15.98 in token spend, consulting the Oracle for all planning. Guided the agent through cleanup sessions with minor manual changes and merged after a final manual review.
Published Oct 11, 2025self-described: Ghostty, open-source terminal emulator; macOS update notification feature
Practitioner account; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits
Recalls that Amp picked the best model for each task and that its CLI steered users toward good practice, such as replacing a context clear with a handoff.
Published Jul 1, 2026
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
After a month with both Cursor and Amp, uses Amp for refactorings and architectural changes that touch many files, and Deep mode almost exclusively for production work. Runs Amp on a dedicated branch and reviews every commit before merging to main.
Published Feb 7, 2026self-described: Healthcare software work; runs Amp on a dedicated branch
Practitioner account, self-described; direct use; counts toward Delivered outcomes, Reliability, Operational control, Cost predictability and limits, Adoption and upkeep
Recalls that Amp picked the best model for each task and that its CLI steered users toward good practice, such as replacing a context clear with a handoff.
Published Jul 1, 2026
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
Tried Amp as a plugin in Cursor to see if it could beat a Claude Code workflow while adding a photo upload feature live. Had Amp turn existing Claude.md files and Cursor rules into AGENTS.md files and calls the agent really, really smooth and really easy.
"This is nice. And now we have a pages, so we have go to app page. I'm just kind of reviewing the code as it's flying in. So client-side validation type, great. Awesome. I think so it just feels smooth I a…"
Ranking AI coding agents on the Every podcast, Klaassen puts Amp in the S tier under Claude Code, saying it is very good at just getting work done, with pretty good ergonomics and good tools already.
"Yes. It's very good at just getting work done. The ergonomics are pretty good, good tools already."
Excerpt, Kieran Klaassen
Published Jun 11, 2025Two-engineer team building Cora, an AI email product at Every, running several coding agents side by side
Practitioner account, self-described; direct use; counts toward Delivered outcomes
After two weeks on Amp, set up orbs, Claude Code cloud, and Codex cloud side by side. Amp generated its own orb setup scripts and orbs just worked, which he rates well above the other two cloud agents.
"All in all, Amp with Orbs feels significantly above the current state of agents in the cloud, much like the jump from Opus 4.1 to 4.5 from late last year."
Excerpt, Andrei Maxim
Published Aug 3, 2026self-described: Compared Amp orbs with Claude Code and Codex cloud environments on his own projects
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Positive
Mike Hostetler, founder and Elixir agent framework builder
Pointed an orb at his ReqLLM repository: Amp prepared the environment with a skill, made the change, and pushed it to GitHub with permissions in place. His complaints were a large default orb size and a confusing project screen.
"The agent made the requested change, committed the code, and pushed it back to GitHub with the permissions already in place."
Excerpt, Mike Hostetler
Published Jul 20, 2026self-described: Maintains several open-source Elixir repositories, including ReqLLM
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Ran Amp and Claude Code with the same models, repository, and AGENTS.md; Amp was faster, cleaner, and needed fewer fixes, but only its free tier made it affordable.
Published Jan 21, 2026self-described: Professional web development; over 95 percent of their code is AI-generated
Tested Amp Free in the CLI and VS Code extension on a solar panel website, found the free result decent and functional, likes the UI and finds the in-tool ads pretty good. Guesses complex work will still need the paid smart option.
"…this is working. For complex things, I guess you will going to need still the smart option to be enabled. But yeah, you need to add money. I'm curious to see if this uh plan it will work also the free one and the one…"
Moved their company work to orbs to keep agents off their laptop and share running threads, but finds the weakest part is Amp's harness, and the ship button is loose.
"…button, but the ship button just does just injects a prompt. So it can do literally anything you want. And so it says yeah, it just says pull down uh fix any merge issues, you know, push it back up. Uh you don't need to…"
Uses the Amp extension's free daily US$10 for a few Opus 4.5 requests beside their main tool, and dislikes the CLI.
"…run the code. It has two modes. Smart that uses OPUS 4.5, GBT 5.2 and also RAS which uses smaller models like Hiku 4.5. Now, this is super powerful because $10 of free usage every single day means you could use Oppus 4.5 and JP…"
Says Amp had a handoff feature for a while that they found genuinely useful and, anecdotally, felt worked better than compaction, until Amp removed it.
Published Aug 14, 2026self-described: Software engineer in Australia, New Zealand and Fiji
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Calls Amp an amazing product they love recommending, praising handoff, threads and sharing, and the Oracle. Says people sign up right away once told about the free, ad-supported plan.
Published Feb 11, 2026
Practitioner account, pseudonymous; opinion; not counted, repeats a stronger account
Says Amp has consistently impressed them, singling out handoff as a better version of Claude Code's compaction and scoped instructions for complex projects.
Published Nov 10, 2025self-described: Engineering lead for CI/CD and DevOps
Practitioner account; direct use; counts toward Delivered outcomes
Says sharing a whole session globally is the favorite part of Amp, that pull requests with Amp threads attached make Hashimoto very, very happy as a maintainer, and links one from a bug fix that morning.
"PRs with Amp threads attached make me very, very happy as a maintainer."
Excerpt, Mitchell Hashimoto
Published Sep 3, 2025self-described: Maintainer of the Ghostty terminal, reviewing outside pull requests
Practitioner account, pseudonymous; direct use; not counted, takes no position
Recalls that Amp picked the best model for each task and that its CLI steered users toward good practice, such as replacing a context clear with a handoff.
Published Jul 1, 2026
Practitioner account, pseudonymous; direct use; not counted, repeats a stronger account
A co-founder's starter guide for Octoco's senior engineers: keep threads short, plan with the Oracle, hand off phases, and expect cost to grow with long threads.
Published Oct 28, 2025self-described: Octoco, senior engineering staff being introduced to Amp
Practitioner account, self-described; direct use; counts toward Reliability, Operational control, Cost predictability and limits
Built a Ghostty feature with Amp over 16 sessions totalling US$15.98 in token spend, consulting the Oracle for all planning. Guided the agent through cleanup sessions with minor manual changes and merged after a final manual review.
Published Oct 11, 2025self-described: Ghostty, open-source terminal emulator; macOS update notification feature
Practitioner account; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits
Mixed
Independent developer maintaining open-source side projects
Checked Oct 12, 2026.Handoff left with the May 2026 rebuild. Amp now compacts a thread automatically at 90% of its context window, and threads can still read and reference other threads. Praise for handoff describes the earlier product. Amp, Rebuilt
Moved his dev work to the cloud, tried Claude and Amp, and kept Amp because it got his workspace scripted while Claude kept hitting snags. He works across 5 repositories and finds orbs less locked down than a sandbox.
"Stuck with Amp because it was able to help me get my workspace scripted and working well - Claude was close but I just kept hitting random snags."
Excerpt, Taylor Otwell
Published Oct 7, 2026self-described: Laravel product work across 5 repositories with multiple agents
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Adoption and upkeep
Moved their company work to orbs to keep agents off their laptop and share running threads, but finds the weakest part is Amp's harness, and the ship button is loose.
"…button, but the ship button just does just injects a prompt. So it can do literally anything you want. And so it says yeah, it just says pull down uh fix any merge issues, you know, push it back up. Uh you don't need to…"
Is moving most of his project work to Amp orbs and writing custom plugins and infrastructure to manage them, keeping Codex for occasional local work and computer use.
"I think I'm ready to move most of my project work to @AmpCode. I'm even writing some custom plugins and custom infra around it to better manage my orbs the way i need them to work."
Excerpt, Joey Kudish
Published Aug 18, 2026self-described: Independent developer running several products; also uses Codex
Practitioner account, pseudonymous; direct use; counts toward Operational control
Found Amp good but costly in the past. After 4 days on the US$20 plan he gets a lot of value, with one orb working for over 4 days and coordinating with other orbs.
"In just $20 I am getting ton of value. One of my orb is working for over 4 days now and co-coordinating with other orbs…"
Excerpt, Ravindra Barthwal
Published Aug 15, 2026self-described: Has tried Cursor, Devin, Codex, Claude, and other cloud agents
Practitioner account, pseudonymous; direct use; counts toward Reliability
Has used Amp for a while, says Amp "seems to be doing something very similar" to the cloud agent tool being launched, and calls one thread per VM a solid model going forward.
Published Aug 3, 2026
Practitioner account, pseudonymous; direct use; not counted, takes no position
Positive
Andrei Maxim, applied AI engineer and former Ruby developer
After two weeks on Amp, set up orbs, Claude Code cloud, and Codex cloud side by side. Amp generated its own orb setup scripts and orbs just worked, which he rates well above the other two cloud agents.
"All in all, Amp with Orbs feels significantly above the current state of agents in the cloud, much like the jump from Opus 4.1 to 4.5 from late last year."
Excerpt, Andrei Maxim
Published Aug 3, 2026self-described: Compared Amp orbs with Claude Code and Codex cloud environments on his own projects
Practitioner account, pseudonymous; direct use; counts toward Adoption and upkeep
Pointed an orb at his ReqLLM repository: Amp prepared the environment with a skill, made the change, and pushed it to GitHub with permissions in place. His complaints were a large default orb size and a confusing project screen.
"The agent made the requested change, committed the code, and pushed it back to GitHub with the permissions already in place."
Excerpt, Mike Hostetler
Published Jul 20, 2026self-described: Maintains several open-source Elixir repositories, including ReqLLM
Practitioner account, pseudonymous; direct use; counts toward Delivered outcomes, Operational control, Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Orbs bill by the minute, from US$0.08 per hour for a1.tiny to US$2.13 per hour for a1.3xlarge. They pause 5 minutes after the agent stops or 20 minutes after the last interaction, whichever is later. Runners on your own machines cost nothing. Sizes & Costs
Found Amp good but costly in the past. After 4 days on the US$20 plan he gets a lot of value, with one orb working for over 4 days and coordinating with other orbs.
"In just $20 I am getting ton of value. One of my orb is working for over 4 days now and co-coordinating with other orbs…"
Excerpt, Ravindra Barthwal
Published Aug 15, 2026self-described: Has tried Cursor, Devin, Codex, Claude, and other cloud agents
Practitioner account, pseudonymous; direct use; counts toward Reliability
Ran Amp and Claude Code with the same models, repository, and AGENTS.md; Amp was faster, cleaner, and needed fewer fixes, but only its free tier made it affordable.
Published Jan 21, 2026self-described: Professional web development; over 95 percent of their code is AI-generated
Tried Amp a couple of times, spending US$5, then US$10, then US$20, and says it is so expensive they struggle to judge it fairly. Has ChatGPT Pro and is not stingy with paying for useful things, but Amp is past their limit.
Published Dec 8, 2025
Practitioner account, pseudonymous; direct use; not counted, takes no position
Ran Amp and Claude Code with the same models, repository, and AGENTS.md; Amp was faster, cleaner, and needed fewer fixes, but only its free tier made it affordable.
Published Jan 21, 2026self-described: Professional web development; over 95 percent of their code is AI-generated
Tried Amp a couple of times, spending US$5, then US$10, then US$20, and says it is so expensive they struggle to judge it fairly. Has ChatGPT Pro and is not stingy with paying for useful things, but Amp is past their limit.
Published Dec 8, 2025
Practitioner account, pseudonymous; direct use; not counted, takes no position
Calls Amp the best coding agent used so far and by far the most expensive, at US$15 in two hours. It was the first test where all the tasks got done, yet the author finds the return hard to justify against Claude Code Max at US$100 a month.
"…could be interesting. But I still think I think I still think it's hard to justify this cost compared to like just giving everybody Claude Max, for example, you know, the 5x or even the 10X. Again, I spent $15 in two hours."
Stacoviak runs Amp beside Claude Code with a product-manager agent reviewing both, uses Claude Code partly because Amp costs him more, and calls Amp's cost justified.
"...in this case one of them was Amp and the other one was Claude Code, because that one's cheaper for me. You're really expensive, by the way."
Transcript excerpt, Adam Stacoviak, around 52:11 in the episode
Published Sep 17, 2025self-described: Changelog, his own long-running project
Uses the Amp extension's free daily US$10 for a few Opus 4.5 requests beside their main tool, and dislikes the CLI.
"…run the code. It has two modes. Smart that uses OPUS 4.5, GBT 5.2 and also RAS which uses smaller models like Hiku 4.5. Now, this is super powerful because $10 of free usage every single day means you could use Oppus 4.5 and JP…"
Tested Amp Free in the CLI and VS Code extension on a solar panel website, found the free result decent and functional, likes the UI and finds the in-tool ads pretty good. Guesses complex work will still need the paid smart option.
"…this is working. For complex things, I guess you will going to need still the smart option to be enabled. But yeah, you need to add money. I'm curious to see if this uh plan it will work also the free one and the one…"
Found Amp good but costly in the past. After 4 days on the US$20 plan he gets a lot of value, with one orb working for over 4 days and coordinating with other orbs.
"In just $20 I am getting ton of value. One of my orb is working for over 4 days now and co-coordinating with other orbs…"
Excerpt, Ravindra Barthwal
Published Aug 15, 2026self-described: Has tried Cursor, Devin, Codex, Claude, and other cloud agents
Practitioner account, pseudonymous; direct use; counts toward Reliability
A co-founder's starter guide for Octoco's senior engineers: keep threads short, plan with the Oracle, hand off phases, and expect cost to grow with long threads.
Published Oct 28, 2025self-described: Octoco, senior engineering staff being introduced to Amp
Practitioner account, self-described; direct use; counts toward Reliability, Operational control, Cost predictability and limits
Built a Ghostty feature with Amp over 16 sessions totalling US$15.98 in token spend, consulting the Oracle for all planning. Guided the agent through cleanup sessions with minor manual changes and merged after a final manual review.
Published Oct 11, 2025self-described: Ghostty, open-source terminal emulator; macOS update notification feature
Practitioner account; direct use; counts toward Delivered outcomes, Operational control, Cost predictability and limits
Positive
Independent developer and contributor to the Air framework
Used Amp for a real open-source documentation task that was merged; it fixed a database bug from logs on the first try for US$4.10, though drafts needed trimming.
Published Jul 30, 2025self-described: Open-source documentation task for the Air web framework
Practitioner account, self-described; structured test; counts toward Delivered outcomes, Operational control, Cost predictability and limits, Adoption and upkeep
GILD's fact checks, which don't count as sources
Checked Oct 12, 2026.Since September 13, 2026, Hobby is free with your own model keys or linked ChatGPT or Claude subscriptions, with no Amp token fees. Individual (Megawatt) is US$20 per month with orb time and credits. Paid credits use provider API prices with no markup outside Enterprise. Most cost complaints describe 2025 pay-as-you-go pricing. Pricing
Questions the sources split on, with the count on each side.
Evidence remains mixed
Among practitioners who compared agents, does Amp stay their main agent?
119
Amp as main agent, 11 sources
Some keep Amp, or return to it, after trying Claude Code, Codex, and Cursor. They cite results and the feel of the tool.
Another agent as main, 9 sources
Others keep Claude Code, Codex, Devin, or Pi as their main agent. Cost or preference for another tool drives that choice.
Most sources say it is worth it
Is Amp worth what it costs?
83
Worth it, 8 sources
Most sources that weigh price against results say time saved justifies Amp, from pay-per-token use to the US$20 monthly plan.
Not worth it, 3 sources
Others found 2025 pay-as-you-go spend too high against a flat Claude plan.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 6 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
9 sources. These accounts focus on spend as usage spreads, shared threads, and what changes when Amp moves from one engineer to a team.
Individual builders
68 sources. These accounts focus on raw capability, cost per task, and how Amp performs in self-directed development.
All practitioners
77 sources. This gives the broadest market read, but combines work settings that can produce materially different conclusions.
77 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders68 sources, counted here
Emphasizes Results and cost per task
Very small team2 to 10 engineers2 sources, counted here
Emphasizes Orbs and team spend
Professional team11 to 50 engineers, or a named company's team1 sources, counted here
Emphasizes Review practice and workspace controls
Technical leadershipLeaders setting adoption across teams6 sources, counted here
Emphasizes How to introduce Amp and keep threads short
Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Individual builders judge Amp on results, the Oracle, model routing, and task cost. The few team accounts focus on spend per engineer, shared threads, and moving agent runs off laptops onto orbs.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 77 sources. Change group
95 sources for this group, 18 of them documentation
Developer Communities57, 60% of 95 sources
Product Documentation18, 19% of 95 sources
Engineering Blogs & Reviews12, 13% of 95 sources
Podcasts, Talks & Videos8, 8% of 95 sources
Older evidence stays when it still applies. Accounts tied to changed plans, retired features, or earlier model lineups remain in the history with a Needs a recheck label.
Nov 1, 2026: by the owner's decision, a record whose own words state no overall view of Amp now casts no vote; it still counts toward its topics and is listed, and 20 records that counted leave the vote this way. Leaders and teams stay unscored, individual builders stay at +69 and all practitioners move from +68 to +69.
Oct 30, 2026: a second-model check moved Adam Stacoviak's Changelog episode to the worth-it side, since he calls Amp's cost justified while finding it costly, and dated Indeed's tool mix to the talk DX published in June 2026, since DX's page prints no day.
Oct 28, 2026: moved two Hacker News accounts that state their author's role, the CTO of Undo and the founder and CEO of Nuon, from individual builders to leaders and teams, and added the Changelog podcast episode with a timed quote. Leaders and teams hold 9 sources, still under the minimum for a printed score; individual builders move from +73 to +71 on 67, and all practitioners stay at +69 on 76.
GILD's Amp record uses public English-language sources dated 2025 or later. Each source links to the original page and names the author and publication date.
The record covers Amp's retired editor extension, the CLI before and after its May 2026 rebuild, the web app, and orbs. Each account names the interface and plan used.
A page shows a finding when at least 5 sources from 3 different authors discuss it. A disagreement needs at least 2 sources on each side.
Removed features, review burden, and autonomy each have fewer than 5 sources from 3 authors, and Evidence & Methodology lists each with its count. GILD read every source for inconsistent results, self-directed speed, and short threads and found under 5 on each, so a team should measure those on its own repositories during a trial.
GILD checks each documentation link against current pages on ampcode.com.
Oct 25, 2026: added two themes from accounts already collected. Value for Money: 2 say Amp is worth what it costs and 6 say it is not. Needs Close Steering: 1 reports stopping a run that went the wrong way, and 2 discuss supervision without that concern.
Oct 25, 2026: added 8 X posts by named developers and founders, among them Taylor Otwell, Mike Hostetler, and Mitchell Hashimoto. Of these, 7 concern orbs and come from posts Amp links on its homepage. Added Johann Rehberger's independent security test of Amp's file-write permissions.
Method
A running review of what engineering teams report about Amp, from individual builders to engineering leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. On the AI coding agent hubs, each account's overall stance comes from GILD's blind coding: two models from different families read the source's own words without seeing each other's codes, and a third settled where they differed. An account that states no overall view there, such as a bug report, casts no vote and still counts toward its topics. Other hubs count the stance stored on each record. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +69 strong positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Method change, Oct 30, 2026. GILD changed how practitioner sentiment counts, to one vote per author. Under both methods it reads +69 Strong positive. No evidence changed.
Correction, Nov 1, 2026. GILD now takes each account's overall stance from its blind two-model coding, and accounts that state no overall view cast no vote. It read +68 Strong positive and now reads +69 Strong positive.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 3 of 6, individual builders 21 of 50, all practitioners 24 of 56.
Limits
These figures count reviewed public accounts; they do not represent all Amp users. Individual builders supply 50 of the 56 public accounts that take a side. Leaders and teams supply 6, and no theme among them has 5 sources from 3 authors yet. Hacker News supplies 48 sources. 7 of the 9 X posts come from developer posts Amp links on its homepage, so they lean positive. Reddit was not collected. The record excludes Amp's own posts, Amp and Sourcegraph staff comments, and AI-written review sites. Orbs and subscriptions arrived in mid-2026, so fewer accounts cover them than the 2025 product.
Amp used pay-as-you-go credits through 2025. Ad-supported Amp Free launched in October 2025 and closed to new users in February 2026. Editor extensions ended March 5, 2026. Amp rebuilt the CLI in May 2026 and added orbs in June 2026. Low, medium, high, and ultra modes and paid subscriptions arrived in July 2026. Hobby became free with users' own keys and subscriptions on September 13, 2026. Accounts tied to retired plans, the editor extension, handoff, or earlier models carry the Needs a recheck label.
Every count, and the sources behind it
17 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
Threads & Handoff. Handoff left with the May 2026 rebuild. Amp now compacts a thread automatically at 90% of its context window, and threads can still read and reference other threads. Praise for handoff describes the earlier product. Amp, Rebuilt, checked Oct 12, 2026
Orbs & Cloud Agents. Orbs bill by the minute, from US$0.08 per hour for a1.tiny to US$2.13 per hour for a1.3xlarge. They pause 5 minutes after the agent stops or 20 minutes after the last interaction, whichever is later. Runners on your own machines cost nothing. Sizes & Costs, checked Oct 12, 2026
Usage / Cost. Since September 13, 2026, Hobby is free with your own model keys or linked ChatGPT or Claude subscriptions, with no Amp token fees. Individual (Megawatt) is US$20 per month with orb time and credits. Paid credits use provider API prices with no markup outside Enterprise. Most cost complaints describe 2025 pay-as-you-go pricing. Pricing, checked Oct 12, 2026
Autonomy & Permissions. Amp does not ask for approval before tools run. A plugin's tool.call handler can allow, reject, or modify each call. Workspace admins can distribute a global plugin. Tools, checked Oct 12, 2026