skills.rest
Chachamaru127
Chachamaru127COMMUNITY
Explore all skills by this author →
𝕏@vibecoder_japanGitHub

session-send

Send confirmed facts as inbox messages between concurrent agent sessions.

3.1k|302|Updated Dec 12, 2025
Search Tags:#coordination#notification#HANDOFF#InBox#Multi-Agent#session messaging#harness cli
One-click install
npx skills add https://github.com/Chachamaru127/claude-code-harness --skill session-send
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: session-send
Source: https://github.com/Chachamaru127/claude-code-harness/tree/main/codex/.codex/skills/session-send
Command: npx skills add https://github.com/Chachamaru127/claude-code-harness --skill session-send

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When multiple AI agent sessions work in parallel, they often collide on the same files or act on wrong assumptions about each other's changes. This Skill delivers verified facts—completion notices, file-touch declarations, and handoffs—to the correct peer session so agents coordinate without guessing.

Core Features & Use Cases

  • Recipient Resolution: Lists running sessions via bin/harness session list and resolves the correct team and agent columns, avoiding silent delivery failures caused by confusing session_id with agent.
  • Inbox Messaging: Sends structured messages with bin/harness inbox send using team, sender, recipient, subject, and body fields, with sender identity pulled from HARNESS_LIVEMSG_TEAM and HARNESS_LIVEMSG_AGENT environment variables.
  • Send Discipline: Enforces a policy of sending only confirmed facts (completions, declarations, handoffs) and never speculation or unverified claims, based on CooperBench findings that false assumptions cause most multi-agent failures.
  • Use Case: After finishing a refactor of a shared module, notify the other agent session that the file is stable and which areas you will touch next, so it does not edit the same code concurrently.

Quick Start

Ask the agent to notify the other running session that your task is complete and which files you plan to modify next.

Frequently Asked Questions about session-send

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

FAQPage Schema
How do I send a message to another agent session?▼

Run bin/harness inbox send with --team, --from, --to, --subject, and the body as the final positional argument. First list sessions with bin/harness session list to confirm the recipient's team and agent values.

How do I find the correct recipient for a cross-session message?▼

Run bin/harness session list and use the agent column, not the session_id column, as the --to value. Inbox delivery matches on exact team plus agent, and these columns differ during breezing execution.

Why did my session message never arrive without an error?▼

The message was likely addressed to a session_id instead of an agent name. Inbox lookup requires an exact team and agent match, so a mismatched recipient fails silently with no error output.

What information should I send between agent sessions?▼

Send only confirmed facts: completion notices, declarations of files you will touch, and handoffs. Do not send in-progress discussions, guesses, or unverified claims, since false assumptions about peers cause most multi-agent failures.

Can I message a session with empty team or agent fields?▼

No. Empty team or agent columns mean the session has not published its identity yet. Wait for it to announce itself rather than guessing based on similar names.

Related Skills

Explore More Software Engineering Skills→
JKHeadleyJKHeadley
75

agent-identity

Create persistent agent identity files for Claude Code sessions.

Community
Intermediate
naftikonaftiko

Create Inbox Rule

Create inbox rules with sender conditions and forwarding actions.

Official
Intermediate
treygoff24treygoff24
5

swarm-coordinator

Coordinate multiple AI development sessions via a distributed task list and DAG.

Community
Advanced
kriscendobotkriscendobot
3

message-bus

Facilitate asynchronous agent communication via journal-based topic and inbox messaging.

Community
Advanced