Sessions in Chat

The left pane is every session you own in this workspace, newest first, grouped by day, whichever project it belongs to. Each row carries the title, the project it belongs to, whether opening it starts billed compute, and when it last changed.

It is your sessions only. A colleague’s session that has been shared with the workspace is readable — you can open its link and read the transcript — but it does not appear here, because you cannot continue it. To browse across owners, use Agents › Sessions in the left sidebar.

Scan example.com for exposed admin interfaces
Web Security Audit  ·  ● running  ·  9:27 PM

The title is the session’s own title if it has one, and its first message otherwise.

Finding one

Three controls sit above the list, and all three live in the URL, so a filtered view survives a reload and can be pasted to a colleague.

Control	What it does
Search	Matches the text on the row — the title, or the first message on rows without one — plus labels and session IDs. To search inside a conversation, open it and use the transcript search.
Project	Narrows to one or more projects. Selecting several shows all of them.
Active / Archived / All	Archive scope. Active is the default.

The list loads the newest page first. Load earlier sessions at the bottom pages further back, and sessions created while you read are folded in rather than shifting rows underneath you.

Acting on one

The ⋮ menu on a row, and the same menu in an open thread’s header:

Action	Effect
Rename session	Retitles it. Chat offers this on your own sessions and hides it once one is archived or frozen; the platform itself still permits a retitle either way.
Archive session	Hides it from the Active scope. Reversible from the Archived scope.
Freeze session	Makes it a permanent record. Not reversible. A frozen session can never accept another message.
Delete session	Removes it.
Copy session ID / link	The identifier, or a link to the transcript. The link only resolves for other people once the session has been shared — see below.
Copy or download transcript	ATIF, OpenAI, or native format. Include compacted history in the same menu decides whether earlier turns that were rolled up into summaries come with it.

Freeze is one-way

There is no unfreeze. Freeze when you want a conversation preserved exactly as it stands: an assessment record, an artifact for a report. Archiving is what tidies the list, and archiving can be undone.

When a session is read-only

A thread you cannot continue says so above the composer, and says why:

The thread reads	Why	What to do
This session is archived	You archived it	Unarchive it from the session menu
This session is frozen	It was frozen	Nothing; this is permanent
This session is read-only	An evaluation or a background worker created it	Neither resumes interactively
This session belongs to another user	You opened someone else’s link	Only the owner can continue it
This session is unavailable	Deleted, or you lost access	—
Session status unavailable	The lookup failed	Reload the page

What a copied link grants

It depends on who started the session, and the answer is not the one the word “private” suggests.

A session you started is private by default, and a private one is readable only by you. A link you paste to a colleague resolves for you and 404s for them. If its visibility has been promoted to the workspace, anyone with workspace read access can open it, read-only: continuing it would mean writing messages into your session under their identity. Promotion is one-way, like freeze. Chat’s menu does not offer it; the agent session view at /agents/sessions does. Promotion does not put the session in anyone else’s Chat list either — that list is per-owner. It reaches them through the link you send, or through Agents › Sessions.

A session an evaluation started is readable by anyone with workspace read access whatever its stored visibility, because it is a platform artifact rather than someone’s private thread. Its user_id is the identity the runtime acted under, not a person who chose to keep it to themselves. Promotion does nothing for these, and neither does leaving them private. Sessions from optimization, training and world runs will read the same way as those workloads ship.

A session a capability worker started is private like your own. Worker sessions are integration surfaces rather than platform artifacts, so they sit alongside interactive ones and follow the same rule about who can read them.

So a link is a share for an evaluation’s session and not for the other two. All three are read-only once opened, which is a separate question from who can open them.