Skip to content

fix(claude-relay-plugin): align plugin identity and drop the legacy engine pin #91

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
willwashburn wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −5
Open

fix(claude-relay-plugin): align plugin identity and drop the legacy engine pin #91

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .claude-plugin/marketplace.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@
"email": "hello@agent-relay.com"
},
"homepage": "https://agentrelay.com",
"repository": "https://github.com/AgentWorkforce/relay",
"repository": "https://github.com/AgentWorkforce/skills",
"license": "MIT",
"keywords": ["sub-agents", "agent-communication", "inter-agent-messaging", "mcp", "relaycast", "coordination"],
"category": "agent-communication",
Expand Down
5 changes: 3 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,10 +35,11 @@ Package metadata lives in [prpm.json](prpm.json). The repo currently publishes `

## Claude Relay Plugin

Install the [`agent-relay`](plugins/claude-relay-plugin) Claude Code plugin from the marketplace:
Install the [`claude-relay-plugin`](plugins/claude-relay-plugin) Claude Code plugin from the `agent-relay` marketplace, which is published from this repo:

```bash
/plugin marketplace add Agentworkforce/relay
/plugin marketplace add AgentWorkforce/skills
/plugin install claude-relay-plugin@agent-relay
```

## Install Packages
Expand Down
2 changes: 1 addition & 1 deletion plugins/claude-relay-plugin/.claude-plugin/plugin.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"name": "agent-relay",
"name": "claude-relay-plugin",
"description": "Lets your Claude Code sub-agents communicate with each other in real time - send messages, coordinate in shared channels, and work as a team instead of in isolation.",
"version": "0.1.0",
"author": {
Expand Down
1 change: 0 additions & 1 deletion plugins/claude-relay-plugin/.mcp.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,6 @@
"mcp"
],
"env": {
"RELAY_BASE_URL": "https://gateway.relaycast.dev",

@cubic-dev-ai cubic-dev-ai Bot Aug 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2: Removing RELAY_BASE_URL makes the MCP server follow the SDK default host (cast.agentrelay.com), but the plugin's own hooks still default to the old gateway.relaycast.dev host when the variable is unset (in hooks/post-tool-inbox.sh, hooks/stop-inbox.js, and hooks/stop-inbox.ts). So on a fresh install the inbox-polling/stop-guard hooks now talk to a different host than the MCP server — reintroducing the exact config drift this PR is meant to fix. Consider also updating the hooks' DEFAULT_BASE_URL/default fallback to the SDK default (cast.agentrelay.com) so the whole plugin moves with the SDK default, and update the plugin README's env-var table, which still documents gateway.relaycast.dev as the default.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At plugins/claude-relay-plugin/.mcp.json, line 11:

<comment>Removing RELAY_BASE_URL makes the MCP server follow the SDK default host (`cast.agentrelay.com`), but the plugin's own hooks still default to the old `gateway.relaycast.dev` host when the variable is unset (in `hooks/post-tool-inbox.sh`, `hooks/stop-inbox.js`, and `hooks/stop-inbox.ts`). So on a fresh install the inbox-polling/stop-guard hooks now talk to a different host than the MCP server — reintroducing the exact config drift this PR is meant to fix. Consider also updating the hooks' DEFAULT_BASE_URL/default fallback to the SDK default (`cast.agentrelay.com`) so the whole plugin moves with the SDK default, and update the plugin README's env-var table, which still documents `gateway.relaycast.dev` as the default.</comment>

<file context>
@@ -8,7 +8,6 @@
       ],
       "env": {
-        "RELAY_BASE_URL": "https://gateway.relaycast.dev",
         "RELAY_AGENT_TYPE": "agent"
       }
     }
</file context>

"RELAY_AGENT_TYPE": "agent"

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 3, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Keep hooks on the same relay engine as MCP

When a user relies on the defaults and sets RELAY_TOKEN to enable inbox polling, removing this pin makes the MCP server use https://cast.agentrelay.com, but the registered post-tool-inbox.sh and stop-inbox.js hooks still default to https://gateway.relaycast.dev. The env block applies only to the MCP subprocess, so it cannot update those separately launched hooks; consequently they query the legacy engine with a token from the new engine and silently miss messages, defeating both inbox polling and the stop guard. Update the hook defaults (including the TS source) and related plugin documentation as part of this migration.

Useful? React with 👍 / 👎.

}
}
Expand Down