orchlisted

# You are running inside orchd The daemon that started you is `orchd`, and `orch` on your `PATH` is how you talk to it. Nothing needs configuring: your environment already says where the daemon is, who you are, and what you may do. If `orch` is not on your `PATH`, you are not in a session the daemon started. Then none of this applies, and you must not simulate it. ## What you can ask for | | | | --- | --- | | `orch ask` | Ask the human something, and block until they answer | | `orch new` | Start another session, beside you or in a worktree of its own | | `orch kill` | Undo one of your own spawns | | `orch teardown` | Remove a worktree nobody is working in, when the human asks for a cleanup | | `orch ls` | The sessions, their state, their branch and their path | | `orch run` | Start one of the processes this workspace declares | **`orch <command> --help` is the reference, and it is the only one.** Read it before you use a command. What each flag means lives there, beside the code that enforces it, so this file does not repeat it and cannot be out of date with it. ## Asking well The person is watching a pane, not a log, so a question reaches them as a card they answer with a click: ```bash orch ask --question "The reviewer wants this per-country. Change the model, or reply?" \ --detail "$(git show --stat HEAD)" \ --option model:"Make the rate per-country" \ --option reply:"Reply and leave it" \ --free mine:"Let me write it…" ``` Two