Work with Sessions
Start, follow, organise, and continue work with a Twin agent.
A Session is a durable conversation around one piece of work. It keeps the request, agent activity, messages, outputs, and supporting context together.
Start new work
Choose Agent → New Session, then describe the result you want.
When useful, you can add:
- one or more files;
- a Channel or saved view as context;
- spoken input through dictation; or
- a clear output format.
The workspace creates the work and starts the first run. You can leave the page and return while it continues.
Understand the states
| State | Meaning |
|---|---|
| Waiting | The work has been accepted and is waiting to start |
| Running | The agent is actively working |
| Needs you | A person needs to review or provide something |
| Complete | The current turn has finished |
| Failed | The work could not complete and needs attention |
The exact actions shown depend on the current state. For example, you can stop active work or resume work that has been paused when those actions are available.
Continue the conversation
Send a follow-up in the same Session when the new request belongs to the same piece of work. The agent can use the conversation and permitted context already associated with it.
Create a new Session when the goal, audience, or access context is materially different.
If you want to explore another direction from an earlier message, you can branch from that turn where the feature is available. This preserves the original path.
Review the details
A Session can show:
- the conversation and live progress;
- files you provided;
- files or artifacts produced by the work;
- activity and provenance;
- the capabilities available to the run; and
- links back to supporting Channels or views.
Technical details are there for inspection and support. Most users can focus on the goal, result, evidence, and next action.
See who started the work
Sessions started from the web app, CLI, API, or MCP remain part of the same workspace. MLX shows their origin consistently in the Sessions table, the sidebar preview, and the conversation:
- a person’s avatar identifies the authenticated user;
- an overlapping Codex, Claude Code, Gemini, ChatGPT, or interface badge shows where the action started; and
- the Twin mark appears only when that answer actually retrieved governed Twin data.
Hover or focus any provenance badge for a plain-language explanation. The sidebar preview also separates the Session title and excerpt from its “Started by” attribution, so an icon never has to be interpreted on its own. These marks explain origin and evidence; they do not change identity, permissions, or routing.
Organise your Sessions
Use search and filters to find:
- all Sessions;
- Sessions assigned to you;
- work that needs you;
- running work; and
- failed work.
You can also rename or archive a Session so the workspace remains easy to navigate.
Only one turn runs at a time
If a Session is already busy, wait for the current turn to finish or stop it before sending another follow-up. This keeps the conversation and resulting business changes in a clear order.