[Future] Session communication/messaging

[frankbria]

Overview

Allow Claude Code sessions to send messages to each other for better coordination when working on related tasks.

Usage

From Claude Code (via MCP)

// MCP tool: send_session_message
{
  to: 'all' | 'backend-auth' | '<session-id>',
  message: "I'm about to refactor the User model - heads up!"
}

// MCP tool: get_session_messages
{
  since?: string  // ISO timestamp
}
// Returns: { messages: [...] }

From CLI

# Send message
parallel-cc message --to all "Refactoring User model in 5 minutes"

# View messages
parallel-cc messages --since "10 minutes ago"

Use Cases

• Announce major changes
• Request file lock releases
• Coordinate merge timing
• Share discoveries

Database Schema

CREATE TABLE session_messages (
  id TEXT PRIMARY KEY,
  from_session_id TEXT NOT NULL,
  to_session_id TEXT,  -- NULL = broadcast to all
  message TEXT NOT NULL,
  created_at TEXT DEFAULT (datetime('now')),
  read_at TEXT,
  FOREIGN KEY (from_session_id) REFERENCES sessions(id)
);

Implementation Notes

• Messages stored in SQLite
• Polling-based delivery (check every N seconds)
• Optional: Desktop notifications for important messages
• Message TTL (auto-delete after session ends)

Acceptance Criteria

• Send message via MCP tool
• Receive messages via MCP tool
• CLI messaging commands
• Message history persisted
• Broadcast and targeted messages work

Dependencies

• May benefit from [Future] Session naming feature #37 (session naming)

[traycerai]

Warning

Rate limit exceeded. Please try after 1048 seconds.