---
title: Rush Mode
link: https://ampcode.com/news/rush-mode
source: ampcode-com
published: 2025-11-07T00:00:00Z
updated: 2025-11-07T00:00:00Z
first_seen: 2026-10-03T23:09:50.514863041Z
summary: '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.'
content: extracted
html: 2025-11-07-rush-mode.html
preview:
  file: 2025-11-07-rush-mode.preview-b9563696879a.webp
  width: 256
  height: 134
  color: '#5f584e'
images:
- source: https://ampcode.com/og?_template=news&_version=7&title=Rush+Mode&date=November+7%2C+2025&tagline=A+faster%2C+cheaper+way+to+use+Amp+for+small%2C+well-defined+coding+tasks.&sig=74d7c8914d91b34de3cbf469b309c2d1b443573fd85a894159d0d1d610372885
  original:
    file: 2025-11-07-rush-mode.image-de06c69f50d7.png
    width: 1200
    height: 630
  variants:
  - file: 2025-11-07-rush-mode.image-e4443a784150.webp
    width: 320
    height: 168
  - file: 2025-11-07-rush-mode.image-80f98eb235b6.webp
    width: 640
    height: 336
  - file: 2025-11-07-rush-mode.image-0eeec5b53003.webp
    width: 960
    height: 504
  - file: 2025-11-07-rush-mode.image-a76894a75634.webp
    width: 1200
    height: 630
  color: '#221b16'
---

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..."](https://ampcode.com/threads/T-62d6f9c3-4859-4dbe-a0ec-0460e2a3707a)
- 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..."](https://ampcode.com/threads/T-aae44811-8790-4ea5-9841-ad85014db950)

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](https://ampcode.com/modes) in `rush` mode, including [the oracle](https://ampcode.com/manual#oracle) and [the librarian](https://ampcode.com/manual#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.