Amp Retires Tab Feature as Agents Write Most Code

Amp Tab will work through the end of January 2026, after which the feature is retired. Amp says it now writes 90% of shipped code and is pivoting from inline tab-completion toward agent-driven workflows; users are pointed to Cursor, GitHub Copilot, or Zed.

amp cover

TL;DR

  • Retirement timeline: Amp Tab will function until end of January 2026, then support ends.
  • Shift in production: Amp now writes 90% of shipped code, driving a move away from inline completions to agent workflows.
  • Product impact: Development resources redirected from inline completion to agentic capabilities.
  • Alternatives for inline completions: Cursor, GitHub Copilot, Zed.
  • Interaction model change: Expect agents to produce and iterate on larger portions of code rather than humans typing most code.
  • Context: Announcement includes a short video conversation with Quinn and Thorsten framing the change as a strategic pivot.

The Amp Tab feature is being retired: it will continue to function until the end of January 2026, after which support ends. The announcement frames this move as part of a broader shift in how code is produced—Amp now writes 90% of shipped code, and the team is positioning inline tab-completion as a legacy interaction model in favor of more agent-driven workflows.

Why Amp Tab is being retired

The decision reflects a change in how the product team sees developer workflows evolving. Early efforts treated AI as an augmentation layered on top of human-written code, with inline completions filling gaps as developers typed. With Amp taking on an increasingly dominant role in generating deliverables, that model is described as less relevant. The retirement of Amp Tab is presented as a reallocation of focus from maintaining inline completion toward building for a future where agents handle the majority of coding tasks.

What this means in practical terms

  • Service window: Amp Tab remains available through January 2026; after that date, the feature will no longer be supported.
  • Shift in interaction model: The change signals a move away from expecting humans to author most code and instead toward workflows where agents produce and iterate on larger portions of a codebase.
  • Product focus: Development resources and attention will be redirected toward agentic capabilities rather than incremental improvements to inline completion.

Alternatives for inline completions

For teams and developers who still rely on inline suggestion workflows, the announcement points to several alternatives: Cursor, GitHub Copilot, and Zed. These options are suggested specifically for continued access to inline completion behavior after Amp Tab is retired.

Additional context

The announcement includes a short video conversation featuring Quinn and Thorsten reflecting on the end of Amp Tab. The move is framed as a strategic pivot rather than a technical failure: the product team emphasizes exploring the next set of problems that arise when agents are the primary code authors.

Original source: https://ampcode.com/news/tab-tab-dead

Continue the conversation on Slack

Did this article spark your interest? Join our community of experts and enthusiasts to dive deeper, ask questions, and share your ideas.

Join our community