Amp has released a new version of its rush agent mode, recasting it as a faster, lower-cost option for small coding tasks rather than a general-purpose agent for broader codebase work. The company states that rush now uses GPT-5.5 with no reasoning, replacing Haiku 4.5, and is meant to find the relevant files, make the smallest correct change, run a focused check, and stop.
Amp lists examples of the kinds of tasks rush is meant to handle: fixing a failing test, matching styling between components, and renaming a symbol across files. It also cautions against using the mode for transient bugs, architecture changes, migrations, complex features, or work where the definition of “done” is still unclear.
The release also changes the toolchain. rush now uses shell_command for searching, reading, and verification, plus apply_patch for edits. That allows Amp to remove several overlapping tools, including grep, glob, and create_file. The company adds that the task subagents use the same setup as the main agent: no reasoning and GPT-5.5.
On its internal evals, Amp reports that rush solved 44% of tasks, up from 39% for the previous version. Average cost rose to $0.58 per task from $0.44, an 18% increase, while runtime fell to 1 minute and 32 seconds from 2 minutes and 59 seconds. Amp characterizes that as a tradeoff of “a little more expensive, meaningfully more capable, and almost twice as fast.” It also notes that deep performed better on the same evals, solving 58% of tasks.
Amp also highlights a pairing with the oracle tool. The suggested pattern is to let rush build, then have the oracle plan, criticize, or review. The company describes the oracle as slower, more expensive, read-only, and suited to adversarial thinking. It suggests that approach for bounded tasks with enough complexity that a second pass may prevent a locally plausible but globally incorrect edit.
To use it, Amp says to run mode: use rush in the Amp CLI.
Source: Amp
