Skip to content

Agentic CLI: IPC socket path exceeds macOS sun_path limit (104) on long usernames #1034

@husqD

Description

@husqD

Describe the bug

The RocketSim agentic CLI cannot connect to the app on macOS accounts with a moderately long home-directory path.
Every CLI command (screen, status, doctor, elements, …) fails with:

{"error":{"code":"internal_error","message":"IPC socket path exceeds the maximum allowed
length."},"ok":false,"rs":"1"}

The app process is running and a simulator is booted, but status reports ipc_reachable: false / rocket_sim_running:
false, and no ipc.sock is ever created in the group container — so the app itself can't bind the socket either.

The IPC socket path is built from the app group container:
/Users//Library/Group Containers/4QMDKC8VLJ.com.swiftlee.RocketSim.group/ipc.sock
The fixed portion (everything except ) is already 81 characters. macOS sockaddr_un.sun_path is capped at
104 bytes, so any username ≥ 24 characters pushes the full path over the limit and the bind/validation fails.

To Reproduce

Steps to reproduce the behavior:

  1. Use a macOS account whose short-name is ≥ 24 chars, e.g. alexandra-martinez-iglesias (27 chars). Resulting socket
    path is 108 chars: /Users/alexandra-martinez-iglesias/Library/Group
    Containers/4QMDKC8VLJ.com.swiftlee.RocketSim.group/ipc.sock
  2. Boot a simulator (e.g. iPhone 17) and launch the app under test.
  3. Open the RocketSim app (it stays running).
  4. Run rocketsim screen (or rocketsim doctor) → see error IPC socket path exceeds the maximum allowed length.

Expected behavior

The CLI connects to the app regardless of home-directory/username length. The IPC socket is created and rocketsim
screen / elements / interact work. doctor reports ipc_reachable: true.

Screenshots

N/A — CLI-only, raw output included above.

Desktop (please complete the following information):

  • OS: macOS 26.x (Darwin 25.x), Apple Silicon
  • Version: RocketSim CLI v16.0.3 (build 317); app group 4QMDKC8VLJ.com.swiftlee.RocketSim.group

Additional context

Confirmed it is NOT worked around by: overriding TMPDIR (path isn't derived from it); installing the CLI symlink via Settings → CLI & Agent (only symlinks the binary); no env var/flag found to relocate the socket.

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions