troubleshooting · agent

Agent socket path too long

The agent daemon's control socket path is too long for the OS unix-socket limit (a long $HOME is the usual cause), so the daemon can't bind it and the CLI can't dial it.

fix

Shorten $TMPDIR (Shoti falls back to a socket under it) and/or $HOME (Shoti's default location), then retry.

See also: agent-not-running · agent-spawn-failed

agent-socket-path-too-long

Run shoti explain agent-socket-path-too-long to read this offline. Still stuck? hello@shoti.ai.

All topics: shoti.ai/troubleshooting.