
Coding agent and development environment
Once each task has its own orb, closing the laptop does not stop that thread, and a phone can pick it up. Production logs are not open by default; access is granted or revoked per orb, and the page's example uses OIDC. A scheduled wake-up can return to check a rollout. A screen recording is how a flicker is handed over for investigation. A new project can start from scratch, be hosted by Amp, and be cloned locally with amp clone. Teammates can read the same thread. It fits engineering teams that hand rollout checks and bug cleanup to an agent and need to follow progress remotely.
Amp from Sourcegraph is a coding agent and development environment. Each agent has its own orb and can keep working after you close the laptop, switch to a phone, or step away, and progress can be shared with teammates. An agent can wake itself on a schedule to check a result that already shipped. Production access is granted or revoked per orb through OIDC. A new project can be hosted by Amp and cloned locally with amp clone. It can also investigate an interface problem from a screen recording you provide, and post to Slack through MCP.
Difficulty: Advanced
Orbs that keep running
Each agent has its own orb and can keep working after the laptop is closed, the phone takes over, or you step away.
Production access per orb
Production access is granted or revoked per orb through OIDC, rather than opening every log by default.
Wake up to check a rollout
An automation can wake the agent to check whether a fix that already shipped is holding in production.
Hosted repo and clone
A new project can start from scratch, be hosted by Amp, and be cloned locally with amp clone.
Check a rollout after leaving
An engineer asks for a production check, closes the laptop, and the agent wakes on schedule to compare the result.
Trace a flicker from a recording
Hand a screen recording of an interface flicker to a running thread so it can locate and change the cause.
Post progress to Slack
A thread posts its conclusion to Slack through MCP so teammates can read it without that computer.
Yes, if the task is running in its own orb. The page says an agent can continue after you close the laptop, switch to a phone, or step away, and that progress can be shared with teammates. That is different from keeping several local worktrees. The phone can pick up the same thread without returning to the original computer.
Not by default. In the page's example, each orb gains or loses production access through OIDC, and that access can be granted or revoked. The agent can also wake itself on an automation to check a result that already shipped. After access is revoked, that orb can no longer read the corresponding production logs.
A project can start from scratch, with the repository hosted by Amp. Locally you fetch it with amp clone. The page also shows an interface problem investigated from a screen recording you supply, and a message posted to Slack through MCP. Those steps stay in the same thread, which teammates can open.
Real reviews and feedback from users