Amp 2025.10.22
Amp 2025.10.22 was released on .
Summary
More Tools for the Agent We shipped several changes to toolboxes that make them easier to use: - You can now have multiple toolboxes in the AMPTOOLBOX environment variable - amp tools make is a new...
Release Context
- This was the 3rd Amp release of 2025 tracked by Havoptic.
- It shipped 1 day after Amp 2025.10.21 (October 21, 2025).
Shipped around the same time
Within 3 days of this release, other AI coding tools also shipped:
- GitHub Copilot CLI v0.0.351 (October 24, 2025)
- Zed v0.209.6 (October 24, 2025)
- Claude Code v2.0.27 (October 24, 2025)
- OpenAI Codex CLI rust-v0.49.0 (October 24, 2025)
- GitHub Copilot CLI v0.0.350 (October 24, 2025)
Compare Amp
- Amp vs Claude Code
- Amp vs OpenAI Codex CLI
- Amp vs Cursor
- Amp vs Gemini CLI
- Amp vs Kiro CLI
- Amp vs GitHub Copilot CLI
- Amp vs Devin Desktop
- Amp vs Antigravity CLI
- Amp vs Grok Build
- Amp vs Cline
- Amp vs OpenCode
- Amp vs Zed
- Amp vs Factory Droid
- Amp vs Devin
- Amp vs Lovable
- Amp vs GitHub Copilot in VS Code
- Amp vs Replit Agent
- Amp vs Bolt
- Amp vs v0
Release Notes
More Tools for the Agent We shipped several changes to toolboxes that make them easier to use: - You can now have multiple toolboxes in the AMPTOOLBOX environment variable - amp tools make is a new command to create a functional example tool in the right location - amp tools show lets you inspect a tool - amp tools use allows you to execute it And Amp itself can fill in all the details to make the tool work as you intended. If you don't yet know what toolboxes are: a toolbox is a directory full of UNIX-style programs that provide custom tools to the agent locally. Conceptually, they sit between MCP servers and common CLI tools, but are less complex than MCP servers and easier for the agent to use than plain CLI tools. Let's use an example to see how we can use amp tools make and amp tools use to create and run a new tool in a new toolbox. Let's build a runtests tool. Chances are that if you have used any coding agent before, you've probably seen it trying to run the your tests, but then stumble and having to guess a few times what the correct command invocation is. We can make (artificial) life for the agent easier by giving it a runtests tool that will always use the correct command. First we create a .amp/tools directory in our repository and add it to the AMPTOOLBOX variable, so Amp knows to look there for tools: Create the directory mkdir -p .amp/tools Add to AMPTOOLBOX. Order matters: prefer tools in the repo over global tools export AMPTOOLBOX="$PWD/.amp/tools:$HOME/.config/amp/tools" Next we run amp tools make to create a new tool, using a built-in template: amp tools make runtests Which prints: Tool created at: /Users/dhamidi/w/amp-wip/.amp/tools/runtests Inspect with: amp tools show tbruntests Execute with: amp tools use tbruntests Great! Now we could open .amp/tools/runtests manually and edit it as needed, so it actually does what we want and runs the tests. But, hey, we can also tell Amp to inspect our package.json file, find the right test command, and adjust the tool template accordingly: amp --dangerously-allow-all -x 'Edit .amp/tools/runtests to run the tests using pnpm test according to our package.json file. It should have an optional workspace parameter and an optional parameter for filtering by test name' Now we can use amp tools show to inspect the tool and see what Amp has created: amp tools show tbruntests That prints the description of the tool (which the Amp agent will see) and the schema of the input parameters (which the agent will use to run the tool): tbruntests (toolbox: /Users/dhamidi/w/amp-wip/.amp/tools/runtests) You must use this tool to run tests instead of using the Bash tool. This tool runs tests using pnpm test with optional workspace filtering and test name filtering. Schema - workspace (string): optional workspace name to run tests in (e.g., "core", "web", "server", "cli"). If not provided, runs tests in the root workspace - testName (string): optional test name filter to run specific tests (passed as -t argument to vitest) But before we now have the agent try it, we can use amp tools use to execute the tool to make sure it works: amp tools use --only output tbruntests --testName "writes a tool" Note how we specified --testName, one of the input parameters of the tool. If we run the command, we'll see something like this: ... Test Files 1 passed | 306 skipped (307) Tests 1 passed | 4181 skipped (4182) It works! And now, when you start Amp, it will automatically register this tool at startup, and use it to run the tests:
Other Recent Amp Releases
- 2026.10.19 (October 19, 2026)
- 2026.10.16 (October 16, 2026)
- 2026.10.13 (October 13, 2026)
- 2026.10.12 (October 12, 2026)
- 2026.10.12.2 (October 12, 2026)
Upgrading from 2025.10.22? See all 111 releases since.