What problem does it solve? Orchestrating an autonomous coding agent from another agent or automation pipeline requires handling interactive prompts, permission dialogs, session state, and structured output, which is error-prone when done ad hoc. ## Core Features & Use Cases - Print Mode Automation: Run one-shot non-interactive tasks with claude -p, capturing JSON results with session IDs, cost, and token usage for scripting and CI/CD. - Interactive PTY Orchestration: Drive multi-turn Claude Code sessions through tmux, including handling workspace trust and permissions dialogs with send-keys sequences. - Structured Extraction & Sessions: Enforce JSON schemas on output, resume or fork sessions by ID, pipe files and diffs as stdin context, and run parallel instances. - Use Case: Pipe a git diff into claude -p to get an automated PR review, or spawn three tmux sessions to fix a bug, write tests, and update docs in parallel. ## Quick Start Ask the agent to run claude -p with a coding task and a max-turns limit in your project directory to get a one-shot autonomous code change.