THE LARGEST PLAYOFF COMEBACK IN NEW YORK KNICKS HISTORY 🔥

Let the celebrations begin 🎉 @Arsenal

The Arsenal. Your Premier League champions.

CHAMPIONS!!!

Congratulations to all Arsenal fans. We did it.... after 22 years of waiting.

22 years too long!! But makes it even sweeter!! #GoGunners @ah @RobChiz @anku

Arsenal !! Champions !! #EPL #Invincible /cc @anku @RobChiz @ah

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.