Summary
The Docker entrypoint currently reports No auth configured when Claude auth is provided via ANTHROPIC_AUTH_TOKEN. This is a bug: the auth check should recognize ANTHROPIC_AUTH_TOKEN as a valid Claude auth source.
Problem
In docker/entrypoint.sh, Step 1 only checks these Claude-side variables:
ANTHROPIC_API_KEY
CLAUDE_CODE_OAUTH_TOKEN
It does the same when checking the mounted .env fallback. If neither of those is present, it errors with:
No auth configured. Set ANTHROPIC_API_KEY / CLAUDE_CODE_OAUTH_TOKEN (Claude) or OPENAI_API_KEY / CODEX_API_KEY (Codex).
However, there are setups where Claude auth is provided through ANTHROPIC_AUTH_TOKEN. In that case, the entrypoint should not fail the auth precheck, but today it does because that variable is ignored.
Reproduction
- Start the Docker image with
ANTHROPIC_AUTH_TOKEN set
- Do not set
ANTHROPIC_API_KEY or CLAUDE_CODE_OAUTH_TOKEN
- Observe the container fails early with
No auth configured
Expected behavior
The Docker entrypoint should treat ANTHROPIC_AUTH_TOKEN as valid Claude auth during:
- environment-variable auth detection
.env fallback auth detection
- Claude auth/runtime detection logic
- auth token resolution for the later
zylos init path, if applicable
Why this matters
The current precheck is incomplete and rejects valid Claude auth configurations. This causes startup failure even though usable auth is already present in the container environment.
Suggested direction
- Add
ANTHROPIC_AUTH_TOKEN to the Step 1 auth presence check
- Add
ANTHROPIC_AUTH_TOKEN to the .env fallback grep
- Include it in Claude-auth detection (
HAS_CLAUDE_AUTH)
- Review whether
AUTH_TOKEN resolution should also prefer / accept ANTHROPIC_AUTH_TOKEN
- Update the error/help text and docs so supported Claude auth env vars are listed consistently
References
docker/entrypoint.sh Step 1 auth check
docker/entrypoint.sh AUTH_TOKEN resolution
docker/entrypoint.sh HAS_CLAUDE_AUTH runtime detection
Summary
The Docker entrypoint currently reports
No auth configuredwhen Claude auth is provided viaANTHROPIC_AUTH_TOKEN. This is a bug: the auth check should recognizeANTHROPIC_AUTH_TOKENas a valid Claude auth source.Problem
In
docker/entrypoint.sh, Step 1 only checks these Claude-side variables:ANTHROPIC_API_KEYCLAUDE_CODE_OAUTH_TOKENIt does the same when checking the mounted
.envfallback. If neither of those is present, it errors with:No auth configured. Set ANTHROPIC_API_KEY / CLAUDE_CODE_OAUTH_TOKEN (Claude) or OPENAI_API_KEY / CODEX_API_KEY (Codex).However, there are setups where Claude auth is provided through
ANTHROPIC_AUTH_TOKEN. In that case, the entrypoint should not fail the auth precheck, but today it does because that variable is ignored.Reproduction
ANTHROPIC_AUTH_TOKENsetANTHROPIC_API_KEYorCLAUDE_CODE_OAUTH_TOKENNo auth configuredExpected behavior
The Docker entrypoint should treat
ANTHROPIC_AUTH_TOKENas valid Claude auth during:.envfallback auth detectionzylos initpath, if applicableWhy this matters
The current precheck is incomplete and rejects valid Claude auth configurations. This causes startup failure even though usable auth is already present in the container environment.
Suggested direction
ANTHROPIC_AUTH_TOKENto the Step 1 auth presence checkANTHROPIC_AUTH_TOKENto the.envfallback grepHAS_CLAUDE_AUTH)AUTH_TOKENresolution should also prefer / acceptANTHROPIC_AUTH_TOKENReferences
docker/entrypoint.shStep 1 auth checkdocker/entrypoint.shAUTH_TOKENresolutiondocker/entrypoint.shHAS_CLAUDE_AUTHruntime detection