director

Inventory agent sessions across harnesses and track blocked asks and stranded outputs.

1|Updated Sep 10, 2026
One-click install
npx skills add https://github.com/ArcavenAE/director --skill director-arcavenae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: director
Source: https://github.com/ArcavenAE/director/tree/main/skills/director
Command: npx skills add https://github.com/ArcavenAE/director --skill director-arcavenae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? When you run many parallel AI agent sessions across harnesses like Claude Code, codex, opencode, and crush, sessions die holding unanswered questions and completed work never reaches you. This Skill sweeps the session inventory, ranks what is blocked on your attention, and keeps custody of outputs and asks that would otherwise be lost. ## Core Features & Use Cases - Session Sweep: Runs scripts/dsi to regenerate a cross-harness session inventory and presents a strict one-line-per-item list of what is blocked on you, what is stranded, and what is running. - Standing Coordination: Adopts a standing role that relays messages between sessions, re-sweeps after relay activity, and captures requirements as it works. - Requirements Harvest: Promotes hardened observations from capture notes into a requirements register with source classes (OBSERVED, JUDGMENT, RULED). - Use Case: After a weekend of parallel work across nine sessions, ask what is waiting on you and get a ranked list of blocked asks, stranded sessions that died mid-question, and uncaptured outputs. ## Quick Start Adopt the director role and run a sweep to tell me what is blocked on me across all my agent sessions.

Frequently Asked Questions about director

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

FAQPage Schema
How do I see what my agent sessions are waiting on?▼

Run a director sweep, which executes scripts/dsi to rebuild the session inventory and presents a ranked list of asks blocked on you, stranded sessions whose questions died with them, and sessions still running. Detail on any item is available by number on request.

How to coordinate multiple AI coding sessions across different harnesses?▼

Adopt the director role in standing mode: it sweeps the inventory, relays messages between sessions, tracks unanswered asks, and captures requirements continuously. It reads sessions from Claude Code, codex, opencode, and crush stores, though only Claude Code currently exposes presence or a message address.

Can I message codex or opencode sessions directly?▼

No. The measured adapter capability table shows only Claude Code exposes presence and an inbox address; codex, opencode, and crush can be read but not reached. Any plan that assumes a session can be messaged must first check the address field on its record.

What happens to work when an agent session dies?▼

Without custody, outputs and unanswered asks are lost when a session's process ends. The director sweep surfaces these as Stranded items, and uncaptured outputs are written to board.md under Uncaptured so nothing produced is dropped.

Why does cross-host messaging fail silently in this setup?▼

An agent:// address aimed at a remote host is delivered to the local inbox instead, silently, because agent:// does not cross hosts. Cross-host sends must use the global:// tier, and accepted-for-delivery only means the bus took the message, not that it was read.