orca-cli

# Orca CLI Use this skill when the task should go through Orca's control plane rather than directly through `git`, shell PTYs, or ad hoc filesystem access. ## When To Use Use `orca` for: - worktree orchestration inside a running Orca app - updating the current worktree comment with meaningful progress checkpoints - reading Orca-managed terminals and sending input to non-agent terminals - stopping or waiting on Orca-managed terminals - creating and managing scheduled Orca automations - accessing repos known to Orca Do not use `orca` when plain shell tools are simpler and Orca state does not matter. Examples: - creating one Orca worktree per GitHub issue - updating the current worktree comment after a significant checkpoint, such as reproducing a bug, validating a fix, or handing off for review - finding the Claude Code terminal for a worktree and reading its status - checking which Orca worktrees have live terminal activity - creating a scheduled automation that runs a prompt against a known repo or worktree ## Preconditions - Prefer the public `orca` command first - Orca editor/runtime should already be running, or the agent should start it with `orca open` - Do not begin by inspecting Orca source files just to decide how to invoke the CLI. The first step is to check whether the installed `orca` command exists. - Do not assume a generic shell environment variable proves the agent is "inside Orca". For normal agent flows, the public CLI is the supported surface, but av...