Threads

A thread is one conversation with the agent: your prompts, the agent’s replies, every tool call it made, and the files it changed. Threads are the unit of work in Amp. You start one per task, come back to it from any device, hand it to a teammate, or point a later thread at it.

Every thread has a URL like https://ampcode.com/threads/T-…. The same thread opens in the web app, the CLI, the Amp apps for iOS and macOS, and in Slack through Puck. Where the agent runs is separate from where you look at it: a thread can run in an orb, on a runner, or in a local CLI session.

An orb thread on ampcode.com with the agent's reply on the left and the Changes pane on the right listing changed files with Ship, Review, and Sync actions

Where Threads Live

The sidebar lists your recent threads. The Organize menu at the top groups them By Project, By Recency, or By Type (orb, runner, or local CLI), or shows one flat list. Snoozed and archived threads have their own sections at the bottom.

The Activity page with the sidebar open, showing search, time, status, user, and project filters next to a list of recent threads

Activity at ampcode.com/feed shows every thread you can see, including your workspace members’ shared threads. Filter by time, status, author, or project, or search with the same query syntax the agent uses to find threads. The filters live in the URL, so /feed?time=7d&q=label:bug is a link you can bookmark or share.

Each project page also lists the threads that worked on that repository.

Start a Thread

Web. Click New Thread in the sidebar. The composer shows where the thread runs (a new orb or a connected runner), which project it belongs to, and which mode the agent uses. Type a prompt and press Enter. The Orbs getting started guide walks through this.
CLI. Run amp in a repository to start a thread on your machine, or amp -ox to start one in an orb for the matching project. amp -x "prompt" runs one prompt and exits. See the CLI page.
Puck. Ask Puck on the web or in Slack to start a thread for you.
Another thread. An agent can start a thread and wait for its result with Agent to Agent. When a thread gets long, ask the agent to “Handoff and …” and it starts a fresh thread with the context that matters.
On a schedule or an event. Automations and event-driven orbs start threads without you.

Use one thread per task. Threads can go on for a long time, but a thread that mixes unrelated work gives the agent a worse context to reason with. See Prompting for more.

Inside a Thread

The title bar shows the thread’s title, the More Actions menu behind the … button, Share, the project, and the agent mode. For threads that run in an orb, the panes on the right open into the machine:

Changes lists what the agent changed since the last commit. Ship commits and pushes according to the project’s Ship Behavior, Review walks through the diff, and Sync pulls the orb’s branch to your machine.
Portals shows web servers running in the orb. See Portals.
Files browses the orb’s file system.
Terminal opens a shell in the orb.

The composer at the bottom sends the next message. While the agent works, a message you send is queued until the agent finishes; press Enter twice to steer it after its current step, or Esc twice to interrupt. See Queueing Messages.

Continue a Thread Anywhere

A thread is not tied to the device you started it on.

Open an orb thread on your phone or another computer and keep prompting. The orb wakes up when you send a message.
Run amp threads continue T-… to attach the CLI to a thread, or pick Copy → Sync CLI Command from the More Actions menu to copy the command with the thread ID filled in.
Send a single message to an orb thread from your terminal or a script without attaching to it:
```
$ amp threads continue T-… -ox 'The deploy finished, verify the fix in production'
```
The message runs on the thread’s own orb, so this is a simple way to wake a thread from a CI job or a shell script.
A thread you started in the CLI stays open on the web too. Send it messages from ampcode.com with Remote Control.

Reference and Find Threads

Paste a thread URL or type @T-… in a prompt and the agent reads that thread and pulls out what matters for the current task. In the CLI, type @@ to search for a thread to mention. Ask the agent to find threads by keyword, file, author, label, or date, and it searches your threads and your workspace members’ shared threads. See Referencing Other Threads and Finding Threads.

Commits the agent makes carry an Amp-Thread-ID trailer, so git log leads from a change back to the conversation that produced it. Putting the thread link in a pull request description gives reviewers the same context.

Click Share in the title bar to copy the thread URL or change its visibility.

The Change Visibility dialog with the options Private, Workspace, and Unlisted

Visibility	Who can open the thread
Private	You. In a workspace, workspace admins can also see it.
Workspace	Every member of your workspace.
Group	Members of the groups you choose, plus workspace admins. Enterprise workspaces only.
Unlisted	Anyone on the internet who has the link.

Without a workspace, new threads are private. In a workspace, threads in workspace-owned projects are shared with the workspace by default, while threads in personal projects or without a project are private. Admins can change the default, turn off sharing outside the workspace, and set up groups; see Thread Visibility Controls.

In the CLI, press Ctrl+O and run set visibility, or run amp threads share T-… --visibility unlisted. Run amp threads visibility private in a repository to make new CLI threads from that repository private by default.

Export a Thread

Add .md to a thread URL, for example https://ampcode.com/threads/T-….md, to read it as Markdown. Export in the More Actions menu offers Markdown and, for the thread’s creator, the full JSON. In the CLI, amp threads markdown T-… and amp threads export T-… do the same.

Organize Threads

The More Actions menu next to the title holds everything that changes how a thread appears in your lists.

The More Actions menu of a thread with Copy, Export, cost and orb status, Pin, Color, Labels, Rename, Snooze, Archive, Delete, Full Width, and Report Bug

Pin keeps a thread at the top of the sidebar.
Color marks the thread in the sidebar and tints its title bar.
Labels tag the thread. Click a label to see every thread with that label in Activity, or search with label:<name>.
Rename replaces the title the agent chose.
Snooze hides the thread for an hour, a day, or a week, or until the agent’s next message. Snoozed threads wait under Snoozed in the sidebar and come back when the snooze ends.
Archive removes the thread from your active lists. The URL still works and the agent can still reference it. Archived threads appear under Archived in the sidebar and in Activity.
Delete removes the thread permanently.
Mark as Unread brings the unread dot back so you remember to look at it later.

The menu also shows what the thread has cost so far and, for orb threads, whether the orb is running and which size it uses.

From the CLI, amp threads label, amp threads rename, amp threads archive, and amp threads delete do the same, and amp threads list and amp threads search find threads without opening the web app.

Work on a Thread Together

Type @ in the composer to tag a workspace member. Tagging invites them to the thread and turns on Multiplayer, so they can prompt the agent, open the orb’s portals, and use its terminal and files. Only non-private orb threads can be made multiplayer, and agent and orb costs are billed to the thread’s owner.