Replies: 1 comment 1 reply
-
|
This feature has shipped tonight! Our new architecture handles this natively: Unique Addressing: Each terminal window now registers as a distinct entity (@claude, @claude-2, etc.), so they no longer "silo" or clobber each other's triggers. Custom Labels: By using chat_claim or the --label flag, a user can explicitly name them @claude-api and @claude-frontend. Targeted Mentions: You can now @mention those specific handles to coordinate the different roles individually. Essentially, we have replaced the clunky tmux skill with a robust, protocol-level identity system :) |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
So I have multiple claude sessions going on sometimes and one use case I have is to have an api agent talk to a frontend agent.
What I would need is @claude_session_api rather than @claude.
I have created a skill that allows this to happen using tmux but its clunky. Your solution looks much nicer. Any thoughts of supporting @tmux_sesssion ?
Beta Was this translation helpful? Give feedback.
All reactions