Skip to content

Sesame agent

Your Sesame agent, the character you call in the Sesame app, can start coding sessions, tell you how they are going, help you answer their questions, and pass along your instructions, across every computer in your account.

  1. Connect at least one computer, if you haven’t yet, by following the Quickstart. Your sessions run there.

  2. In the Sesame app, add the Sesame Link app to the character you want to call. It uses the Sesame account you are signed in to there, so there is no code to enter.

Call the character in the Sesame app and talk the way you would to a colleague; there are no fixed commands. Refer to sessions and computers by name. Anything too long to say aloud, such as a list of sessions or a session’s latest reply, appears on screen in the Sesame app.

Ask for an overview at the start of a call, or whenever you lose track:

“What are my sessions doing?”

“Anything need me?”

Your Sesame agent starts with the sessions that need you most:

Status Meaning
Needs you A question, permission request, or plan is waiting for your decision.
Failed A turn failed in the last half hour or so.
Finished A turn finished in the last half hour or so, or there is news you haven’t heard yet.
Running The session is working on a turn now.
Idle The session is waiting for its next message.
Unknown The computer couldn’t report the session, for example because it is offline.

For each session you hear its name, computer, status, and latest change, such as “Fix login bug on your laptop finished: it says the tests pass.” Your Sesame agent reads up to eight at a time; say “keep going” to hear the rest.

Without focus, your Sesame agent works like a dispatcher: it sums up each session in a sentence and passes your messages along. Focus connects you to one session for a real back-and-forth with Claude, Codex, or Pi, such as working through a design, answering a string of questions, or steering a turn as it runs.

“Focus on Fix login bug.”

While you are focused:

  • You hear Claude, Codex, or Pi directly: your Sesame agent relays their replies in the first person, as in “I’ve finished the migration and the tests pass,” and keeps them short. Code and long output stay on screen.
  • Your words go through as you said them: once you have said enough to act on, your Sesame agent passes along what you said, word for word. It waits while you are still talking, so you can think out loud.
  • Your Sesame agent doesn’t answer for the session: it won’t offer its own plan or opinion about the work. It asks what you mean, or passes your question on and relays the answer.
  • “This session” is implied: “stop”, “what’s it waiting on?”, and “end this session” all apply to the focused session.

A focused conversation might go:

You: Focus on Fix login bug.

Agent: I’m idle. My last change moved token refresh into the session middleware, and the tests pass.

You: Did you check what happens when the refresh token has expired too?

Agent: Not yet. I’ll add a test for it now.

Agent: The expired case logs the user out, but it drops their unsaved draft. Should I save the draft first, or is losing it acceptable?

You: Save it first.

Other sessions keep running while you are focused, and their news waits until you leave focus. If another session needs a decision, your Sesame agent tells you and offers to switch. To leave focus, say “Back to all my sessions,” and it catches you up on the others.

“Start a Claude Code session on my laptop to fix the flaky upload test.”

If you have several computers, or the computer offers more than one runtime, your Sesame agent asks which one. The session opens in the computer’s default workspace unless you name one of its recently used folders. Claude Code sessions it starts use the Auto permission mode; see Permissions and approvals.

“How’s the upload test fix going?”

“Tell the payments session to also cover refunds.”

You can message a session while it is working; the message waits its turn.

“What does the migration session need?”

“Deny it, and tell it to use the staging database instead.”

Your Sesame agent reads out the request and its choices, then submits exactly the choice you make.

“Stop the upload session.”

“End the docs session.”

Stopping interrupts the running turn; the session stays open. Ending removes the session from Sesame Link, and your Sesame agent asks you to confirm first. Ending a Codex session this way doesn’t stop Codex; to stop it too, use End session in the web client. See Ending a session.

“Did any session mention Sentry?”

“What did the old login session decide about retries?”

Your Sesame agent searches your sessions’ history, including sessions that have ended, and tells you what it found and where.

“Which computers are online?”

“Is my desktop up to date?”

After you start a session or send it a message, your Sesame agent keeps an eye on it and tells you when a decision needs you and how each turn ended. Anything that happened between calls is summarized when your next call starts.

You can also send requests from the character’s text chat in the Sesame app. It works like a call, except:

  • There is no focus: name the session each time, for example “tell Fix login bug to run the tests”.
  • News isn’t posted on its own: ask how a session is doing.

Your Sesame agent can’t approve a request it can’t read aloud in full, such as a long plan, the content of a file Claude wants to write, or the arguments of most MCP tools. It tells you what it couldn’t read. Approve those in the web client or at the computer’s terminal; you can still deny them by voice.

Ask your Sesame agent to disconnect from Sesame Link. This removes its access to your computers until you add the Sesame Link app again.