Vibe Vault — secure credential access for AI coding agents
Stop AI coding agents from exposing your API keys.
Give Cursor, Claude Code, Devin, and VS Code secure access to credentials through a local macOS vault, with Touch ID approval, per-agent audit logs, and no cloud account.
Free for solo developers · macOS 14+ · Local-first · No account required
git clone https://github.com/lunaos-ai/luna-vault cd luna-vault && swift build -c release --product vibevault .build/release/vibevault scan
The risk
Developers now give agents access to repositories, terminals, deployment tools,
and production services. Credentials are still copied into .env files,
shell histories, chat windows, and project folders.
GitGuardian reported 28.65M new hardcoded secrets in public GitHub commits in 2025.
AI-service secrets were one of the fastest-growing leak categories in the same report.
Agent sessions touch terminals, repos, provider tools, local config, and runtime env.
Lakera found credentials inside published npm packages containing Claude local settings files.
Sources: GitGuardian State of Secrets Sprawl 2026 and Lakera AI coding assistant credential scan.
Outcome
Traditional password managers store credentials for people. Vibe Vault controls how AI coding agents access credentials during development.
.env files multiply across repos with no central view or rotation trail.vibevault cursor prepare.How it works
Add or generate a key, prepare Cursor, approve access, let the agent run, then see both successful and denied reads in the audit log.
The setup command wires MCP, agent rules, skills, ignore rules, and a git leak guard so the AI tool requests credentials through Vibe Vault instead of copy-paste.
OPENAI_API_KEY is stored or generated in the encrypted local vault.
Comparison
Password managers, cloud secrets platforms, and .env files each solve
part of the problem. AI coding needs a local workflow boundary around all of them.
Vibe Vault scans gaps, guards git, and injects values only when a command or agent session needs them.
1PasswordKeep it for passwords and browser logins. Use Vibe Vault for local agent API-key access, scanning, and audit.
Bitwarden MCPVibe Vault packages the local Mac coding flow around scanner, MCP, browser import, and project audit.
DopplerDoppler fits cloud SecretsOps. Vibe Vault protects the machine before a secret reaches deployment.
InfisicalUse Vibe Vault when the first job is moving real API keys out of repos used by AI coding agents.
Vibe VaultOne workflow covers local vault storage, AI-agent access, repo protection, provider sync, and audit.
Use cases
Vibe Vault is for local AI coding, multi-repo development, deployment credentials, team onboarding, incident review, and contractor workflows.
Use credentials in a session without pasting raw values into prompts or project files.
.env files.Run vibevault scan to find expected env names and tracked local secret files before an agent session.
Sync to Cloudflare, Vercel, and PushCI without turning Vibe Vault into a cloud vault.
Create new values, import password-app exports, or read visible credential fields from screenshots before review.
Give developers the same scan, prepare, guard, run, and audit path on every Mac.
Audit agent, project, credential, timestamp, and result before a suspicious deployment or repo change.
Use limited local access instead of emailing, pasting, or scattering shared secrets.
Expansion path
Vibe Vault starts where the workflow is local and high-risk: Mac developers using AI agents. The larger category is identity and access management for AI coding agents.
Trust
A security product needs a precise threat story. Vibe Vault keeps Solo credentials local, makes provider sync user-initiated, and records access metadata without storing secret values in logs.
Pricing
Solo stays free. Paid plans cover team rollout, offline license use, updates, support, and a standard workflow for developers whose agents touch real credentials.
Individual
A complete local vault for one builder: app, CLI, MCP, audit, scanning, and provider sync.
Team coverage
Includes 5 developers, offline verification, deployment guidance, and email support.
Studios
For multi-repo teams that need repeatable secret handling across client and product work.
Companies
For macOS engineering groups that want onboarding help and predictable support.
Monthly subscriptions issue a signed offline license valid for the current billing period plus a renewal buffer. Renewal sends a fresh signed license. If a subscription is canceled, the current license keeps working until it expires. Verification remains offline: the app checks the signed license locally and does not contact a Vibe Vault license server to open. Business controls such as SSO, MDM policy, SIEM export, and centralized admin are roadmap items, not included in the current self-serve plans.
FAQ
Vibe Vault starts narrow on purpose: credentials, agent access, local approval, provider sync, and audit evidence for AI coding.
1Password is a strong human vault. Vibe Vault is the local credential runtime for AI coding: repo scanning, agent setup, command injection, provider sync, and per-agent audit.
.env files?.env is convenient until files drift, get copied, or reach git. Vibe Vault keeps the source of truth outside the repo and injects values only when needed.
No. Agents request values through the configured workflow. They receive the values you allow for the current project or command, not unrestricted vault access.
After an approved process receives a secret, Vibe Vault cannot control everything that process does with it. The product reduces exposure, scopes access, and records the read so misuse is visible.
Solo secrets are local to your Mac. Team licensing covers seats and support; it does not move your vault into a LunaOS cloud account.
The current product is local-first. You should keep provider recovery paths and rotate credentials when a machine is lost. Shared vault and relay workflows are on the roadmap for larger teams.
Reads are recorded with secret name, action, project context, agent or process, and timestamp so you can review what happened after an AI session.
Audit events are for access metadata, not raw values. Shell commands and third-party tools can still log values if you print or pass secrets to them unsafely.
Solo vault data stays local. Data leaves the machine only through actions you initiate, such as provider sync, downloads, checkout, or support email.
No local secret manager can defend against complete device compromise. Vibe Vault relies on macOS Keychain, local approval, and reduced copy-paste exposure; it is not an anti-malware boundary.
Secrets are encrypted locally. The vault ciphertext lives on disk and the master key is held in macOS Keychain.
No. Signed offline licenses verify against an embedded public key. The app does not need a license server to open.
The subscription covers updates, support, and license use. License verification stays offline; renewal issues a fresh signed license rather than requiring an always-online account.
vibevault cursor prepare do?It wires the MCP server, installs the agent skill and rules, and prepares guardrails so Cursor can request secrets through the vault.
Yes. Vibe Vault can push to Cloudflare, Vercel, and PushCI when you explicitly run a sync command.
No. Those tools organize context and instructions. Vibe Vault protects the credentials those workflows need when agents run real commands.
Not yet. Vibe Vault is macOS-first because it uses local developer machines and native Keychain security. Linux, Windows, and remote development environments are on the expansion path.
Start
Protect your first repository in minutes, then use the audit trail to prove what happened.