Repository navigation
messaging skill 0.2.1: use agent-relay-sessions tools only when linked to this session - #200
Merged
Merged
Conversation
…d to this session The hosted server sends as the agent name approved when it was connected until its tools are linked, which can be another agent or workspace. Use them only after a join_relay call a note or reply hint gives, or once they are linked. Otherwise stay on the socket route. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars.
|
[Medium impact] The PR appears safe to merge; no actionable issues were found.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Follow-up to #195, for Greptile's open thread there.
messaging-agents-on-the-relaytold a session to use theagent-relay-sessionstools whenever it had them. That server is hosted: until its tools are linked to this session, it sends as the agent name approved when it was connected, which can be another agent or another workspace.The skill (0.2.1) now uses those tools only when they act as this session:
[reply: …]line gives ajoin_relay desktop_address=…call: make it once, then use the tools;[reply: …]line names the tools with nojoin_relay.Otherwise the session stays on the socket route. That route and the
socket-requestfallback are unchanged, and so is the rule that a same-named tool from any other server never counts.The "already linked" signal comes from the core. In
crates/probe/src/relay/hosted_mcp.rs(relay), reply hints carry thejoin_relaytext for a session that may not have linked the tools yet, and leave it out once it has.Versions: skill 0.2.1,
agent-relay-setupcollection 1.2.2.Verified
This is a wording change to the skill, checked against the core's source. It was not run end to end through the MCP route, and no message was sent from a real identity.
Follow-up
AgentWorkforce/relay#2032 pins
RELAY_SKILL_REFto #195's merge commit. Once this merges, the pin moves to this PR's merge commit before #2032 merges.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need.