No plaintext handoff
Sensitive values should not live in `.env`, shell profiles, or CLI config files an agent can read directly.
Security model
Automic Vault protects macOS developer machines by moving secrets out of plaintext files, injecting approved credentials into trusted tools, and gating sensitive commands before they execute.
Last updated: May 15, 2026
Threat model
Automic Vault assumes a local AI coding agent can read project files, inspect shell configuration, run command-line tools, and accidentally expose credentials through logs or transcripts. The product reduces that ambient authority.
Sensitive values should not live in `.env`, shell profiles, or CLI config files an agent can read directly.
Approved tools receive named secrets for the execution that needs them; the model does not receive a raw value to paste or summarize.
Package publishing, cloud mutation, and token-revealing commands should be approved at the command boundary.
Release builds install under `/opt` and stub into `/usr/local/bin`; debug builds use `/tmp/opt` and `/tmp/usr/local/bin`.
Disclosure
Automic Vault is open-source software. Use the public repository for source review, issue reporting, and release tracking. Do not include live secrets in public issues.