coordinate-agents

Coordinate a second Sidecar-managed agent through headless shell commands with pinned targets.

1.1k|80|Updated Dec 26, 2025
One-click install
npx skills add https://github.com/marcus/sidecar --skill coordinate-agents
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: coordinate-agents
Source: https://github.com/marcus/sidecar/tree/main/.claude/skills/coordinate-agents
Command: npx skills add https://github.com/marcus/sidecar --skill coordinate-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Running a second AI coding agent alongside your main session often means juggling tmux panes, guessing whether the agent is ready, and accidentally typing into the wrong pane. This Skill provides a safe, ordered workflow for discovering, starting, prompting, waiting on, and answering a Sidecar-managed agent entirely from a shell, with structured refusal codes instead of silent failures.

Core Features & Use Cases

  • Safe agent lifecycle: Discover shells with sidecar shell list and sidecar agent list, create the layout separately with sidecar create shell, then start a provider with sidecar agent start that returns only when the agent is confirmed ready.
  • Pinned prompt-and-wait: sidecar agent prompt --wait submits and waits as one operation pinned to a specific session, pane, process, and provider, returning explicit refusal codes like agent_blocked, agent_replaced, or agent_prompt_stalled.
  • Read before answering: Inspect a blocked agent with sidecar agent read (visible, recent, unwrapped, detection, or transcript sources) before replying with logical keys via sidecar agent send-keys.
  • Use Case: Ask a second agent to review the current diff in a new right-side pane, wait up to two minutes for it to finish, and read its findings — all without disturbing the user's existing layout.

Quick Start

Ask the agent to start a reviewer agent in a new right-side shell pane, prompt it to review the current diff, wait for it to finish, and report the findings.

Frequently Asked Questions about coordinate-agents

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

FAQPage Schema
How do I start a second AI coding agent in Sidecar from a shell?

Create the pane first with sidecar create shell --split right --name reviewer --json, then run sidecar agent start <target> --kind codex --timeout 30s --json. The start command returns only when the provider is positively identified and ready for input.

How do I prompt another agent and wait for it to finish?

Use sidecar agent prompt <target> "your task" --wait --timeout 2m --json. The --wait flag submits and waits as one pinned operation; a timeout is mandatory, and the wait settles on idle, done, or blocked unless narrowed with --until.

Why does sidecar agent list return a feature_disabled error?

Agent control is behind a default-off feature flag. The user must enable agent_control under features.flags in ~/.config/sidecar/config.json; the skill instructs agents to ask the user rather than enabling it themselves.

What should I do when a Sidecar agent wait returns blocked?

A blocked status means the agent is asking a question. Read the screen first with sidecar agent read <target> --source recent-unwrapped, decide on an answer, then reply with sidecar agent send-keys using named keys like enter or down.

Can I use send-keys to type prompt text into an agent?

No. Prompt text must go through sidecar agent prompt, which is bracketed-paste aware and submits correctly. send-keys is only for answering UI prompts with logical keys such as enter, esc, arrows, or ctrl+<letter>.

What are the limitations of Sidecar agent coordination?

Sidecar owns provider identity, readiness, and refusal rules but not raw terminal control or workflow policy; running arbitrary commands in a pane is tmux's job. There is no --force for busy panes, and prompting an already-working agent claims no specific turn.