Skip to content

Pi session fails with default state directory: "Link state directory is too long for a Pi socket" #8

Closed

Description

@leandro4979-hub

What happened

Creating a Pi session in the web client failed with HTTP 400 bad_request:

Link state directory is too long for a Pi socket · Link status 400 · bad_request

Expected: Pi sessions start with the default state directory (~/.local/state/sesame-link). Link was connected and Pi was reported ready.

The default state directory expanded to 47 bytes. The generated /sessions/<36-character-UUID>/control.sock suffix adds 60 bytes, giving a 107-byte socket path. This appears to exceed the macOS Unix-domain socket path limit.

Verified workaround: stop Link, move its existing state directory intact to ~/.sl, leave a compatibility symlink at the old location, then start Link with --state-directory "$HOME/.sl". The resulting control.sock path is 85 bytes. A new Pi session then reached Ready in the web client with the message composer enabled; the local tmux session remained running after detaching. Existing sign-in was retained.

Please consider a shorter socket directory independent of the state directory, or an actionable preflight check. Doctor did not flag this path-length problem. No raw logs, credentials, or session content are included.

Steps to reproduce

  1. Install Sesame Link 0.1.35, Pi 1.3.0 and tmux 3.8 on macOS Apple Silicon.
  2. Sign in and start Link using its default state directory under a home directory where the expanded state path is 47 bytes.
  3. Confirm Link is connected and Pi reports ready.
  4. Create a Pi session from link.sesame.com.
  5. Observe HTTP 400 bad_request with the socket-path error above.
  6. Use a shorter state directory as described above and create a new Pi session: it reaches Ready.

Sesame Link version

0.1.35

Computer running Link

macOS, Apple Silicon

Operating system version

macOS 27.2

Coding tool

Pi

Coding tool version

Pi 1.3.0; tmux 3.8

Where you saw it

Web app on a computer

Output of sesame-link status

Sanitized summary after the workaround (not raw command output):
Sesame Link: running
Connection: connected
Pi: ready, 1.3.0
Version: 0.1.35, up to date
Starts at login: yes

Activity

  1. added
    bugSomething doesn't work as it should
    needs-triageNot yet looked at by a maintainer
    on Oct 21, 2026
  2. darkmirage commented on Oct 22, 2026

    @darkmirage
    Contributor

    Thanks for reporting this, and for the clear write-up and workaround. They made it quick to fix.

    It's fixed in Sesame Link 0.1.36: Pi sessions now start with the default state directory, whatever your account name's length. Run sesame-link update to get it. Your current setup with the shorter state directory keeps working, so there's nothing else to change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions