desktop 1.1.10: the socket guard names an unset or missing relay_socket
From a cubic P3 on AgentWorkforce/agentrelay.com#172. The fail-fast guard test -S "${relay_socket:-/nonexistent}" fires both when relay_socket is unset and when it names a missing or stale socket (for example, a pointer to a previous app run). Its message said only "relay_socket is not set". It now reads "relay_socket is unset or not a live socket (
Desktop 1.1.9 → 1.1.10. Text only; no behaviour change.
🤖 Generated with Claude Code
[!NOTE]
Low Risk
Text-only skill and package metadata updates with no runtime or setup behavior changes.
Overview
Bumps setting-up-agent-relay-desktop to 1.1.10 in README.md and prpm.json.
The pre-install socket guard in the skill now uses a clearer fail-fast message when relay_socket is unset or when it points at a path that is not a socket file (including stale paths), and it prints the path or unset. Short comments were added to state that test -S only checks for a socket file on disk, while the following curl to /setup/status is what confirms the Desktop app is actually responding.
Documentation and messaging only; the guard logic is unchanged.
Reviewed by Cursor Bugbot for commit fd7d2b12f1f5e6bd6b4f03ba59a91d0caee8e3e8. Bugbot is set up for automated code reviews on this repo. Configure here.
Agent Relay sessions
claudesession26d00c25· opened viagh pr create· last active 2026-10-08