Skip to content

Codex

Run Codex sessions on your computer and drive them from the web client, your Sesame agent, or the terminal, as you would Claude Code.

Install Codex CLI on the computer running Sesame Link, with codex available on PATH. The Codex desktop app does not satisfy the CLI requirement. Check that the CLI is available, then sign in:

Terminal window
codex --version
codex login

Codex sessions don’t need tmux.

In the web client, choose Codex as the runtime when you create a session, or ask your Sesame agent to start one. From the terminal, run:

Terminal window
sesame-link codex "Summarize the failing tests"

This starts Codex in the current folder. Its terminal opens once the session has a first message: pass it as an argument, type it when asked, or send it from another client. Use --model, --reasoning-effort, --sandbox, and --ask-for-approval to configure the session. You can’t change the model or reasoning effort after the session starts.

When you create a Codex session in the web client, open its settings and choose Permissions:

  • Ask me: requests appear in your clients for you to approve or deny.
  • Approve for me: Codex’s automatic reviewer decides without asking you.
  • Full access: unrestricted file and network access with no approval prompts, equivalent to --yolo. This appears only when the computer allows both danger_full_access sandbox policy and never approval policy, with the user reviewer.

Ask me and Approve for me use the workspace sandbox with on-request approvals. Full access requires an explicit choice; allowing it on the computer does not select it for you.

Sessions your Sesame agent starts use Approve for me when the computer allows it.

Terminal window
sesame-link sessions attach <id-or-name>

This opens the session in Codex’s own terminal interface, once its first message has been sent.

End session in the web client stops the session’s work and archives the Codex conversation, keeping its history. See Ending a session for the other ways to end one.