You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: CLAUDE_CODE_OAUTH_TOKEN from .env not picked up in web terminal (ttyd) #21
When running Claude Code via the web terminal (./clide web / make web), CLAUDE_CODE_OAUTH_TOKEN set in .env is ignored. Claude starts into the normal unauthenticated first-run setup loop, requiring a browser-based OAuth login to proceed.
This works correctly via make claude and make shell.
Steps to Reproduce
Set CLAUDE_CODE_OAUTH_TOKEN=sk-ant-oat01-... in .env
Run ./clide web or make web
Open the web terminal at http://localhost:7681
Run claude
Expected Behaviour
Claude authenticates silently using the token from .env, same as it does in make claude / make shell.
Actual Behaviour
Claude enters the unauthenticated startup loop and prompts for browser-based OAuth login.
Root Cause (suspected)
The web service in docker-compose.yml likely doesn't pass CLAUDE_CODE_OAUTH_TOKEN through to the container environment, or the claude-entrypoint.sh pre-seed logic that handles auth config isn't wired into the ttyd session the same way it is for the claude and shell services.
Acceptance Criteria
CLAUDE_CODE_OAUTH_TOKEN set in .env is available inside the ttyd web terminal session
Running claude in the web terminal authenticates without prompting, same as make claude
ANTHROPIC_API_KEY path is verified to work the same way
No regression to make claude / make shell auth behaviour
Activity
fix(web): pre-seed Claude auth in web terminal + add tmux multi-pane …
fix(web): Claude auth + tmux multi-pane for web terminal (#22)
Stage clean: latest code from Gitea (#107)