Here's a concrete reward for good software architecture: if your system contains of easily identifiable components, Amp can create them faster and cheaper for you.

What's one architectural decision you make in all projects you start? For me it's unidirectional dataflow.

Toolbox tools are now properly streaming their output

Compaction does encourage laziness, essentially letting you give up on your context window. Given how precious the context window is, that's a bad idea. Handoff instead of compact solves this elegantly

Unix has almost the perfect permissions model for agents. Give them a $HOME. Put agent tools in ~/.local/bin. Selectively give them access to your files using chown.

Here's the full post with a walkthrough on how to create a new tool called `run_tests`, all commands and output shown: https://t.co/ovx2jPuTCJ

We've made Amp toolboxes better: • AMP_TOOLBOX supports multiple toolboxes, like PATH • `amp tools make` creates a new, ready-to-edit tool • `amp tools show` inspects it • `amp tools use` tests it It's now super easy to create a new tool and get immediate feedback.

https://t.co/ThC8NpCmb0

Amp's CLI is now a proper, full-on TUI. Best part for me personally? No more Ink, no more flicker.

https://t.co/a20xG52ZIO

Amp now lets you provide tools to the agent with a few lines of code. Instead of writing an MCP server, you can drop any executable into a directory you tell Amp about. As long as the executable can produce a tool description, Amp will pick it up. This way Amp doesn't have to

[👇link below 👇] When I speak with peers who have similarly spent the same amount of time invested in these tools, we're noticing a new emergent pattern: We are reducing our consumption of open-source software and minimising our dependencies on third parties. Instead of

@AmpCode Here's a real example of how it works

This is the longest I had @AmpCode work without supervision - I could hardly believe it, it just kept going. The secret ingredients were: - giving Amp a structured planning tool (NOT markdown files) - telling it to use a subagent for each step of the plan. I had the plan

All details here:

Amp now has a better permission system. You can now define exactly which tool (built-in or MCP) can run with which arguments.

New JetBrains integration in the Amp CLI

Our next step towards more agents in the terminal: amp -x

Part URI is not valid per rules defined in the Open Packaging Conventions specification. The Open Packaging Conventions specification is ECMA-376, which points to RFC3987 which tells you what characters are allowed in a package. ChatGPT saw the space, I didn't.

Amp's new CLI is finally the default! https://t.co/ONc7TvhZCS