Description
Selecting "Use your Claude subscription" on the "Connect Your AI" onboarding screen does not work, even after a fully successful Claude Code CLI login.
Steps to reproduce
- Install Claude Code CLI (
npm install -g @anthropic-ai/claude-code)
- Run
claude and complete /login → select "Claude account with subscription (Pro, Max, Team, or Enterprise)"
- Confirm login succeeded — CLI shows
Logged in as <email> and Login successful
- Open Juno, select "Use your Claude subscription" on the Connect Your AI screen
- Fully quit (Cmd+Q) and relaunch Juno to rule out stale state
Expected
Juno's orchestrator picks up the CLI's OAuth session, same as the "No API key needed — uses Claude Code CLI authentication" copy promises.
Actual
Every attempt (including after a clean CLI login and full app restart) returns:
Failed to initialize orchestrator brain: Configuration error: Anthropic API key not found in settings or ANTHROPIC_API_KEY env var
Environment
- Claude Code CLI: v2.1.270
- Model shown in CLI: Sonnet 5 · Claude Pro
- OS: macOS
- Juno: latest (npm
juno-cua / desktop app)
Notes
The CLI-side auth is confirmed working (claude config get / terminal shows Logged in as ..., Login successful), so the issue appears to be in how the orchestrator brain component reads (or fails to read) the CLI's stored credentials — it seems to require ANTHROPIC_API_KEY regardless of subscription login state.
Description
Selecting "Use your Claude subscription" on the "Connect Your AI" onboarding screen does not work, even after a fully successful Claude Code CLI login.
Steps to reproduce
npm install -g @anthropic-ai/claude-code)claudeand complete/login→ select "Claude account with subscription (Pro, Max, Team, or Enterprise)"Logged in as <email>andLogin successfulExpected
Juno's orchestrator picks up the CLI's OAuth session, same as the "No API key needed — uses Claude Code CLI authentication" copy promises.
Actual
Every attempt (including after a clean CLI login and full app restart) returns:
Environment
juno-cua/ desktop app)Notes
The CLI-side auth is confirmed working (
claude config get/ terminal showsLogged in as ...,Login successful), so the issue appears to be in how the orchestrator brain component reads (or fails to read) the CLI's stored credentials — it seems to requireANTHROPIC_API_KEYregardless of subscription login state.