You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One click, from the tray or Settings — the tray menu shows Install opencapx Command while the command is missing (and drops the item once it is installed); Settings → General → Command line manages install/remove and shows the state. macOS asks for your password once when /usr/local/bin is root-owned.
From a terminal:opencapx install-cli (and uninstall-cli). The installed command is a symlink to the app's stable copy at ~/.opencapx/bin/opencapx, so it survives app moves, re-installs and updates.
This fixes the documented first step (opencapx connect claude) not working on a fresh DMG install — the CLI used to be reachable only by its full path inside the app bundle.
A real CLI front door
opencapx --help lists every command with a description (it previously showed only the signing toolchain, no matter how much was added since); every subcommand documents its own flags (opencapx pack --help, opencapx sandbox --help, …); a typo errors with a suggestion instead of silently launching the app; and opencapx --version exists.
Also in this release
The commands themselves are unchanged: connect, sandbox, rewrite, rules, guard, automation, and the plugin signing toolchain (keygen / pack / verify / verify-package / sign-index / verify-index). Agent hooks and MCP entries never needed the CLI install — they already point at the stable copy by absolute path.