Skip to content

Orca

Sesame Link works with Orca. Turn it on once, and each Claude Code or Codex terminal Orca starts is also a Sesame Link session. You can steer it from your phone or browser, and Orca still shows whether it’s working, idle, or waiting for you.

Turn it on

Section titled “Turn it on”

With Orca open, run:

Terminal window
sesame-link config orca on

Orca now starts Claude Code with sesame-link claude and Codex with sesame-link codex. New Claude Code and Codex terminals in Orca become Sesame Link sessions. Terminals that are already open stay as they are. You can turn it on before you install either one.

If you already set your own Claude or Codex command in Orca’s Agents settings, Sesame Link leaves it alone and changes neither. Clear it there first, then run the command again.

To go back to plain Claude Code and Codex terminals, run:

Terminal window
sesame-link config orca off

How it behaves

Section titled “How it behaves”
  • When Orca restores a terminal after a restart, it reconnects to the session if it’s still running. If a Claude Code session has ended, Sesame Link continues the same conversation in a new session. A Codex session that has ended can’t be continued: Codex reports that it can’t find the conversation, and you can start a new one.
  • If Sesame Link isn’t running, or is already running as many sessions as it allows, the terminal starts plain Claude Code or Codex instead and says why. You can’t reach that one remotely. The same goes for a Codex terminal started with options Sesame Link can’t pass on, such as -c.
  • Orca’s commit messages and other one-off Codex runs use plain Codex, as before.
  • Closing an Orca terminal doesn’t end its session. Reach it from your phone or browser, or attach it again with sesame-link sessions attach <id-or-name>.
  • Orca’s Chat UI doesn’t use a terminal, so chats you start there aren’t Sesame Link sessions.
  • Only Claude Code and Codex terminals are covered for now. Pi and Cursor terminals in Orca start as usual.