What problem does it solve? Orchestrating an autonomous coding agent from another agent requires knowing the right CLI flags, handling interactive permission dialogs, and managing sessions, which is error-prone without a reference guide. ## Core Features & Use Cases - Print Mode Automation: Run one-shot non-interactive tasks with claude -p, structured JSON output, JSON schema extraction, session resumption, and cost caps via --max-turns and --max-budget-usd. - Interactive PTY Orchestration: Drive multi-turn Claude Code sessions through tmux, including handling workspace trust and bypass-permissions dialogs with send-keys sequences. - Configuration & Extensibility: Covers settings hierarchy, CLAUDE.md memory files, custom subagents, hooks, MCP server integration, permissions, and slash commands. - Use Case: Pipe a git diff into claude -p for an automated PR review, or spawn parallel tmux sessions where separate Claude instances fix bugs, write tests, and update docs simultaneously. ## Quick Start Ask the agent to run claude -p with a coding task, an allowedTools whitelist, and a max-turns limit in the target project directory.