# Multi-agent sessions

In Foxora, each agent gets its own session — multi-agent means multi-session. Switch the lead and you switch threads; run several at once and watch one of them live on the Stage, right next to the conversation you're driving.

## One agent, one session

Switching the lead agent doesn’t reuse the current thread — it opens that agent’s own session. Each agent keeps a separate transcript and memory den, so nothing leaks between them: your research agent never sees your refactor agent’s scratch work, and vice versa.

> Why a fresh thread?Bleeding two agents’ context into one transcript muddies both. Giving each its own session keeps memory clean and makes each one’s history easy to follow.

## Running several at once

Because sessions are independent, you can have several running in parallel. A session that’s working keeps going while you switch to another; the sidebar floats anything working or waiting on you to the top, and surfaces a marker when a background run finishes or needs you. See session status.

## A second session on the Stage

To watch two conversations at the same time, open one on the Stage. From a session’s row menu choose Open in Stage — that session mounts as a live conversation on the right, with its own stream, history, and composer, while you keep driving the main one on the left.

> Delegate, then watchHand a long task to one agent, open its session on the Stage, and keep working in the main conversation. You see its progress without losing your own place. To learn how a lead delegates to a crew under the hood, see Agents & crews.

### When the Stage view isn't available

Mounting a second session on the Stage needs a build that injects the conversation renderer. Where that isn’t available, the Stage shows a short notice instead of the embedded session — everything else about the session keeps working.