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, and the Amp apps for macOS, Windows, Linux, iOS, and Android. 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. Pinned threads come first, then active threads grouped by project. Threads with no activity for 72 hours move into a collapsed Inactive Last 72h section. The archive button on that section’s header archives all of them at once. 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.

To choose your defaults, right-click or long-press an option under Time, Status, Users, or Projects and select Use … as Default. Each default is saved in this browser and applies when you open Activity without that filter in the URL. Saving a default does not change the current view. Use Reset Default in the same menu to reset that filter independently. Time resets to Last 24h. Status and Projects reset to All. Users resets to your own threads in a workspace where threads are private by default, or All otherwise. A saved project that you can no longer access is ignored.

Explicit URL filters take priority. Search links with a q parameter keep their existing defaults rather than applying your saved choices.

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 or on a connected runner, the panes on the right open into the machine:

Changes lists committed and uncommitted changes. Use its commit picker to view one commit at a time, as described in Review Commits. 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 an orb. See Portals.
Files browses the orb or runner’s file system. Drag and drop files from your computer onto it to upload them into the execution environment.
Terminal opens a shell in the execution environment. Paste or drop a file onto it to upload the file to the orb or runner and insert its path. See Upload Files to an Orb. (Runner terminals require the --remote-control-terminal flag.)

To make the transcript and composer wider, set Thread Width in Settings > Appearance to Wide or Full, or run Set Width to Wide or Set Width to Full from the command palette. The setting applies to every thread in that browser or app.

Review Changes

The Changes pane orders files intelligently: Amp reads the diff, moves the files that best explain the change to the top, and mutes less important files such as generated code. You can also have the changed files ordered alphabetically. If the diff changes after an order has been applied, Amp keeps that order while the agent works and computes an updated order when the turn finishes. If the new order would rearrange files, a blue dot appears on the file order button. Click Apply Updated File Order when you are ready. Intelligent ordering is unavailable when a diff contains more than 500 files or when the thread is read-only for you; files are then listed alphabetically.

Review Commits

When the thread’s branch has commits, a commit picker appears at the bottom of the Changes pane. Its button shows what the pane is showing and how many commits the branch is ahead of its base branch, such as All Changes · 3 commits ahead of origin/main. Click it to choose what the pane shows:

All Changes shows every committed and uncommitted change since the merge base, which is where the branch split from its base branch.
Uncommitted shows only the changes that are not committed yet.
Each commit since the merge base is listed by its short SHA and subject, newest first. Select a commit to see only that commit’s diff. Hover over a commit, or press the right arrow key, to read its full commit message.
Compare With Branch… shows all changes since the merge base with another remote branch.

To review a branch’s commit history one commit at a time, such as after a restack, select each commit in turn. You do not need to push the branch or open a pull request.

Every thread, with or without an orb, also has a Huddle pane: a voice and video call for talking the work over with your team. See Huddle.

The composer at the bottom sends the next message. When the agent is working, any message you send is steered: it is sent after the current step instead of waiting for the agent to completely finish. Press ⌘+Enter or Ctrl+Enter to instead queue the message until the agent completely finishes, or press 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.
Run amp threads continue T-… to attach the CLI to a thread. For an orb thread, pick Orb → Copy Sync CLI Command from the More Actions menu to copy an amp sync 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 Cross-Client Access.

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, or choose Share Thread… in the command palette. The Share dialog lets you copy the thread URL and choose access for your workspace, groups, or anyone with the link. Choose No access for an audience to stop sharing with them. You can also choose Contribute for workspace or group members to turn on multiplayer.

If you do not have a workspace, the dialog offers Create Workspace so you can share threads with your team.

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

Workspace admins open such a thread, or a link to one of its artifacts, through audited access: they confirm their identity again, the page shows an audit notice, and the view is audit-logged. Artifacts opened this way are read-only.

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.

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

Use a thread’s More Actions menu to organize it. To snooze a thread, right-click it in the sidebar or press Ctrl+G Z in the thread. On a phone, Snooze is in the More Actions menu.

The More Actions menu of a thread with Copy Thread URL, Export, orb status, Cost & Usage, Pin, Snooze, Archive, Rename, Labels, Color, Artifacts & Attachments, Delete, 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 and mutes its notifications. When something can bring the thread back on its own (the agent is working, an automation can run, or multiplayer is on), the menu offers Snooze Until I’m Needed. It ends when someone sends a message, the agent finishes replying to one, a scheduled run’s reply tells you something new (not when it only says nothing changed), or the thread’s automations are done; tool calls along the way do not end it. Otherwise the menu offers Snooze Until Tomorrow, or Snooze Until Morning between midnight and 8am, which ends at the next 8am. For any other snooze, ask the agent in the thread or Puck, for example “snooze this until Monday at 9am”, “snooze this for two weeks”, “snooze this until you need me”, “snooze this until I reply”, or “snooze this until I unsnooze it”. While a snoozed thread waits for you to approve a tool or answer a question, it shows in the sidebar; once you answer, it is snoozed again. Snoozed threads wait under Snoozed in the sidebar and come back when the snooze ends. Snoozing does not stop the agent, and it does not pause the thread’s automation; scheduled runs keep firing and using credits, but quietly. To stop an automation, pause it from the thread’s automation indicator or archive the thread.
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. You can unarchive a thread at any time, unless its project was deleted; those threads stay readable but are permanently archived. Archiving a thread does not archive the threads it created. They stay active and move to the top level of the sidebar.
Archive N Threads shows on parent threads and archives the parent thread and all of its child threads at once. If you don’t want to archive the child threads, choose the plain Archive option instead.
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 threads in an orb or on a shared runner can be made multiplayer, and agent and orb costs are billed to the thread’s owner.

To talk instead of type, join the thread’s Huddle, a voice and video call inside the thread with camera, microphone, and screen sharing.

Artifacts

An artifact is a document attached to a thread that you, your teammates, and the agent edit together. Use one for what people will read: a plan, a report, notes from a call, or findings gathered from several threads. A thread can hold many artifacts, grouped in folders. Artifacts hold headings, lists, checklists, tables, code, images, and interactive views.

Open them from Views → Artifacts in any thread, or ask the agent to write one. A link to an artifact in the transcript opens it in the Artifacts tab. To have the agent write or edit the artifact you are on, use

Ask Amp inside it.

The agent reads and writes artifacts as Markdown with its artifact tool, which every user-selectable agent mode and every Space has. Each save makes a new revision. If someone saved a newer revision while the agent worked, the agent’s update is refused and it merges its change into the newer version instead of overwriting it.

The agent of another thread, such as a child thread, can also edit an artifact when you could edit it yourself, and it then sends the artifact’s thread a message saying what it changed and why.

Share shows which thread's agent made the last edit. An agent can also copy an artifact you can open into its own thread, for example to start the parent's report from a child thread's draft. The copy is a new artifact without the original's comments, and the original stays where it is. Only the artifact's own thread can delete it. Share → General Access sets who can open an artifact's link:

Same Access as Thread (the default): people who can open the thread. The artifact follows later changes to the thread’s visibility.
Workspace Members: members of the thread’s workspace, even if they cannot open the thread. They can read the artifact but not edit it.
Anyone with the Link: anyone, without signing in.

People who can open the thread and belong to its workspace can edit, and so can the owner of a personal thread. A workspace admin can turn off public links for the workspace’s threads by turning off Allow Users to Share Threads and Portals Outside the Workspace or Allow Public Artifact Uploads in workspace settings; existing public links then stop working. The Export tab downloads an artifact as Markdown or HTML, or prints it to a PDF.

Images you add to an artifact are stored with the thread, so only people who can open the thread see them; readers who reach the artifact through a workspace or public link see a broken image. Deleting an artifact keeps its images until the thread is deleted, and deleting a thread deletes its artifacts. Each artifact holds up to 2 MB.