msg-cli-agents

Send messages between Claude Code CLI sessions with file-based delivery and session ID signing.

Updated Feb 10, 2026
One-click install
npx skills add https://github.com/ammonfife/sakima.co --skill msg-cli-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: msg-cli-agents
Source: https://github.com/ammonfife/sakima.co/tree/main/.claude/skills/msg-cli-agents
Command: npx skills add https://github.com/ammonfife/sakima.co --skill msg-cli-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a robust system for sending messages between Claude Code CLI sessions, facilitating communication and coordination among active sessions.

Core Features & Use Cases

  • Inter-session Messaging: Enables message passing between CLI sessions, allowing for task handoffs and coordination.
  • Fallback Delivery Methods: Supports file-based inbox system (preferred) and Terminal osascript injection for flexibility.
  • Session ID Signing: Ensures messages are received by the intended recipients.
  • Use Case: A developer can send a task update to all open CLI sessions without manually notifying each one, enhancing collaboration.

Quick Start

To send a message to all other sessions, use the following command:

echo "[Session <sender-id> → ALL OTHER SESSIONS] <message>" >> ~/.claude/projects/-Users-benfife/.inbox

Frequently Asked Questions about msg-cli-agents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I send messages between Claude Code CLI sessions?

To send messages between Claude Code CLI sessions, you can use an inter-session messaging solution that passes information via a file-based inbox system or Terminal osascript injection. This enables task handoffs and coordination without manual notification.

What is the best way to coordinate task handoffs across multiple CLI instances?

The best way to coordinate task handoffs across multiple CLI instances is using inter-session messaging with session ID signing. This ensures messages are securely received by intended recipients during active workflow integration.

Can I broadcast a task update to all open CLI sessions at once?

Yes, you can broadcast a task update to all open CLI sessions by appending a message to a shared file-based inbox. This allows a developer to notify all active sessions simultaneously for enhanced collaboration.

Does inter-session messaging for CLI require any external dependencies?

No, inter-session messaging for CLI requires no external dependencies. It supports fallback delivery methods natively, utilizing file-based inboxes and script-based injection to facilitate communication.

Why does inter-process communication between CLI sessions need session ID signing?

Inter-process communication between CLI sessions needs session ID signing to ensure messages are received by the exact intended recipients. This security measure prevents unauthorized sessions from intercepting task handoffs.

When should I use file-based inboxes versus osascript injection for session messaging?

You should use file-based inboxes as the preferred delivery method for reliable session messaging, switching to Terminal osascript injection as a fallback when direct file access is unavailable or constrained.