patcher-clilisted

# Patcher CLI Use `patcher` when controlling Patcher itself: inspect current context, coordinate threads, message agents, or inspect projects, providers, and environments. This file covers the everyday loop — get context, spawn, coordinate, inspect. Each other area has a reference file; read the one your task needs rather than all of them. ## Start With Context - Use `patcher status` to identify the current project, thread, and environment. - Prefer `--json` when command output will drive follow-up work. - Run `patcher guide` for the system overview and `patcher guide <chapter>` for full command reference. - A standalone `patcher` CLI with no connection env targets the default local server at `http://127.0.0.1:38986` and host daemon port `38987`. Set `PATCHER_SERVER_URL` and `PATCHER_HOST_DAEMON_PORT` only for remote or non-default targets. The Add machine installer injects its enrolled daemon's selected local API port automatically and atomically reserves it across default and custom machine data directories. - The main server and source Vite app bind to loopback by default. Use a private Tailscale Serve URL (or an equivalent private reverse proxy) for remote browsers and execution machines. `--server-bind-host 0.0.0.0` is a compatibility escape hatch only: the public API is guarded by a per-install key that any local process can read, and permits command execution and file reads, so wildcard binding requires a trusted network boundary. Every `/api/