Skip to content

docs(manage-channels): warn against agent-shared with per-thread channels#2376

Open
ira-at-work wants to merge 1 commit into
nanocoai:mainfrom
ira-at-work:fix/manage-channels-agent-shared-warning
Open

docs(manage-channels): warn against agent-shared with per-thread channels#2376
ira-at-work wants to merge 1 commit into
nanocoai:mainfrom
ira-at-work:fix/manage-channels-agent-shared-warning

Conversation

@ira-at-work
Copy link
Copy Markdown

Summary

  • Adds a one-line warning to the agent-shared option in the isolation question: don't use it when the same agent group also has per-thread channels (e.g. GitHub), as an active PR session will absorb DMs and reply on the wrong channel.
  • Updates the shared description to call out Signal DM / Telegram as the right fit.

Test plan

  • Read through and verify the guidance is accurate and actionable

🤖 Generated with Claude Code

…nels

agent-shared routes incoming messages to any active session for the agent
group, including per-thread GitHub PR sessions, causing DMs to be answered
as PR comments. Note the pitfall and recommend 'shared' for personal chat
channels (Signal DM, Telegram) when GitHub is also wired.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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