Menu
Cross-session agent session messaging via claude-peers-mcp broker
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Pre-action boundary checking — validates agent tool calls against declared capabilities and task contracts
Auto-detect project context and optimize harness — deactivate unused agents/skills, suggest missing experts, generate project profile
Multi-LLM adversarial consensus loop — 3+ LLMs compete to find flaws in designs/specs until unanimous agreement is reached
Monitor Claude Code releases and auto-generate GitHub issues for each new version
Execute OpenAI Codex CLI prompts and return results
YAML-based DAG workflow engine with topological execution and failure strategies
| name | peer-messaging |
| description | Cross-session agent session messaging via claude-peers-mcp broker |
| scope | core |
| user-invocable | false |
Enables cross-session coordination between multiple GPT Codex + OMX sessions through the claude-peers-mcp broker. Complements Agent Teams (R018, intra-session) with inter-session messaging.
| Scope | Mechanism | Tools | Use Case |
|---|---|---|---|
| Intra-session agents | Agent Teams (R018) | TeamCreate, SendMessage | Single session multi-agent collaboration |
| Cross-session instances | claude-peers-mcp | list_peers, send_message | Multi-terminal/project real-time coordination |
| Cross-session memory | claude-mem | save_memory, search | Async memory persistence |
Important: R018's
SendMessageand claude-peers-mcp'ssend_messageare different tools with different scopes. Do not confuse them.
| Tool | Purpose | oh-my-customcodex Scenario |
|---|---|---|
list_peers | Discover active agent sessions | omcodex:status system overview |
send_message | Send message to peer | Cross-project workflow coordination |
set_summary | Broadcast current task summary | DAG cross-project step sync |
check_messages | Read incoming messages | Receive coordination signals |
Terminal A runs auto-dev on project-1; Terminal B works on dependent project-2. Peers coordinate via messages when blocking dependencies are resolved.
Share test infrastructure state between projects running concurrent test suites.
dag-orchestration cross-project steps can use peer messaging for synchronization (currently impossible without this tool).
# Install broker (optional MCP server)
npm install -g claude-peers-mcp
# Add to MCP config
claude mcp add claude-peers-mcp -- npx claude-peers-mcp
omcodex:status (peer discovery)