Rush Mode

Amp has a new mode: rush, named so because a rushed job is faster and cheaper in the moment, and sometimes that's more important than quality.

Token-by-token, it's 67% cheaper and 50% faster than smart.

Prompt-to-result (what you actually care about)? It depends. It's less capable, which means that on complex tasks it often spends more tokens and time fixing its mistakes along the way.

You can rush small, well-defined tasks: simple bugs, small UI changes, minor features. For best results, mention the files that need to be changed.

Don't rush complex tasks: new end-to-end features, bugs with no clear diagnosis, an architecture refactor. It'll be slower and not much cheaper, if it even arrives at a solution at all. Use smart instead.

For example:

• A small rush-able task that took 37 seconds and cost $0.12 (44% faster and 77% cheaper than smart): "warn if there are more than 20 MCP tools..."
• A complex, non-rush-worthy refactor where rush took 2x longer than smart and was just 19% cheaper: "refactor all hardcoded colors from the CLI and web UI..."

The rush agent mode is a unique combination of system prompt, tools, and model (Haiku 4.5 for now). You can use all of Amp's subagents in rush mode, including the oracle and the librarian. You'll also notice it doesn't show its TODOs, which makes it faster.

To use it: run command mode: use rush in the Amp CLI, or select rush mode in the Amp editor extension's prompt field.