Sessions started by programs

Not every session in a project was opened by you. Codex opens threads of its own to do part of a bigger job, a script may run codex exec or claude -p, a program may call a tool through its SDK, and Grok starts helpers. Those sessions have no title, you never talked to them, and there can be hundreds. The studio keeps them out of your list so it stays yours, and gathers them behind one button.

The robot button

When a project has such sessions, its header shows a button with a robot and their number, beside the other buttons of the project. The number counts all of them, the ones you chose to see and the rest. Pressing it changes nothing in your list. It opens a box called Sessions started by programs.

The box first says in plain words what these sessions are. Then it lists them, newest first. Each row has:

• a name the studio gave it from what it did, and how it ended: Finished, Failed, Stopped early or Unclear;
• when it ran, which tool, and how many messages;
• who started it. For a thread Codex opened for another session, the name of that session, which you can click to open it, and the task it was given. For codex exec, that a script started it;
• Asked: the start of its first prompt, and What it did: a short summary.

Who writes the names and summaries

The project's own subscription writes them, the same Claude Code, Codex or Grok account the project's mail and map use, with a cheap model. The model gets a short excerpt of each run, never the whole transcript: the first prompt, the last answer, how many steps of each kind it took, the names of files it edited. Up to eight runs go in one question.

Each one is written once and kept. It is written again only when the run went on since, or when you change the language of the studio. While the box writes, a row says Summarizing what it did. If the account is signed out or at its limit, the box says why the work waits, lets you choose another subscription for the project, and still shows every first prompt.

Put some of them in your list

1. Press the robot button.
2. Tick the runs you want to see. The ones already in your list come ticked.
3. Press Show in my list. The button reads Hide from my list when you only unticked, and Save my choice when you did both.

The runs you chose stand in your list in a group of their own, Started by programs, under the pinned sessions, each with the robot beside it. One that works or waits for you rises to those groups with its robot, and is never shown twice. A name you give such a session yourself wins over the studio's. To take one out again, untick it in the box.

The iPhone app, which is not out yet, has the same list: a row with the robot among a project's sessions opens a sheet that does what the box does.

A run of a project on another computer is asked of that computer. An agent older than the studio cannot answer, and the box then shows its error. For how the groups of the list are ordered, see How a project's sessions are ordered. For helpers that belong to one of your own sessions, see Helpers and sub-agents.

Small tips

Questions