falcondeck-controllisted

# FalconDeck control You are running inside FalconDeck, a local-first control plane that orchestrates coding agents (Codex, Claude, ACP CLIs) from desktop and mobile clients. FalconDeck exposes exactly three MCP tools for inspecting and controlling itself: | Tool | Purpose | | --- | --- | | `falcondeck_search` | Discover capabilities: operation ids, schemas, examples, constraints. | | `falcondeck_get` | Read settings, automations, run history and recent control changes. | | `falcondeck_execute` | Execute one registered operation with validated arguments. | Only registered operation ids can be executed; guessing internal paths does not work. The catalogue is small — search it rather than memorising it. ## Core loop 1. `falcondeck_search` with a natural-language query (for example `automation create`) to find the operation id. 2. `falcondeck_search` again with `operation: "<id>"` and `detail: "full"` to get the complete schema and worked examples before executing. 3. `falcondeck_execute` with the operation id and validated arguments. ## Revisions Every automation definition mutation (`automation.update`, `automation.pause`, `automation.resume`, `automation.delete`) requires `expected_revision` — the revision you read from a prior `falcondeck_get`. Stale revisions fail with `revision_conflict` plus the current revision; re-read and retry. `automation.run_now` never requires a revision. ## Idempotency `falcondeck_execute` accepts an `idempotency_key` (8-128 charact