use-native-credential-proxy

You can inject environment-based credentials into container API requests by using NanoClaw's built-in credential proxy, which reads credentials from a local .env file. This removes the need for external credential services or gateway installations.

Migrating from OneCLI gateway involves replacing it with NanoClaw's built-in credential proxy. You must update source files to integrate credential-proxy.ts, adjust configuration, and rebuild the project to complete the phase-based migration.

Using env-based credentials keeps credentials within the project scope, avoiding external dependencies like OneCLI. This approach is safe and portable, allowing containers to read credentials locally from a .env file during API calls.

No, you do not need to install OneCLI. NanoClaw has a built-in credential proxy that enables simple environment-based credential management by reading from a local .env file and injecting those credentials into API requests.

To enable the native credential proxy, edit your NanoClaw deployment configuration to read credentials from .env, update source files to integrate credential-proxy.ts, rebuild the project, and restart the service.

The built-in credential proxy is limited to deployments relying on environment-based credentials. It requires modifying source files and rebuilding the project, making it unsuitable if your architecture depends on dynamic external credential services.