The list
Each row shows whether the session needs you, whether it is working, the model it runs with the provider’s logo before it, and the project it started in. A project that belongs to one of your agents shows as the agent’s name and icon. The narrow column at a row’s left carries its state:
Under Reduce Motion the indicators stand still.
Order
Choose the order in Settings > Sessions:- Latest turn (the default): a session rises when it appears or someone writes to it, and stays in place while it works.
- Most recent activity: every step of a working session lifts it.
- Started: nothing moves, and new sessions arrive on top.
Nested sessions
Sessions a live session spawns - its subagents, and the agents it consults in other projects - appear nested under it. A Claude subagent is a session of its own, titled by its task, with its own feed; its steps also show once in its parent’s feed. Filters choose only top-level sessions; whatever is nested under a session shown stays under it.Filters and search
The toolbar holds:- Working (bolt): only sessions working, watching or needing input, with their count.
- Unread (inbox tray): only unread sessions. With both on, either kind shows.
- Background (terminal): headless and scheduled runs no interactive session launched, such as jobs a project’s service starts. Off by default.
- Pinned (pin): pinned sessions as their own block above the list. On by default.
- Archived (archive): archived sessions. Off by default.
- The period: Last hour, Last 24 hours (the default), Last 7 days or All time. Sessions that are working, watching or need input show whatever the period.
- The agent filter, listing your agents with their icons.
- Search, by session title and agent or project name.
Pin, archive and read
A session’s header holds, as icon buttons:- Mark as read / Mark as unread: an inbox tray, with an accent dot while unread.
- Pin: keeps the session above the list.
- Archive: hides it unless Archived is on. A working session cannot be archived, archiving makes a session read, and writing to an archived session brings it back.
The session header
Beside the title stand the session’s facts, its model and metrics, and a quiet ID tag; pressing it copies the session’s bare id. The controls on the right:- New session: starts a new session with the same agent in the same harness. ⌘N does the same.
- Open in the source app, for a session started elsewhere.
- Claim session, for a session started elsewhere that no other process runs, so you can talk to it here.
- Read, Pin, Archive and Close.
The feed
A session’s feed reaches its whole history; older parts load as you scroll back. Consecutive tool calls fold into one line that opens onto a step per call, and Expand steps opens them all. A thinking block shows as a closed Thinking line, and a compaction of the context as a quiet marker. Under each message stands its time and, while the pointer is over it, Copy.File preview
Click a file name in a Write or Edit step, or an existing path in a message, and the file opens over the session: Markdown and plans, code, JSON, logs, images and PDFs. Its top bar shows the path, Copy, Open With, Show in Finder and Close. ⌘-click a file on this Mac to show it in Finder at once. An agent’s documents in the database - its context, routines and assets - open in the same preview with their kind, name and version, and Copy and Download.Run a command block
A code block the agent marks as a shell command (bash, sh or zsh) carries Run and Copy at its top right. Run is your consent: the command runs where the session runs, in its working directory on this Mac or on its server. Its output appears under the block as it comes, with Stop while it runs and the exit code at its end. The agent takes the command and its output in with your next message, with nothing else added to the conversation.
Widgets
In the sessions AgentKit runs, an agent can answer with AgentKit’s widgets as well as text. Each widget does one fixed thing, says beforehand exactly what its press will do, and your press is the consent. Its result reaches the agent with your next message. Other surfaces show a widget as plain code. The first widget is Secret: a masked field and Save, which stores the value in the agent’s vault. The value never enters the conversation; the agent learns only that it was saved.Talk to a session
AgentKit is a surface of its own. A session started from an agent’s page runs in the agent’s folder, and its panel ends with a composer. Writing to a session after it ended continues it. AgentKit writes only to the sessions it started or you claimed. Any other session stays readable here and continues only in the surface that started it. AgentKit ends a session’s process after a few idle minutes so it can be continued elsewhere without two writers; your next message continues it.The composer
A box with your text on top and one row of controls under it: the mode on the left, the model on the right, then Send.- Mode: for Claude, every mode Claude has, each with a line on what it does; for Codex, its three approval choices, Ask for approval, Approve for me and Full access. A new session starts in the default from Settings > Claude or Codex; a session continues in the mode it last ran in.
- Model: the models the harness offers, and an effort slider over the levels the model supports.
- Send / Stop: while a turn runs, Send becomes Stop when the box is empty. A message sent during a turn shows as queued and joins the running turn at its next step.
- Pasted or dropped images, screenshots included, join the message as attachments.