Sessions

A session is one Claude Code, Codex, or Pi conversation, running on one of your computers in one folder. Every client signed in with your Sesame account can see it and work in it. Each message you send starts a turn: the agent’s work in response, until it replies and waits for you.

Runtimes

Each session runs one coding runtime:

• Claude Code: fully supported. Each session runs in its own terminal on your computer, so you can attach to it and see exactly what Claude shows.
• Codex: a preview.
• Pi: a best-effort preview. Native dialogs must be answered in its terminal.

Folders

Every session runs in a folder on its computer. The folder you started Sesame Link in, usually where you ran sesame-link auth login, is the computer’s default workspace. New sessions open there unless you choose another folder, and recently used folders are offered first.

To change the default workspace, restart Sesame Link from the new folder:

sesame-link stop
cd ~/code/other-project
sesame-link start

Sessions use the PATH your login shell sets up, so they find the same node, python, and other tools as your terminal.

Sharing a session

All of your clients can use the same session at the same time.

• Messages: a message you send while the agent is working goes straight to Claude Code 2.1.247 or later, or to Codex or Pi, which can fold it into the running turn or take it next. With an earlier Claude Code it waits in a queue until the turn ends, and you can cancel it until then.
• Prompts: in Claude Code and Codex, a permission prompt appears on every client that has the session open. The first answer wins.
• Names: the coding agent names each session after its task. Rename a session from any client, and every client shows the new name.

Ending a session

Ending a Claude Code session closes its terminal, however you end it. The conversation stays in Claude Code’s history, so you can resume it with claude --resume on its computer.

For a Codex session, what ending keeps depends on how you end it:

• End session in the web client stops its work and archives the conversation, keeping its history.
• Asking your Sesame agent to end it removes it from Sesame Link only; Codex may keep working.
• sesame-link sessions delete deletes the conversation permanently.

Ending a Pi session stops its process. Its saved conversation stays on the computer in Pi’s history. Disconnecting a terminal or restarting Sesame Link leaves Pi running.

Limits

• A computer runs up to 8 sessions at once. To allow more, up to 64, start Sesame Link with sesame-link start --max-sessions <number>.
• A computer won’t start a new session while it has less than 1 GiB of memory free.
• A single message can be up to 64 KiB.