Adi Ranjan

We made Amp Free. It's powered by great tokens and tasteful ads. Agentic coding is now free for everyone.

Amp Free. Everything about agentic coding is changing again.

What kinds of ads support Amp Free? We're fortunate to have some of the best-loved dev tools companies as partners at launch.

We set out to make Amp Tab better than Cursor Tab and usable in VS Code or any fork thereof. It’s also free (too cheap to meter). If you’re using VS Code, try it. If you’re using Cursor/Windsurf with Amp/CC/Codex, you might be able to ditch the fork and monthly sub.

Watch this 4 min video to learn how to 1. Create a custom slash command called 'ship' 2. Use the /ship command to *reliably* deploy to prod (error free) with an agent Also, Build Crewers, unite! If you want to join the tribe, it's free: buildcrew.team

We flipped the switch: Amp Tab is now on by default for new installs. It’s our free completion engine for manual edits in VS Code. It’s fast, knows your recent changes and compiler errors, and suggests cross-file updates when needed. Already on Amp? Run `Enable Amp Tab` from cmd/ctrl+shift+p.

Amp Tab for all! Let's gooo :)

Tip #2 for coding better with agents from Amp Core Dev @camden_cheek Create a custom slash command that uses ripgrep to find TODOS and implement them. The beauty is that the context is already right there in the file and you have a helpful comment that tells the agent what to do. ```markdown # Ampdo Command **Instructions:** Search for AMPDO: comments in the codebase to gather feedback and instructions about code changes. ## Search Process Use ripgrep to find AMPDO: comments with context: ```bash rg "AMPDO:" -C 3 ``` ## Review Process - Read each AMPDO comment and surrounding code context - Take appropriate action based on the feedback: implement requested changes, address issues, or follow instructions - Present findings organized by file and comment type - Execute any action items or specific change requests ## Output Format - Group by file path - Show line numbers and full context for each AMPDO comment - Summarize key themes and action items at the end ## Expected Actions After finding AMPDO: comments, the agent should: 1. Analyze the feedback or instructions in each comment 2. Implement any requested code changes 3. Address any issues or concerns raised 4. Remove or update AMPDO: comments once addressed 5. Provide a summary of all actions taken ```

Tip #3 for getting better at prompting agents for coding … Amp core dev @nicolaygerold uses @obsdmd when he needs to take his time and write very detailed prompts. Forces him to make sure he’s super clear with the agent on the task.

RT @AmpCode: Raising An Agent - Episode 8 In this episode, @beyang sits down with @camden_cheek to discuss how the Amp team evaluates new…

`/new` `/continue` `/finally` (not a real slash command)

We will make your terminal do things you never knew were possible

Here's a real example of how GPT-5 behaves in Amp compared to our default agent. Left is default, right is GPT-5 agent. This is N=1, so standard caveats apply, but these are wildly different runs. More commentary below.

Try GPT-5 in Amp: ampcode.com/news/gpt-5 See our model evaluation notes (continuously updated): ampcode.com/news/model-eva…

We’ve been working with OpenAI over the last few weeks on GPT-5 in Amp. We’re still evaluating where and how to use GPT-5 (after all, it took 6 months to figure out 3.5 Sonnet’s true capabilities). Join us and try GPT-5 in Amp now:

GPT‑5 is now live on @AmpCode 🚀 Dive in via the CLI (amp --try‑gpt5) or flip on the extension ("amp.gpt5": true) in your favorite VS Code editor, Cursor, or Windsurf! #GPT5 #Amp #AI

GPT-5 isn't the only big announcement today. We just announced Jetbrains in the CLI here at @AmpCode 😎

For all our @jetbrains stans out there, we got you! Check out the @AmpCode CLI integration now: ampcode.com/news/jetbrains…

New frontier models deserve a proper mech suit tuned to their strengths. A new mech suit lands in Amp tomorrow.

There it is, the first orb