A session is a live, multiplayer run where you and your teammates work with an agent in real time. You send messages, the agent takes turns implementing your requests, and everyone in the session sees progress as it happens. Reach for a session when you want to explore and steer as you go, rather than hand off a fully-specified task.
Talking to the agent
The composer has two modes:
- Agent mode — every message you send is an instruction to the agent.
- Chat mode — messages are normal team chat; mention
@agentto direct a message at the agent.
This lets a group discuss in chat and then instruct the agent deliberately, or switch to agent mode for focused back-and-forth.
Turns and queuing
The agent works one turn at a time. If you send more instructions while it’s working, they queue — the composer shows a “queued” count — and run in order. When the agent is running you can Stop it to interrupt the current turn.
Participants
A session shows the participants who have joined, so you can see who else is in the room. The roster persists for everyone who has taken part.
Working views
Alongside the conversation, a session gives you several views of the work:
- Preview — a live preview of your running application (with a process switcher and address bar when your app exposes more than one process).
- Resources — external resources provisioned for the session, such as a database branch.
- Files — a read-only browse of the sandbox filesystem.
- Diff — the changed-files diff for the working branch.
Repositories & pull requests
A session works on a branch in your connected repo. You can Open PR when you’re ready, and the session shows the pull request’s status (open, draft, merged, closed) with a link to GitHub. Multiple repositories and PRs are supported in a single session.
See the Start a live session guide for a walkthrough.