use-native-credential-proxy

Injects Anthropic credentials from .env into NanoClaw containers, bypassing the OneCLI gateway.

1|Updated May 22, 2026
One-click install
npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill use-native-credential-proxy-rosedwayane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: use-native-credential-proxy
Source: https://github.com/roseDwayane/LocalizeAgenticSys/tree/main/nanoclaw/.claude/skills/use-native-credential-proxy
Command: npx skills add https://github.com/roseDwayane/LocalizeAgenticSys --skill use-native-credential-proxy-rosedwayane

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires typescript, vitest.

What problem does it solve? NanoClaw routes all Anthropic credentials through the OneCLI agent vault with an HTTPS proxy and certificates, which adds setup complexity. This Skill provides an opt-out path for users who prefer simple .env-based credential management, reading the API key or OAuth token from .env and injecting it directly into the container environment. ## Core Features & Use Cases - Native .env Credential Injection: Reads ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, or CLAUDE_CODE_OAUTH_TOKEN from .env and passes them into the container as Docker -e environment variables that the Claude Agent SDK reads natively. - Flag-Gated Opt-Out: All logic is gated behind NANOCLAW_NATIVE_CREDENTIALS=true, so the OneCLI gateway path remains untouched when the flag is unset. - Tested Integration: Ships a behavior test driving the real .env read and a wiring test asserting the one-line reach-in exists in buildContainerArgs, plus a REMOVE.md for clean rollback. - Use Case: A user with a Claude Pro/Max subscription runs claude setup-token, stores the token in .env, and restarts NanoClaw so containers authenticate directly without configuring the OneCLI vault. ## Quick Start Ask the agent to apply the use-native-credential-proxy skill so NanoClaw reads my Anthropic credential from .env instead of the OneCLI gateway.

Frequently Asked Questions about use-native-credential-proxy

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I use an Anthropic API key from .env instead of OneCLI in NanoClaw?

Apply this skill to copy the native credential proxy into src/, add the one-line reach-in in buildContainerArgs, then set NANOCLAW_NATIVE_CREDENTIALS=true and ANTHROPIC_API_KEY in .env. Rebuild with pnpm run build and restart the service.

How do I use a Claude Pro or Max subscription token with NanoClaw?

Run claude setup-token in another terminal to mint an OAuth token, then add CLAUDE_CODE_OAUTH_TOKEN=<token> and NANOCLAW_NATIVE_CREDENTIALS=true to .env. The skill injects the token into the container as a standard environment variable.

Does the native credential proxy remove the OneCLI gateway?

No, the skill is additive and gated by the NANOCLAW_NATIVE_CREDENTIALS flag. When the flag is unset, nativeCredentialEnvArgs() returns an empty array and the OneCLI gateway path works exactly as before.

Why does the container fail with 'no Anthropic credential found in .env'?

This error occurs when NANOCLAW_NATIVE_CREDENTIALS=true is set but none of ANTHROPIC_API_KEY, ANTHROPIC_AUTH_TOKEN, or CLAUDE_CODE_OAUTH_TOKEN exists in .env. Add one credential and restart the service.

How do I revert to the OneCLI gateway after enabling native credentials?

Follow REMOVE.md: delete the copied proxy files, remove the import and reach-in from src/container-runner.ts, strip the env keys from .env, then rebuild and restart. The removal is idempotent and safe to run partially.