NanoClaw is adopting OneCLI as its default credential and proxying layer. Every NanoClaw agent will access external services through OneCLI’s Agent Vault, a gateway that handles credential injection, access policies, and approvals so agents never hold raw API keys.
NanoClaw already isolates every agent in its own Docker container. OneCLI’s Agent Vault gives you fine-grained controls over what those agents can access and how.
How the integration works
NanoClaw previously ran its own credential proxy that held every secret in memory. We replaced it with the @onecli-sh/sdk . When NanoClaw spins up a container, it calls applyContainerConfig() to route outbound HTTPS traffic through the OneCLI gateway, which injects the real credential:
import { OneCLI } from '@onecli-sh/sdk' ; const onecli = new OneCLI ({ url: ONECLI_URL }); // Configure container to route through the gateway await onecli. applyContainerConfig (containerArgs, { agent: agentIdentifier, // per-agent credential policies });
Each NanoClaw agent group gets its own OneCLI agent identity, so your sales agent and support agent can have different credential policies. You register credentials once with onecli secrets create and the gateway matches outbound requests by host and path.
Why this matters
OpenClaw proved that people will hand over the keys to their email, their calendar, their code repos, their databases in order to get the value of an agent doing real work on their behalf. Millions of people did exactly that, and most of the time it works out fine. But when it doesn’t, the consequences are real.
A director of AI alignment at Meta gave OpenClaw access to her email and explicitly told it not to take any action without her approval. The agent started mass-deleting emails anyway. She couldn’t stop it from her phone and had to physically run to her computer to kill the process.
That story is what happens when agents operate without boundaries. The value of agents comes from giving them access to real systems and real data. An agent that can’t touch anything is just a chatbot. But an agent that can touch everything, with no policies, no rate limits, no approval flows, is a liability. The question is how you get the Claw unlock without the risk.
... continue reading