--verbose / -v for full JSON; invoke also has dedicated json and markdown subcommands for structured output.
Command groups
| Group | Purpose |
|---|---|
| Vault lifecycle | status, init, unlock, lock, rotate-master, audit |
| Secrets | secrets create, list, update, rotate, delete, import |
| Credentials | credential create, list, delete |
| Capabilities | capability list, describe, create, delete, policy, bind, unbind, bindings |
| Invoke | invoke, json, markdown |
| OAuth | oauth setup |
Top-level shortcuts
These shortcuts avoid typingcapability invoke ... for the most common operation:
Global behavior
- Auto-initialization: if no vault exists, the first command that needs it will auto-initialize with safe defaults
- Daemon boundary: on unix platforms,
invokecommands connect to theaivaultddaemon (auto-started) for secret isolation. See Daemon - Output modes: human-readable (default); JSON via
--verbose/-von commands that support it; or structured JSON/markdown via thejson/markdownsubcommands