What problem does it solve? Orchestrating an autonomous coding agent from a terminal assistant requires knowing the right CLI flags, handling interactive permission dialogs, and managing sessions, which is error-prone without a structured guide. ## Core Features & Use Cases - Two Orchestration Modes: Run one-shot non-interactive tasks with claude -p print mode, or drive multi-turn interactive REPL sessions through tmux with PTY dialog handling. - Structured Output & Automation: Extract JSON results, stream events, enforce JSON schemas, resume sessions, and cap spend with --max-turns and --max-budget-usd for CI/CD pipelines. - Full CLI Reference: Covers subcommands, permission flags, hooks, MCP server integration, custom subagents, slash commands, and CLAUDE.md memory configuration. - Use Case: Pipe a git diff into claude -p to get an automated PR review, or run 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 your coding task, allowed tools, and a max-turns limit in your project directory.