Skip to content

desktop 1.1.10: the socket guard names an unset or missing relay_socket - #151

Merged
khaliqgant merged 2 commits into
mainfrom
fix/socket-guard-wording
Oct 8, 2026
Merged

khaliqgant merged 2 commits into
mainfrom
fix/socket-guard-wording

Conversation

@khaliqgant

@khaliqgant khaliqgant commented Oct 8, 2026 •

Copy link
Copy Markdown
Member

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 ()…", and notes that a stale path means the app isn't running.

Desktop 1.1.9 → 1.1.10. Text only; no behaviour change.

🤖 Generated with Claude Code

View guided diff


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 fd7d2b1. Bugbot is set up for automated code reviews on this repo. Configure here.


Agent Relay sessions

  • claude session 26d00c25 · opened via gh pr create · last active 2026-10-08

The fail-fast check fires both when relay_socket is unset and when it names
a missing or stale socket; the message now says which path it saw
(agentrelay.com#172 review).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Session-Id: 26d00c25-77c9-401f-b9f0-51ce6c9deda6
@khaliqgant

Copy link
Copy Markdown
Member Author

@codex review

@coderabbitai

coderabbitai Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 9fcfeb3c-f976-4237-a52d-c1702a373701
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 8, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-08T17:57:13.351064Z fd7d2b1 Manual request
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Can't wait for the next one!

Reviewed commit: 039c7cac7a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@cubic-dev-ai cubic-dev-ai Bot left a comment •

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

All reported issues were addressed across 3 files

Reply with feedback, questions, or to request a fix.

View guided diff | Re-trigger cubic

Comment thread skills/setting-up-agent-relay-desktop/SKILL.md Outdated
…ays so

test -S passes for a stale socket file a crashed app leaves behind, so the
guard no longer claims the socket is live; the curl after it is what proves
the app answers.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

Session-Id: 26d00c25-77c9-401f-b9f0-51ce6c9deda6
@khaliqgant khaliqgant changed the title desktop 1.1.10: the socket guard names an unset or stale relay_socket desktop 1.1.10: the socket guard names an unset or missing relay_socket Oct 8, 2026
@khaliqgant

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown

Codex Review: Didn't find any major issues. Delightful!

Reviewed commit: fd7d2b12f1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

@khaliqgant
khaliqgant merged commit 41075c4 into main Oct 8, 2026
3 checks passed
@khaliqgant
khaliqgant deleted the fix/socket-guard-wording branch October 8, 2026 19:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant