ocx

# Operating `ocx` `ocx` controls a locally running opencodex proxy. The CLI covers the dashboard's operational surface, subject to Consent and Secret-bearing commands below. `ocx capabilities` lists the *declared* index, not every verb. Be precise about the gap, because guessing costs you more than reading: the capability index below is complete and authoritative for what it lists, and it does not yet list every management route. A route with no declared capability may still have a working command — `ocx access key` and `ocx route policy` both work while `capabilities --route` returns nothing for them. So use the index first, and fall back to `ocx <group> help` before concluding a capability is missing. This skill is for **operating** a proxy. Two neighbours cover different jobs: `AGENTS_INSTALL.md` is for installing one, and the repository `AGENTS.md` is for changing the codebase. ## Start here ```bash ocx capabilities --json ``` That is the machine-readable index of declared verbs, the routes they drive, their flags, and whether they mutate. Read it first rather than guessing a command name. It is not exhaustive — an unmatched `--route` exits 4 when the table has no row, even if a working verb exists. The converse of generation also holds: a verb can exist without appearing here (`ocx access key`, `ocx route policy`). Narrow it when you already know what you want: ```bash ocx capabilities --mutating-only --json # only state-changing verbs ocx capabilities --rou...