Feature request
Allow each locally managed Buzz agent to connect its own Claude Code or Codex subscription account directly from the desktop UI.
Today, users can manually configure isolated account directories with environment variables, but the agent editor does not provide a complete per-agent account connection flow. A machine-wide login also makes it difficult to intentionally assign different subscriptions to different agents.
Proposed behavior
- In the agent editor, offer subscription account connection for supported Claude Code and Codex runtimes.
- Support a separate account for each agent, with isolated local credential/configuration storage (
CLAUDE_CONFIG_DIR / CODEX_HOME). Keep tokens out of relay events, exported agent definitions, and logs.
- Launch the provider's supported login flow for the selected agent account. Show connection status for that account rather than the machine-wide default.
- Preserve existing manually configured account directories and existing shared/default-account behavior.
- Make pending login, successful connection, failed login, and switching back to the default account clear.
- Apply account selection through the existing agent configuration save flow; explain when a running agent must restart to use a changed account.
- Account checks, login, model discovery where applicable, and actual agent startup should use the same account environment.
Acceptance criteria
- Two Claude Code agents can use different signed-in accounts without one login overwriting the other's credentials.
- Two Codex agents can do the same.
- The default CLI account can remain logged out while an independently authenticated agent runs normally.
- Cancelling agent edits does not silently change the running agent's account.
- Existing agents and manually configured account paths continue to work.
- Runtime tests cover account environment isolation, and UI tests cover connection status and save/cancel behavior.
Related bug: #7836 (startup readiness currently ignores the per-agent auth environment).
Additional requested scope
Place an effort selector directly below model selection. Discover supported effort values from the selected Claude Code/Codex adapter and model, including before the agent's first normal session. Account, model, and effort changes should use the existing Save/Cancel boundary, with no silent writes on dropdown selection.
Feature request
Allow each locally managed Buzz agent to connect its own Claude Code or Codex subscription account directly from the desktop UI.
Today, users can manually configure isolated account directories with environment variables, but the agent editor does not provide a complete per-agent account connection flow. A machine-wide login also makes it difficult to intentionally assign different subscriptions to different agents.
Proposed behavior
CLAUDE_CONFIG_DIR/CODEX_HOME). Keep tokens out of relay events, exported agent definitions, and logs.Acceptance criteria
Related bug: #7836 (startup readiness currently ignores the per-agent auth environment).
Additional requested scope
Place an effort selector directly below model selection. Discover supported effort values from the selected Claude Code/Codex adapter and model, including before the agent's first normal session. Account, model, and effort changes should use the existing Save/Cancel boundary, with no silent writes on dropdown selection.