Automic Vault

Your secrets manager should know what the secrets do.

Automic Vault moves supported credentials out of plaintext files. It checks the
Tool, Verified Launcher, Target, command, arguments, working directory, and
requested Secret Names before applying one. Your existing commands still work,
and agents need no plugin.

- One credential, different decisions: gh issue list can run while gh auth token
  still needs Approval.
- Terminal and Codex get separate rules: policy follows each Verified Launcher.
- Use API_TOKEN across projects: the working directory selects the Project Value.

Download for macOS: https://www.automicvault.com/Automic%20Vault.dmg

How authorization works

Most secrets managers check an identity and Secret Name before returning the
stored value.

Automic Vault checks the Verified Launcher, Tool, Target, command, arguments,
working directory, Secret Names, and selected Secret Value sources. Policy
evaluates the complete Authorization Request on the Mac where it will run.

With Read Only access, one GitHub token produces different decisions:

gh issue list     → automically authorized
gh issue create   → Approval required
gh auth token     → Secret Disclosure; Approval required

Automic Vault controls Secret Application. After the handoff, the Target
controls the Secret.

Set separate rules for each Verified Launcher

Terminal, Codex, and an unknown process can invoke the same Tool. Automic Vault
identifies the Verified Launcher and gives each Tool–Launcher pairing its own
Authorization Policy.

Use the same Secret Name across projects

A Secret Name can have a Global Value and multiple Project Values. Automic
Vault selects the nearest Project Value for the physical working directory.
Every project can request API_TOKEN. The Project Directory selects a value; it
does not grant authority.

Give an agent task ten minutes of Write Access

Eligible Codex tasks and Claude Code sessions can receive a visible, in-memory
Temporary Access Grant for ten minutes. Blessed Scripts bind an exact path,
contents, Secret Names, and declared Tool capabilities.

Move every human Approval to iPhone

iPhone Approval is optional and enabled per Mac. Open Automic Vault on an
iPhone using the same iCloud Keychain account, enable iPhone Approval, and allow
notifications. Then enable it under Settings > iPhone Approval on the Mac.

The iPhone carries the human decision. The Mac still verifies the complete
Authorization Request, records the result, and enforces it. Secret Values and
Authorization History stay on the Mac. The Mac exposes no local allow action.
If no phone or relay is available, the request waits until its Gate Client
cancels.

iPhone Mirroring and Show on Mac can expose Approval controls on the Mac when
biometrics are off. Disable them, or require Face ID or Touch ID on every
eligible iPhone.

Each Tool gets its own credential handoff

- AWS normal invocations receive short-lived STS credentials from a native helper.
  Long-lived keys stay in Automic Vault.
- Docker credential release verifies the live Docker process and requested registry.
- Launcher Bundles give exact single-file Mach-O snapshots a revalidated identity.
- Homebrew policy separates reads and updates from installs and upgrades.
- Over 100 supported developer configurations are checked for Exposures and Hazards.

The boundary ends at the Target

Automic Vault controls supported Secret Application and sensitive Tool
operations at the Local Execution Boundary. macOS handles general process and
filesystem security. Root or kernel compromise, arbitrary local destruction,
and the Target's behavior after Secret Application remain outside the product
boundary. Code signing proves identity and integrity, not intent. A compromised
Target can leak a received Secret.

Automic Vault is free Apache-2.0 open-source software for macOS.

Documentation: https://www.automicvault.com/docs/
Security: https://github.com/automic-vault/automic-vault/security
Source: https://github.com/automic-vault/automic-vault