Skip to main content
Every agent session gets a title you can read at a glance in the Sessions list, and a short summary at the top of its page. Both are written for you once the session has settled. A name you give a session always wins over both. This works the same in the web app and the desktop app.

What you see

  • The Sessions list shows one title per session: the main work it did, such as “Fix flaky ingest test” or “Explain how Local syncs issues”. Rest the pointer on a title for a moment to see its summary without opening it.
  • A session’s page opens with one line on what happened, then a few short points: what changed, what was found, what was decided, what is still open. It sits above the tabs, so you read it first whichever tab you are on. Choose Hide details to keep just the line; your choice is remembered on that computer. A point with a source mark opens the message it came from.

Where a title comes from

Orchestra uses the first of these that the session has:
  1. The name you gave it. See Renaming a session.
  2. The title Orchestra writes when it summarizes the session. It names the work the session did, not just what it was first asked. A session that moved on to other work is named after the work it spent the most time on.
  3. The title the agent gave it, or its first request, cleaned of pasted text markers and long instructions, until the session is summarized.
A placeholder such as Claude Code in my-repo is only shown when nothing better exists yet.

Renaming a session

Click the title at the top of a session’s page (or press F2), type a name and press Enter. In the Sessions list, open a row’s menu and choose Rename. Your name shows everywhere the session’s title does, for everyone who can see the session. A new summary never replaces it. Clear the name to go back to Orchestra’s title.

When the summary appears

A session is summarized once it settles: about 15 minutes after its last message, or as soon as it ends. It is read again later if it grows. Sessions with only a few messages are not summarized and keep their first title. A session that only answered questions or reviewed something still gets a title and a summary.

Two summaries, one for people and one for agents

The summary at the top of the page is written for people. The Outcome tab keeps the detailed version agents use when they pick up the work: what the session concluded, the decisions made, what is still open and the dead ends, each linked to the messages that say so. A session that concluded no work, such as one that answered a question, has no outcome there.

On Orchestra Local

Summaries on Local are written with your own model key or the subscription you said yes to. With neither, a session gets a plain summary taken from its own text: what you asked, which files changed and how it ended. See Local or hosted. A teammate’s session that reached you through your repository’s git shows the title it had when they last published it.