Skip to content

messaging skill 0.2.1: use agent-relay-sessions tools only when linked to this session - #200

Merged
khaliqgant merged 1 commit into
mainfrom
fix/messaging-skill-linked-mcp-only
Oct 31, 2026
Merged

khaliqgant merged 1 commit into
mainfrom
fix/messaging-skill-linked-mcp-only

Conversation

@kjgbot

@kjgbot kjgbot commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

What

Follow-up to #195, for Greptile's open thread there. messaging-agents-on-the-relay told a session to use the agent-relay-sessions tools 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:

  • a session note or [reply: …] line gives a join_relay desktop_address=… call: make it once, then use the tools;
  • or they are already linked: this session made that call, or a [reply: …] line names the tools with no join_relay.

Otherwise the session stays on the socket route. That route and the socket-request fallback 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 the join_relay text 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-setup collection 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_REF to #195's merge commit. Once this merges, the pin moves to this PR's merge commit before #2032 merges.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need.

…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>
@coderabbitai

coderabbitai Bot commented Oct 31, 2026

Copy link
Copy Markdown

Important

  • Trigger review

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

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 238bbd91-9bd0-4a90-9449-1fe07358518f
  • Autofix · 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

@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

@greptile-apps

greptile-apps Bot commented Oct 31, 2026 •

Copy link
Copy Markdown

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Restricts agent-relay-sessions tools to cases where the session has evidence that they use its identity.

  • The messaging skill uses hosted tools only when they are linked to this session.

Acknowledged intent: kjgbot explicitly states that sessions without linking evidence must stay on the socket route.

Reviews (1) · Last reviewed commit: "messaging skill 0.2.1: use agent-relay-s..." · Reviewed by Greptile

@khaliqgant
khaliqgant merged commit 88fdbef into main Oct 31, 2026
4 checks passed
@khaliqgant
khaliqgant deleted the fix/messaging-skill-linked-mcp-only branch October 31, 2026 06:05
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.

2 participants