send

Inject messages into running dev-team Claude Code sessions via osascript keystrokes.

1|Updated Jun 13, 2026
One-click install
npx skills add https://github.com/apireno/agent-workflow-template --skill send-apireno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: send
Source: https://github.com/apireno/agent-workflow-template/tree/main/.claude/skills/send
Command: npx skills add https://github.com/apireno/agent-workflow-template --skill send-apireno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When orchestrating multiple AI dev-team sessions across Terminal windows, you often need to pass a follow-up instruction, answer a question, or relay VP review feedback to an already-running session. Spawning a new session reloads conversation history and costs tokens; this Skill delivers the message directly into the live session's input box as if a human typed it. ## Core Features & Use Cases - Direct message injection: Sends text into a recorded Terminal window via osascript, resolved by repo name, suffix alias, or a bare numeric window id for windows with no repo binding. - Focus-guarded delivery: Delegates keystrokes to qa-send.sh, which verifies Terminal is frontmost and the target window is correct before typing, so nothing lands in the wrong application. - Delivery verification: Distinguishes PROCESSED, DELIVERED, SUBMITTED BUT NOT PROCESSED, and NOT CONFIRMED outcomes by checking the session transcript, so queued-and-dropped messages are never reported as read. - Use Case: After /peek shows the tuner dev team blocked on a question, run /send acme-service-a with the answer, then /peek again to confirm the team resumed work. ## Quick Start Ask the agent to send a follow-up instruction to a running dev team, for example: tell the acme-service-a dev team to validate PRD-114 first.

Frequently Asked Questions about send

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

FAQPage Schema
How do I send a message to a running Claude Code session?

Use /send with the repo name and your message, for example /send acme-service-a please validate PRD-114 first. The skill resolves the repo's recorded Terminal window and injects the text via osascript as if typed at the prompt.

How do I message a Terminal window that has no repo binding?

Pass a bare numeric window id as the first argument, such as /send 12345 your message. List available ids with bash scripts/cto/window-peek.sh list. This covers second sprints on the same repo, QA drive windows, or sessions without registry entries.

Why did my message fail to send with a focus-guard error?

The focus guard aborts when Terminal is not frontmost, the front window is not the target id, the window id is stale, or Accessibility permission is missing. Nothing is typed anywhere in these cases; fix the cause and retry.

What is the difference between DELIVERED and PROCESSED delivery verdicts?

PROCESSED means the message appears in the session transcript and was actually read. DELIVERED only means it left the input box; queued messages have been observed dropped at turn end, so never report anything below PROCESSED as read.

When should I use /send instead of resuming a dev-team session?

Use /send when the session is already running and you only need to pass a follow-up instruction or answer. It avoids the new-session spawn, conversation-history reload, and token cost of resuming, making it the cheaper path for quick interventions.