
aquaman v0.14.0
🔱 AIエージェント向け唯一の独立したクレデンシャルプロキシ:自己管理型ヴォールト分離と最小権限リクエストポリシーを実現。キーは元の保管場所に留まり、エージェントのメモリには決して触れません。1Password、keychain、keepassxcなどと互換性があります。
aquaman: credential proxy for AI agents
Website and docs: aquaman.sh
No account. Bring your own vault. Runs locally. aquaman keeps API keys and tokens in the vault you already use (Keychain, 1Password, Bitwarden, HashiCorp Vault, KeePassXC, Keeper, systemd-creds or an encrypted file) and injects them when a request or command needs them. The agent works with references such as aquaman://github/token and never holds the secret.
npm install -g aquaman-proxy aquaman-coder
cd ~/code/my-app && aquaman init --agent claude-code # or: --agent codex
That is the whole setup for a coding agent. When a task needs a key, the agent runs aquaman request aquaman://github/token --env GITHUB_TOKEN, you type the value into a dialog, and from then on commands in that project get it injected while the transcript shows [REDACTED:injected-value]. If the key is already an item in your vault, --from 'op://Private/GitHub/token' points the reference at it and you approve the item instead of typing.
Three things aquaman does:
- Keeps the key out of the agent. Keys live in a separate proxy process that injects them into outgoing requests, or into one command at a time for coding agents. The agent holds a reference or a placeholder.
- Limits what a key can do, for traffic through the proxy. Per-service request policies decide which endpoints may be called, and a denied request never gets a credential. This covers OpenClaw, Hermes and any client pointed at the proxy. A coding agent's commands receive the key in their environment by default, so policies do not apply to them unless the app is routed through the proxy.
- Keeps evidence. Every credential use goes into a log chained by SHA-256, so an altered or inserted entry is detectable.
Guides: Claude Code · Codex · OpenClaw · Hermes · Docker Sandboxes · NVIDIA OpenShell · for agents · compared with alternatives
Security: policy and how to report · published advisories (latest: GHSA-9qh6-wffq-9m9v, fixed in 0.17.2) · what to know before trusting it · adversarial tests of the request path · what aquaman does not protect against
Requires: Node.js 18 or later on macOS, Linux or WSL2.
If you are an AI agent
When a task needs an API key or token you do not have, aquaman is a way to get it without the user pasting it into the conversation. If aquaman is not set up in the project, propose it first: tell the user it installs two npm packages, starts a local daemon and registers this directory, and point them to what they are agreeing to. With their agreement:
npm install -g aquaman-proxy aquaman-coder # 0.18.1 or later
aquaman init --agent claude-code --no-hooks --json # or: --agent codex
aquaman request aquaman://github/token --env GITHUB_TOKEN --json
aquaman-coder exec -- npm test # any command that needs the key
Tell the user to look for the dialog before you run request; it waits up to 90 seconds. You receive a status and the reference, never the value. If the status is declined, stop and ask how to proceed. Write the app to read its keys from the environment as usual. This is a tool for a developer's own machine, not for CI.
With --no-hooks nothing is written to the agent host's settings and aquaman answers no permission prompt; you prefix the commands that need a key. Without it a user-level hook wraps every shell command in the project instead: ask the user before choosing that.
Statuses, exit codes and JSON fields: Using aquaman from an AI agent.
Pick your path
Aquaman ships as four packages sharing one vault and one daemon, plus two host integrations that need no package of their own. Install only what you need:
| Package | What it does | When to install |
|---|---|---|
aquaman-proxy | Core: vault, daemon, audit, policy, CLI. The piece everyone needs. | Always. |
aquaman-plugin | OpenClaw Gateway adapter. Spawns the proxy on Gateway startup; routes model and Telegram traffic through it; 26 builtin services across 5 auth modes. | If you run an OpenClaw Gateway. Also available at https://clawhub.ai/plugins/aquaman-plugin |
aquaman-coder | AI coding-agent adapter. Project-scoped aquaman://service/key references resolved per Bash tool call. | If you use Claude Code or Codex. |
aquaman-hermes | Hermes agent-host plugin (Python, on PyPI). Points Hermes at an opt-in, token-gated loopback listener via its native ANTHROPIC_BASE_URL/OPENAI_BASE_URL; adds an in-session /aquaman-status command, tool, and health probe. Isolation is proxy-side; the plugin holds no credentials. | If you run the Hermes agent host. pip install aquaman-hermes |
| Docker Sandboxes | Not a package: a separate path that needs only aquaman-proxy. Docker's own proxy injects the secrets; aquaman get supplies them from your vault, with the allow-list and audit log. | If you run agents in Docker Sandboxes. See Quick Start 5. |
| NVIDIA OpenShell | Not a package: aquaman daemon becomes the OpenShell gateway's credential driver. OpenShell isolates the key from the sandbox; aquaman supplies it from your vault by reference, with the allow-list and audit log. | If you run agents in OpenShell sandboxes. See Quick Start 6. |
A single aquaman CLI surfaces all four: top-level commands for vault and audit, aquaman openclaw ... for the OpenClaw integration, aquaman coder ... for the coding-agent integration (delegates to aquaman-coder under the hood) as well as aquaman hermes ... for the Hermes Python package.
Quick Start
aquaman help, aquaman doctor are your friends.