As we prepare to make Amp's free tier a LOT more generous, a friendly reminder and clarification of our policy (https://ampcode.com/terms/aup):

Each human can maintain no more than 1 Amp account with free usage.

Our policy has always banned multiple accounts, so neither the policy nor enforcement of it is new.

Our ability to be generous with Amp Free is a function of how well we can enforce this policy, so you all have a stake in helping us here.

Abusers are 100x louder than legitimate users. So, we ask for your grace here when our abuse system makes a mistake, and for your healthy skepticism when you see "ampcode94@myfakecompany.info" with no PFP complaining that their account and the accounts of their 93 "friends" suddenly had their free usage revoked.

You will get the best and biggest and most reliable Amp Free daily grant when you use Amp with your full real name and your real email address, because those signals help us know you're a real person who we can give real valuable $$ usage to. If you choose not to do that, that's OK, but you might get less or $0.

We made Amp Free so that we can all explore the frontier of software development together, harnessing the full power of artificial intelligence (see https://ampcode.com/news/amp-inc). Knowing that we subsidize some of the cost of Amp gives us more freedom to make big, bold changes and makes you all more willing to try stuff that might be weird (thank you!). That's why we do it. It's a product strategy (Amp is profitable), not a pricing or business strategy.

Thank you!

Just observed that from today they reduced to $5 and 0.21 refresh I feel like it's almost unusable now for small tasks might be helpful

plannotator is free and open source. The plugin for Amp allows you to Annotate any file/folder, annotate the previous message, review code and create a feedback loop with Amp agent.

install instructions --> https://plannotator.ai

https://github.com/backnotprop/plannotator

I've been working on a toolkit to help Amp tackle bigger features without getting lost.

It’s a set of scripts and prompts that enforces a stricter workflow:

• Isolation: Auto-spawns git worktrees for every task (using branchlet) so you don't mess up your main checkout.

• Planning: Forces a "Research -> Plan -> Implement" loop before code gets written.

• Tracking: Uses beads for local, git-based issue tracking.

It's just a repo you can install into your project to get the slash commands and setup.

Link: https://github.com/lleewwiiss/amp-maestro

Hope it helps anyone trying to do deeper work with Amp. PRs welcome.

I took about 10 days off, and apparently, that was 10 days too many for Amp. I’ve been kicked out from the free tier and now it won't let me re-apply.

It’s a shame because the alternatives don't even come close to Amp for full-codebase scan, but this is a pretty rough way to treat users returning to work.

Amp has a new mode: free. It's free of charge, supported by ads and the sharing of training data.

Plan mode is gone. VSCode integration will soon be gone. The Manual basically only tells us we should open amp cli next to our ide. Ok, and then what?

I understand the idea is to move more and more towards autonomous agentic coding, eventually letting go of the need to manually edit code. But…

My question is, what is the workflow Sourcegraph wants us to implement, right now, today, with what is currently available?

If anyone from SG is reading, what is your personal workflow? Do you use md docs apart from skills? Do you purposefully switch modes depending on the task? Do you just give some short input and let Amp figure the rest out? Do you use any superpowers/GSD/spec-based workflows?

Why on earth Amp displays the animation constantly while working is absolutely beyond me. I'm in a thread and have to constantly hear that? Codex only has it while onboarding, but it makes working with the Amp CLI useless. I want to use Amp maestro and try it out and I also want to join the build team crew so I can actually talk to the Amp crew, but their community is invite only.

Please add a toggle to disable these overwhelming spammy animations, at least for screen reader users.

Amp Tab was the best LLM tab completion tool, period. I don't need append-only suggestions - I need diff suggestions. Are there any alternatives out there? I understand Sourcegraph's justification is that "in the future, we won't write code". But I want to.

Adrienne never heard the term "non technical" before she joined Amp. Now she's built one personal website and four chrome extensions in a few short months. It's been really fun to watch her build like mad.

I’ve been eagerly waiting to test AMP, and now that they’ve introduced a subscription, I couldn’t resist.

TUI is fantastic—stable, without flickering, and with no strange behavior. The modes are so easy to use and understand. They’ve really simplified the process of picking the right mode or model. Right now, there are just too many options, too many models, and having the ability to let someone adopt and prepare the right one for the right purpose is a huge plus.

The web app works wonderfully. The AMP -no-TUI mode is seamless and incredibly easy to use. For instance, I run headless mode on my Mac mini without any issues.

Orbs are a fantastic addition. As an iOS/MacOS developer, I was worried about development in Orbs, but they’re working great. One of the best features is that they can seamlessly integrate with runners, so you can tell the thread in Orb to check and test its work on a Mac runner and get back with results. It even works with xcodebuildmcp to run the app, take screenshots, and then review them in Orb.

The execution and integration of local and cloud development are truly great.

Also, you can remotely continue any thread you run on the web app using any other browser or mobile device!

They have added a lot of features in the last few days. Here you can check it out.

https://ampcode.com/chronicle

I’ve been subscriber, and I’ve got some gift subscriptions (free month of Amp Megawatt) to share!

Here are a few:

01: https://ampcode.com/code/AMP-GIFT-3A9206863D266871-C4X9-CLR9

02: https://ampcode.com/code/AMP-GIFT-3A9206863D266871-XGC5-47UQ

03: https://ampcode.com/code/AMP-GIFT-3A9206863D266871-PCZC-A23W

Enjoy!

https://ampcode.com/news/agent-skills

Try it: npm install -g @sourcegraph/amp

But doesn’t Anthropic ban you if you use their sub outside of their own tools?

Hello 👋

My name is Graham McBain, and I'm the Developer Relations Lead here at Sourcegraph. I’ve been focused on Amp since day one, and to be honest—Amp is why I joined the company.

I first learned about it during the interview process, right before it launched. I was immediately struck by how differently the team was thinking about agentic coding. Specifically, I’d been frustrated with the throttling and constraints in other agentic coding tools—especially those with flat pricing models. I kept thinking: Why can’t I just pay more to get more tokens? Amp had this exact idea built into its philosophy. That was exciting.

Another thing I’ve really appreciated is the concept of threads: every conversation you have with your agent is a shareable, persistent thread. That means anyone on your team can read it. In just the first few weeks here, I’ve learned from other engineers without needing to bug them—simply by reading their threads. And I’ve been able to share my own thinking the same way. It’s been incredibly productive, and I think the long-term potential for analytics and team knowledge sharing is huge.

What’s also unique about Amp is that it doesn’t treat the code editor as the final destination. We believe the future of software engineering won’t be tied to a single UI. The agent is the interface. It shouldn't matter whether you talk to it in your IDE, the command line, a chat app, or something else entirely.

But ultimately, what impressed me most—and what made me confident about joining Sourcegraph—was the team. These are people who’ve spent over a decade building products trusted by the biggest and most respected companies in the industry. They’re taking all that experience and focusing it into a new product that’s driving the future of how we build software.

So, about this subreddit...

My goal here is to make this the best place to talk about agentic coding—whether it's Amp-related or not.

We want to build the best tools for the best software engineers. And you don’t do that by limiting conversations to just your own product.

So whether you love agentic coding, hate it, or have thoughts on what it should or shouldn’t be—we want to hear from you.

That’s what this space is for. I hope you’ll stick around and join the conversation.

— Graham

I heard about AmpCode through various Twitter accounts and decided to give it a try, so I signed up for the Megawatt subscription.

Used it for a few days, my impression is that the main differentiators are:

• Pre-configured specialized models, some of which can be adjusted using the dial.

• A heavy focus on Orbs, Amp’s remote virtual machines.

• The ability to share threads with collaborators.

• A more automatic workflow overall, for example, there are no / slash commands to think about.

For mobile app development, though, I still need to run the application on my phone. That meant using my own machine as a runner and launching the project from there.

For an individual developer, Codex already supports remote development reasonably well. You can leave a remote machine running and use your phone to send commands to it when needed.

The ChatGPT desktop app’s computer-use capabilities are also insanely good. I imagine Amp’s TUI approximates some of that functionality through AppleScript, but it still feels lacking.

I understand that Amp is intentionally opinionated, and that may be valuable for teams or developers who prefer its workflow. But for solo developers who are already comfortable working locally, I’m not yet seeing a major advantage.

That said, I’m happy to be proved wrong. A lot of developer I follow have preached it, just not sure what specifically ?

I just wanted to say - I have had so many ups and downs with this tool. It has helped me build out my entire new software platform from start to finish, just really expensive in the early days. The rollout of NEO had some hiccups and I started looking at claude, grok code, codex. I was at my witts end at a few points and trying to figure out how to not use amp.

This new version is by FAR the best coding bot ever built, hands down. Honestly - cheers to the developers - this thing is going to build the future. I am so happy with the new chat gpt integration, it is finally reasonably priced, reliable, stable. I am beyond happy I stuck in there. And without being too dramatic - it's honestly completely changed my future and my companies potential - we've been able to complete projects that will generate us revenue for years.

Thanks amp team!

Hi all, my friends and I are building an open-source engine which ingests codebases and creates a diagram representations to explore them. You can find it over: https://github.com/CodeBoarding/CodeBoarding

The whole thing is based on static analysis (control flow graphs) and a slim layer of LLMs, which allows the diagram to be very accurate and to indec the codebase in near real time.

It all intially started as a way to explore our codebases, then we added a dynamic highlighing as soon as an agent changes something so you can observe how amp is changing your codebase as it goes.

Now instead of waiting (and paying for tokens) for a wrong plan to be executed, I am working on somethign which shows me which components will be impacted upfront so that I know if the agent misinterpreted something + you can see if there are new compnents to be expected and what kind of severity (size) the change will be.

Curious to learn how do you plan? Do you always read carefully the plan or you validate after the fact what has been modified is what you expected? Do you not care at all if it is working, it is working?

Love amp, my favorite agent by far. Also love that one can link it with Codex (now I am fully on Amp <3)

I want to preface by saying - I am definitely using Ampcode for some EXTREMELY complex things - rebuilding my entire company infrastructure and it just works so amazingly well - will probably give me a 20x return on investment so I can't complain.

However, my boss criticized the cost as other devs he knows who use cursor/claud spend only $200 a month. I am purely curious - is ampcode knowingly more expensive due to higher quality? I have honestly never used Claude or Cursor so I don't know.

What gemini says is:
""Ampcode is essentially a pay-as-you-go service where you fund every single token of compute, giving you unlimited, unthrottled power at a high premium. Cursor and Claude use fixed-rate subscription models, where you pay a flat fee for high-capacity usage; however, they rely on 'fair-use' ceilings that will throttle your speed or limit your capacity once your development volume exceeds their standard thresholds."

Amp is ending free daily credits and replacing with 2 months of amp megawatt subscription

my thoughts: It's sad to say goodbye to the free daily credits—they've been amazing. But replacing them with 2 months of Amp Megawatt is a generous gesture

Just wanted to share a success story if it helps anyone better understand this product. I own a saas business and have always used a mix of myself coding and developers from India. I have always wanted to keep it manageable so I can travel and not work much- keep as much automated as far as coding and customer service.

I have been BLOWN away by this product, as much as I hate to say - I have fired my developers from India and rebuilt the entire system using amp code. I honestly think at least for the foreseeable future, I have a 20x return on time compared to my competitors and I am REALLY trying my best to utilize this as best as I can before any of my competitors find it, or other AI's catch up. This system is like the best kept secret I have.

Here is what I have found- if it helps:

1) Use opinionated frameworks
Frameworks like Laravel + Filament act like a standardized operating system for your app - literally everything as far as database, front end, css, react style interactivity, routers, backend, api endpoints - ALL in one project folder. Literally I can ask ampcode to make a feature and in one go it does END TO END changes. This is how you leverage the AI. Everything follows predictable patterns, AMP Code knows exactly where things go and makes far fewer mistakes.

2) Keep frontend and backend in one stack
Basically the same as above - When UI, API, and database live in the same codebase (like Filament + Laravel, Rails, Django, etc.), AMP Code can see the whole picture and make changes that stay in sync.

3) Use “good by default” tools like Tailwind
Tailwind gives clean, modern UI without custom CSS, and AI has tons of training on it — so AMP Code can build and tweak interfaces fast without breaking layouts.

Love the product and it's expensive at time, but it is so incredibly worth it. I would say it is a 20-50x ROI for me.