use-native-credential-proxy

To use environment variables for Docker container authentication instead of a proxy vault, you can configure the container agent to read credentials directly from a .env file, bypassing the default HTTPS proxy and certificate-based injection.

The best way to pass Anthropic API keys directly into a container runtime is by enabling native credential handling, which injects API keys or OAuth tokens from your local environment files into the container spawn arguments.

To configure NanoClaw agents to bypass the OneCLI gateway vault, you enable native credentials by setting the NANOCLAW_NATIVE_CREDENTIALS flag to true in your .env file and providing your API key.

Yes, you can run NanoClaw agents in isolated environments without the full OneCLI gateway infrastructure by using native credential handling to propagate environment variables directly into the container runtime.

Modifying container spawn arguments for environment variable propagation is necessary to satisfy requirements for non-proxy credential handling, allowing direct injection of API keys into the container runtime instead of relying on vault-based authentication.

Yes, native credential handling supports both Anthropic API keys and OAuth tokens, reading them directly from your .env file and passing them into the container environment for simplified authentication management.