feat: fail fast on CLI authentication errors (v0.2.4) - #3
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Workers now raise a typed WorkerAuthError immediately when the claude CLI reports an auth failure (oauth session expired / not logged in / invalid api key / please run /login), during spawn, TUI ready-wait, or crash — instead of hanging out the full tui_ready_timeout.
Motivation: a downstream deployment burned ~178 serial multi-minute ask timeouts when the CLI OAuth expired, because auth death was indistinguishable from slowness. Auth failures now surface fast and typed so embedders can fall back immediately.
Co-Authored-By: Claude Opus 4.8 noreply@anthropic.com