Preserve AGENTS world-state context - #788
Open
shiny-code-bot wants to merge 4 commits into
Open
Conversation
6 tasks
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.
Why
A single 32-KiB AGENTS context item did not hard-enforce the repository's per-item 10K-token rule. This amendment keeps the same approximate aggregate allowance while proving every model-visible item stays independently bounded.
Refs #787
What changed
InputText.project_doc_max_bytessolely in the project loader; no global/home loader cap is added.Verification
just test -p codex-core world_state— 104 passed, 0 failed.just test -p codex-core agents_md— 66 passed, 0 failed.just fix -p codex-core— completed successfully.just fmt— completed successfully.git diff --check— clean.origin/main: 706 additions, 92 deletions; 798 changed lines across seven files.Changed-files inspection was separately inconclusive: the configured IntelliJ Code Bridge descriptor was unavailable, so execution is not proven. This is an inspection/harness limitation, not a code failure.
Internal review delegation was unavailable. Automatic Validation and Automatic Background Review emitted no observable start or terminal events in this run, so neither status is claimed. Final independent review remains with external orchestration.