Amp

What Amp is

Amp describes itself as a coding agent and development environment built for the frontier ^[1]. Rather than a single chat window that answers questions about code, it is presented as a working environment in which agents take on development tasks, and it is aimed at people doing demanding, up-to-date software work.

The company behind it calls itself an independent agent research lab ^[1]. That framing matters: Amp is positioned as a product of agent research rather than as a feature bolted onto an existing code editor or cloud platform.

Who it is for

Amp says it works with indie developers as well as with companies that have more than 20,000 developers ^[1]. That range — from individual builders to very large engineering organizations — is the audience the product is designed around.

The team also operates Amp Labs, which it describes as placing small teams of AI-native builders inside companies in the real economy ^[1]. That work sits alongside the software itself, putting agent-based development into organizations outside the tech industry.

How the agents work

The product page says agents keep working after the laptop is closed and can be started from a phone ^[2]. In practice that means an agent's task is not tied to a session on one machine; work continues in the background and can be kicked off remotely.

Amp gives each agent its own orb, and the page says this removes the need to juggle git worktrees ^[2]. Git worktrees are a common way for developers to work on several branches at once without disturbing each other; giving every agent its own isolated environment handles that problem for the user instead.

A walkthrough on the product page shows an agent using automations to wake itself up, a Portal to test a change, and MCP to post a summary to Slack ^[2]. The three pieces together sketch the intended loop: an agent schedules its own follow-up work, checks a change in a running environment, and reports back into the place where a team already talks.

The team and its stance

The about page lists Beyang Liu and Quinn Slack among the people at Amp, and says everyone at Amp builds Amp with Amp ^[1]. Using the product to build the product is presented as the team's normal way of working.

The team's manifesto commits to building for a world in which intelligence is abundant, continuous and cheap ^[1]. Those three words describe the assumption behind the design: that model capability is not a scarce, rationed resource but something available all the time and at low cost, and that developer tools should be built accordingly.

The same about page quotes users describing Amp as the Porsche of command line coding agents ^[1] — a comparison the team chooses to display, pointing at a command line heritage alongside the broader environment.