Fix retained web-search resume on fresh actors - #51
Merged
Conversation
first-assist
deleted the
fix/retained-resume-web-search-state-20260901
branch
September 1, 2026 03:40
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.
Summary
Allow a freshly initialized Codex process actor to adopt the exact frozen web-search domain policy and call ceiling from a retained session while encoding
thread/resume. Actors that already hold retained state continue to reject any policy or ceiling change.This fixes a pre-dispatch rejection when a retained web-search-enabled thread is resumed in a new process. It does not change GraphQL SDL, persistence, authorization, or data migration behavior.
Verification
Documentation impact
Check exactly one option and explain the result.
Explanation: bumped
graphql-orm-aito 0.95.13 and updated its README, changelog, migration guidance, implementation status, generated workspace inventory, and both lockfiles.