Organize and share threads

On this page

Rename and pin threads to keep current tasks easy to find, and move devboxes into folders when a project accumulates many of them. When a teammate needs to see what an agent did, share the conversation with them as a read-only link.

Organize your workbench

Right-click a thread row, or open its ... menu, to rename, pin, mark unread, or archive it. Pinned Template box threads can be reordered. Use Mark unread when you want to return to a conversation later.

You can rename a thread while its devbox is starting. The name will stay after startup finishes.

To group devboxes by task or stage, open the devbox's menu and choose Move to, then a folder. Choose New folder… to create one, No folder to remove the devbox from a folder, or Manage folders… to edit your folders. Folders group entire devboxes and their threads; moving one will not change its files or stop its agents.

You can also ask an agent to organize its devbox. Enable Folder access in Agent permissions first. Each folder's When to use description helps the agent choose the right destination.

Search your threads

To find an earlier conversation by what was said in it, choose the search button beside the back button at the top of the sidebar and type a word or phrase. Search looks through your messages and the agents' final replies in all of your Codex and Claude threads, across every project, including archived and cold-stored conversations. It won't wake a sleeping devbox or Template box.

Each result shows the thread's title, its project, and a highlighted excerpt. Use the arrow keys and Enter, or click a result, to open that thread.

A new reply will appear in search a few seconds after the agent finishes. Search leaves out the agent's progress updates, tool output, and attachments, and it includes only your own threads, not conversations that teammates have shared with you.

If you're a team admin, results can also include threads you started while editing a Team Template. Opening one will take you to the Team Template editor when you have an editing session open, or to the Team Template's page otherwise.

Restore archived conversations

Use Archive thread to hide a finished secondary conversation without destroying its devbox. On desktop, archived conversations stay in the project's thread list under Archived chats; choose Show on that section when you need older work.

The devbox's main row offers Sleep now and Destroy and archive. Destroy and archive will permanently delete the machine's files, so push any commits you need or copy files elsewhere first. See Create and manage devboxes.

After a devbox is destroyed, its archived conversations remain readable without a running machine. Find the conversation under Archived chats and open its menu, then choose Restore thread → To new devbox to continue from the project's latest snapshot or the Team Template's current saved version. Ordinary projects also offer To Template box to continue on the current Template box. Restoring a thread will not recover the destroyed devbox's files.

A History only thread has saved conversation text but no original agent session to reopen. You can read, copy, rename, pin, share, or delete it. Continuing, branching, moving, unarchiving, and restoring are unavailable unless that exact session becomes available again.

You can share a started Codex or Claude thread with people on your boxes.dev team. Drafts, setup threads, and threads that have not started cannot be shared.

Review the conversation before sharing it. The link will include saved messages, commands, tool output, diffs, attachments, and images, including any sensitive content in them. New saved activity will also be visible.
Choose Share thread in the thread header or menu, then choose Share and copy link in the dialog, confirming if asked.
Send the copied link to your teammate. They will need to sign in with an account currently on your team.

Opening the link will add the conversation to your teammate's Shared with me section. On its browser page, Open in app will open it in the desktop app, or the mobile app on a phone or tablet.

Teammates can read the conversation but cannot send prompts, answer approvals, stop the agent, open your workspace or terminal, or control your devbox.

Images already saved with the conversation load without a running devbox. An image linked by its file path on the source machine is different: it appears with an explicit load control, and loading it may wake that devbox and will show the file currently at that path, which may have changed since the message was written.

Copy messages and links

Choose Copy transcript from a thread's menu to copy your messages and the agent's final replies as Markdown. The menu also offers Copy working directory and Copy session ID.

Use Copy share link to invite a teammate. Copy personal deeplink reopens the thread in your own workbench without granting anyone else access. Permanent /thread/ links grant no access by themselves and follow the team's current access rules.

Understand your team's policy

A team admin can choose Thread access in Team settings:

Shared links only: teammates need a share link. This is the default.
Thread titles: teammates can browse titles and request access, but still need the share link to read a transcript.
All threads: teammates can browse and read eligible conversations unless the owner marks one private.

Under Thread titles or All threads, open Teammates' projects in the desktop project selector or mobile Home to browse their work. A devbox your teammate named will appear under that name. Choose Pin to my workbench to keep a thread in Shared with me. Browsing alone will not add it to that list. Remove from Shared with me will remove only your saved row, leaving the conversation and your access unchanged.

Under Thread titles, choose Request access when you want to read a conversation. If you own the thread, accept or dismiss requests in Shared by me. Accepting will make the share link available to the requester; they will need to open it to read the conversation. Access requests do not send email or push notifications.

Open Manage sharing from the thread menu and choose Revoke sharing. This will disable that URL immediately. Sharing again will create a new URL. Archiving will keep a share active; deleting the thread will remove it. If your team uses All threads, teammates will still be able to read the thread through that policy.

Make private will override the team's browsing policy, revoke sharing, remove access requests, and remove the thread from teammates' saved threads and Team work. Sharing the thread again will clear that private setting, create a new link, and restore the team's browsing policy. Under All threads, teammates will be able to read it through that policy as well as through the link.

Read Claude's subagent conversations

Claude's active and recently finished subagents appear above its reply box. Open one to read its conversation, then use Back or Escape to return to the parent thread. The subagent view is read-only, and your unsent parent message will stay in the reply box. Finished subagents leave the list after your next message; older conversations may not have this list.