A steel vault with a glowing key sealed inside; only a small card of light comes out of a side slot

CredsForDevs

Zero-trust credential vault for developers and AI agents
Ask about this product
Developer toolOur product

CredsForDevs

Zero-trust credential vault for developers and AI agents

Your SSH keys are in ~/.ssh, your connection strings are in appsettings.Development.json, your VPN profiles are somewhere in Downloads - and the moment you point a coding agent at any of them, it can read all of it. CredsForDevs keeps them in one vault in the editor you already have open, stored in the OS keychain. When an AI agent needs to run a migration, open an SSH session or bring a VPN up, it asks the broker: you approve the real command in your editor, the vault performs it, and only the output comes back. The protocol has no field a raw secret could travel in. Unlike agent vaults that only mediate HTTP, it brokers SSH, database and VPN protocols. Teams can add an optional self-hosted server that syncs end-to-end encrypted vaults and cannot read anything it stores. CredsForDevs is part of Dew Flow, our multi-agent development orchestrator, and is free on the VS Code Marketplace as remsoftdev.creds-for-devs.

Ask about it Learn more

Features

  • SSH hosts, keys, jump hosts and port forwards - connect in one click
  • Databases: Postgres, MySQL, SQL Server, MongoDB
  • VPN profiles: WireGuard and OpenVPN
  • Terminal commands, scripts and config files kept out of git
  • Payment instruments, one-time codes and seed phrases
  • Ten agent permission switches, all off by default
  • Password rotation by agents without seeing the old or new value
  • Entry lifetimes and per-entry PINs
  • Single-binary creds CLI, 6.8 MB, no runtime to install
  • YubiKey / FIDO2 unlock and self-hosted team server
  • Install: VS Code Marketplace - remsoftdev.creds-for-devs

The Challenge

Product: Credential vault and agent broker

Part of: Dew Flow multi-agent orchestrator

Distribution: VS Code Marketplace, MIT licence

Encryption: AES-256-GCM, keys in the OS keychain

What the product had to solve:

  • Agents can read everything: Credentials scattered across files are open to any coding agent in the workspace. The vault makes every entry invisible to agents until you switch it on.
  • More than HTTP: Existing agent vaults mediate HTTP. Real development work needs SSH commands, database queries and VPN connections - brokered on the machine where the secret already lives.
  • A server you do not have to trust: Secrets are encrypted on your machine; the team server stores ciphertext and has no code path that could acquire a key.
  • Rotation without exposure: An agent writes a placeholder, the vault mints the new password, runs the statement and stores the value - only a statement that succeeded updates the vault.

Results

  • Agents run SSH, database and VPN actions without holding secrets
  • Every agent call approved in the editor and logged
  • End-to-end encrypted team sync
  • Zero runtime dependencies in the extension

0 fields

in the broker protocol that a secret could travel in.

10 switches

control what agents may do - every one off by default.

6.8 MB

single-binary CLI for terminals, scripts and remote hosts.

Case studies from our work

Interested in This Product?

Tell us how you would use it - we will answer questions on availability, setup and custom versions.

Ask about this product
An unhandled error has occurred. Reload 🗙