Amp is a coding agent and development environment for engineers who want agents running independently. Each agent gets its own orb, a remote environment where it keeps working after you close your laptop, and you can steer it from a browser, a terminal or a phone. For local work, a CLI and runner put the same agent on your own machine. Threads are multiplayer, so teammates can watch, review and continue each other's work.
It is aimed at professional developers, small engineering teams and startups who spend their days juggling parallel tasks, branches and worktrees and would rather hand follow-ups to an agent. Engineers comfortable with terminals, code review and production monitoring will see the most value, because the agent can be granted access to infrastructure and then asked to show proof of its work.
Examples drawn from real use include monitoring a performance rollout with automations that wake the agent on a schedule and compare production numbers, fixing a bug straight from a user report, reproducing a UI flicker from a screen recording, and testing and shipping changes while watching a rollout. Developers also dictate prompts, ask for screenshots as proof, post updates to Slack through MCP, and verify refactors in a terminal attached to the orb. Projects can be hosted by Amp and cloned with amp clone, and production access can be granted or revoked per orb through OIDC. Because agents run in orbs rather than on a laptop, long tasks such as rollouts, refactors and bug investigations can continue overnight, and results are waiting in a thread when the engineer returns to review them.
