callsign
NewUnique per-session agent names + iMessage routing for Claude Code and Hermes. Address sessions by name (Frank, Steven, …) instead of one shared trigger.
Summary
, 'Frank' or 'Steven') instead of using a shared trigger.
- It also integrates with iMessage for routing messages to specific sessions, making multi-agent workflows more intuitive and organized.
Install & Usage
mkdir -p .claude/skillsAdd the configuration to .claude/skills/callsign.md
/callsignUse Cases
Usage Examples
/callsign Frank
Assign the name 'Steven' to this session and route iMessage alerts to it.
List all active sessions and their callsigns.
Security Audits
Frequently Asked Questions
What is callsign?
This skill assigns unique, memorable names to each Claude Code session, enabling developers to address agents individually (e.g., 'Frank' or 'Steven') instead of using a shared trigger. It also integrates with iMessage for routing messages to specific sessions, making multi-agent workflows more intuitive and organized.
How to install callsign?
To install callsign: create the skills directory (mkdir -p .claude/skills), then add the config to .claude/skills/callsign.md. Finally, /callsign in Claude Code.
What is callsign best for?
callsign is a community categorized under General. It is designed for: agent. Created by heyfinal.
What can I use callsign for?
callsign is useful for: Managing multiple concurrent Claude Code sessions with distinct identities for parallel tasks.; Routing iMessage notifications to a specific agent session by name for targeted assistance.; Assigning a consistent name to a long-running session to easily resume context and history.; Using named agents in team collaborations where each developer interacts with their own session.; Debugging complex systems by dedicating named agents to different components or services.; Automating workflows that require distinct agent personas for different stages or environments..