Repository navigation
CL-8988: refresh OAuth credential before continuation infers - #1208
Merged
Merged
Conversation
Continuations run after tool results land, possibly long after the attempt-start refresh, so an expired token 401s the next infer.
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
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.
Continuation infers run after tool results land, possibly long after the attempt-start refresh, so a token expiring mid-run 401s the next infer. This wraps the reactor director at the run.ts host layer: after the director returns an infer action, the OAuth credential is ensured fresh (expiry-aware, single-flight) and pushed to the live agent before the reactor executes the infer. Directors stay pure; non-infer decisions pass through untouched.
Verification: lint, typecheck, dead-exports, build, and full suite (8607 pass, 0 fail) green in the worktree.
Fixes CL-8988