v0.1.37

Improved

• When Sesame Link stops with an error, its error report names the step it stopped in, so
  repeated failures at start are easier to diagnose.
• When Sesame Link can't read your login shell's PATH at startup, its error report says why,
  such as a shell Link can't ask, like nologin or tcsh.

Fixed

• A Codex session no longer gets stuck after a turn fails with an error such as Bad Request: it
  returns to idle and sends your next message.
• A computer removed from your account while offline now stops trying to reconnect and reports
  that it was removed, instead of retrying every hour.
• sesame-link start and sesame-link auth login now refuse a --state-directory path that's
  too long, and say why, instead of restarting and failing silently.
• Stop is hidden in the web app whenever a Claude Code or Codex session can't be interrupted, such
  as while a message is still being sent.

Staff preview

• Cursor shell-command and MCP tool approvals can be answered with "always allow" from your phone
  or browser once you set allow_cursor_persistent_rules to true; it's off by default.
• Cursor's file deletion, web search, and MCP tool approvals are no longer missed after the agent
  edits a file, and MCP tool approvals can be answered remotely on Cursor 2026.10.22 or later.
• Cursor sessions no longer hold later messages behind one whose delivery couldn't be confirmed
  once a later message is delivered, and a message sent just as a background task finishes is no
  longer left unconfirmed.

---

sesame-link v0.1.37 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.

v0.1.36

New

• sesame-link config orca on now also makes each Codex terminal Orca opens a Sesame Link
  session, and Orca keeps showing whether it's working, idle, or waiting.
• Pi asks whether to trust a new folder in the web app, the Sesame app, or sesame-link pi, and
  the session starts once you answer. Pi remembers your answer.

Improved

• You can answer Claude Code's "trust this folder?" prompt from your phone or browser even while a
  terminal is attached, as long as nobody is typing in it.
• With sesame-link config claude-mod on, interrupting from your phone or browser stops exactly
  the running turn on Claude Team and Enterprise accounts.
• Sesame Link's secure connections follow the latest certificate authority distrust decisions.

Fixed

• Claude Code sessions whose project folder under ~/.claude/projects is a symbolic link no
  longer show "Stop hook error" after each reply, and can be compacted again.
• Claude Code 2.1.304 no longer shows a "hook was skipped" message in each session with
  claude-mod on.
• A Codex session's history stays readable after a turn is interrupted while one of its commands
  keeps running.
• Pi sessions start on Macs with account names longer than eight characters, instead of failing
  with "Link state directory is too long for a Pi socket".

Staff preview

• Cursor's Auto-review command prompts, web search approvals, and "Delete this file?" prompts can
  be answered from your phone or browser.
• A Cursor session waiting on something only the terminal can answer shows what the terminal
  shows, and a second message sent right after another is delivered in turn.
• Cursor sessions keep taking messages after Cursor summarizes the conversation.
• Cursor sessions on 2026.10.19 and earlier October builds no longer repeat their replies or end
  turns with "WritableIterable is closed"; they show no thoughts. Restart sessions started before
  the update.
• The menu-bar app lists Cursor with the other coding agents.

---

sesame-link v0.1.36 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.

v0.1.35

New

• sesame-link config orca on makes each Claude Code terminal Orca starts a Sesame Link session,
  while Orca keeps showing whether it's working, idle, or waiting.
• sesame-link claude "prompt" sends the prompt once as the first message, and
  sesame-link claude --resume <id> reconnects to that conversation's session or continues it.
• A message stuck behind text left in Claude Code's input box can be released from your phone or
  browser; the cleared text is shown so you can copy it back.

Improved

• Up to 12 sessions run at once by default, up from 8, and stopped sessions no longer count
  toward the limit. A limit you set with --max-sessions is kept.
• A session waiting on a screen Sesame Link doesn't recognize, such as an MCP server approval,
  now shows that screen in your clients instead of sitting silently.
• sesame-link start says when this computer keeps Sesame Link offline while nobody is logged
  in, and on Linux offers to run loginctl enable-linger.
• Claude Code 2.1.303 is verified.

Fixed

• Sesame Link no longer stays offline after Sesame refuses its connection; it keeps retrying,
  and sesame-link status shows when.
• Two copies of Sesame Link signed in as the same computer no longer knock each other offline all
  day; sesame-link status says how to fix it.
• Messages sent from your phone or browser around a /compact, or while you type in the session's
  terminal, are now delivered or held for review correctly instead of getting stuck.
• Idle sessions with a terminal attached no longer make the web client say "Link couldn't confirm
  access to this session right now".
• Approving a plan from your phone or browser no longer fails while Claude is still writing it.

---

sesame-link v0.1.35 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.

v0.1.34

Improved

• When a Codex session can't take a message right now, it says nothing was sent and what helps:
  waiting a minute, forking the session, or restarting Sesame Link.
• On macOS, Login Items in System Settings can list Sesame Link by name with its icon, instead
  of "Sesame AI, Inc.", when the menu-bar app is installed.

Fixed

• A Codex session no longer refuses every message until Sesame Link restarts after an earlier
  message's outcome was unclear; it recovers once the thread shows what happened.
• A fork of a compacted Claude Code conversation no longer holds every message after its first.
  Start a new fork to replace one that is already stuck.

---

sesame-link v0.1.34 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.

v0.1.33

New

• You can fork a conversation into a new session, optionally on another model and in a new Git
  worktree, leaving the original untouched.
• Forks can start from an idle Claude Code or Pi session, a Codex session at any finished turn,
  an ended session, or a conversation you had outside Sesame Link.
• Forks need Claude Code 2.1.296, Pi 1.0.2, or Codex 0.154.0 or newer.

Improved

• sesame-link restart now also restarts Codex after you install a new Codex release, so
  features that need it, such as Codex forks, turn on.
• sesame-link diagnostics no longer overwrites an existing file; move it aside or pass another
  --output.

Fixed

• Messages no longer stay unconfirmed or hold later messages after you submit them yourself in a
  busy Claude Code session.
• Messages reach Claude Code more reliably while Claude has queued messages or has just compacted
  its context.
• A fork's first message no longer stays listed as queued after it appears.
• Workflow agents that were stopped, paused, or cut short are no longer listed as still working.
• sesame-link uninstall right after stop no longer occasionally fails with "Couldn't keep
  Sesame Link stopped".
• Session folders and slash commands are handled more safely.

Staff preview

• Cursor sessions say to run agent login when the Cursor CLI is logged out, in
  sesame-link status, the New session dialog, and at start.
• Cursor Plan mode shows the "Ready to build?" prompt as waiting on the terminal, and later
  messages are delivered after a plan you didn't build.
• Only the terminal can trust a Cursor workspace; remote clients can't answer that prompt.

---

sesame-link v0.1.33 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.

v0.1.32

Improved

• When image storage fills up, new uploads replace the oldest images already sent instead of
  being refused; removed images stay in the message history, marked as removed.

Fixed

• sesame-link update no longer hangs on a build that doesn't answer --version; it gives up,
  reports why, and keeps the installed build.

---

sesame-link v0.1.32 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.

v0.1.31

• Messages from remote clients reach Claude Code sessions in more layouts: in don't-ask mode,
  with a custom status line or pinned notices between Claude's message box and its mode footer,
  and in narrow panes or under a long session title when Claude Code labels the line above its
  message box with ultracode or fast mode. Sessions Sesame Link starts keep Claude Code's
  screen-reader mode off, because its flat layout has no message box Sesame Link can recognize,
  and --ax-screen-reader is no longer accepted as a Claude argument.
• Messages from remote clients no longer sit unsent in a Claude Code session's message box after
  a browser terminal opens on it. Sesame Link's input safeguard no longer leaves behind a tmux
  error that opened tmux's view mode on the session and swallowed the Enter key, and Sesame Link
  now closes view mode before pressing a key. While the session's terminal is in copy mode,
  Sesame Link leaves the key unpressed instead of changing the selection.
• A Codex turn that fails with an error Codex will not retry, such as a model stream lost while
  the computer slept, no longer leaves the session refusing new remote messages until Link
  reconnects or restarts. A Codex session that is refusing messages for another reason now shows
  as degraded after its turn ends instead of appearing idle.
• sesame-link auth login opens a sign-in link that fills in the terminal's code, so you check
  that the browser shows the same code instead of typing it, and starts Sesame Link as soon as you
  are signed in, in the folder you signed in from, instead of asking first; it also starts when
  run outside a terminal. Sign-in and pairing codes are now bold rather than reversed, so
  selecting one to copy it shows the selection.
• Remote updates are on by default: browsers you link can update Sesame Link on this computer
  without being asked first. Turn them off with sesame-link config remote-update off.
• On macOS, sesame-link restart and sesame-link start no longer fail with "Bootstrap failed:
  5: Input/output error" when the previous Sesame Link is still exiting; they wait for launchd to
  finish removing it before registering the new one.
• Sesame Link reports completed and failed turns so remote clients can show which sessions have
  unread results, including when no web browser is connected.
• sesame-link --help and the menu-bar app link to the new public issue tracker at
  https://github.com/SesameAILabs/link/issues, where you can report problems and request features.
• Staff preview, Cursor sessions:
  • Messages from remote clients reach Cursor sessions with Run Everything or Auto-review on, and
    after the session's branch has a pull request open. They used to wait in the queue and never
    arrive, because the mode's label or the pull request number in Cursor's footer stopped Sesame
    Link recognizing the message box.
  • Remote clients can start Cursor sessions with Auto-review, in which Cursor's reviewer runs the
    calls it judges safe and asks about the rest, or Run Everything, which runs every call without
    asking. Run Everything is offered only after you add "run_everything" to
    allowed_cursor_approval_modes in remote-access.json; the setting allows Cursor's own
    prompts and Auto-review by default.
  • Remote clients can answer a Cursor session's command prompts again after the agent has edited
    files, when Cursor shows its review hint under the prompt; under Auto-review, the prompt is
    shown as waiting for an answer in the terminal rather than as a running turn.
  • A Cursor session lists the pull requests it opens with gh pr create or a GitHub integration,
    and the ones whose branch it pushes, as Claude Code, Codex, and Pi sessions do.
  • New Cursor sessions can name themselves with a descriptive title, keeping any name you chose;
    Cursor's own tool approval policy still applies.

---

sesame-link v0.1.31 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.

v0.1.30

• Messages from remote clients reach Claude Code sessions again when Claude Code labels the line
  above its message box, as it does with ultracode on. They used to wait in the queue and never
  arrive, because the label stopped Sesame Link recognizing the message box.
• A Herdr tab Link opens for a new session now closes when the session ends, as Ghostty and
  Terminal windows do, instead of leaving a shell behind.
• Staff preview: sesame-link cursor starts the installed Cursor CLI in the current folder as a
  Sesame Link session, with --mode, and attaches its terminal; Cursor keeps its own model setting.
  sesame-link status lists Cursor, and remote clients can start, message, and interrupt Cursor
  sessions; Cursor's own prompts still decide what runs. A new allowed_remote_runtimes setting in
  remote-access.json lists the tools remote clients may start sessions with, all by default.

---

sesame-link v0.1.30 — macOS binaries signed with Sesame's Developer ID and notarized by Apple; the Linux binary is an unsigned preview. The release's manifest of archives is signed with Sesame's release key, which sesame-link update checks before installing. Public installs use https://storage.googleapis.com/sesame-link/install.sh, which verifies release checksums and the macOS signature.