from session-orchestrator46
Orchestrates repeated agent-driven sessions automatically with configurable kill-switches and resource-adaptive concurrency to run routine work without continuo
Autopilot adds a top-level controller that repeatedly starts session workflows (session-start → session-plan → wave-executor → session-end) when the Mode-Selector reports sufficient confidence. It enforces post-session and pre-iteration kill-switches (spiral, failed-wave, carryover > 50%, max-hours, resource overload, etc.), writes an autopilot.jsonl record per invocation, and adapts agents-per-wave based on resource signals.
Use Autopilot when you have many routine, repeatable sessions (e.g., mechanical refactors, repeated follow-ups) where human attention is costly. Invoke /autopilot to let the controller run N iterations with safety gates. Prefer it for workflows with reliable Mode-Selector signals and existing session lifecycle tooling.
scripts/lib/autopilot.mjs (kill-switch enforcement and JSONL writer).--max-sessions, --max-hours, --confidence-threshold, --dry-run), dependency injection contract for modeSelector, sessionRunner, resourceEvaluator, and peerCounter, and atomic iteration semantics.Best suited for Claude/Claude-Code style coordinator agents and workflows that integrate with the repository's session lifecycle. Integrates with agentic orchestration tools that can run /session and produce sessions.jsonl entries.
This skill has not been reviewed by our automated audit pipeline yet.
