fix(codex): route workspace memory through tools#87403
Merged
steipete merged 1 commit intoMay 27, 2026
Merged
Conversation
* fix(codex): route workspace memory through tools * fix(codex): preserve extra memory bootstrap files * fix(codex): support memory_get-only context routing * fix(codex): only tool-route canonical workspace memory * fix(codex): keep memory fallback for sandbox workspaces (cherry picked from commit d93524d)
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:
Verification:
Behavior addressed: Native Codex release builds no longer paste configured workspace MEMORY.md into every turn when memory tools can serve it on demand.
Real environment tested: Local release/2026.5.27 checkout on Node 24.15.0.
Exact steps or command run after this patch: Focused MEMORY.md Vitest filter plus touched lint, extension typecheck, extension test typecheck, docs check, and diff whitespace check.
Evidence after fix: MEMORY.md focused tests passed: 7 passed, 239 skipped in run-attempt.test.ts.
Observed result after fix: Root MEMORY.md routes through memory_search/memory_get pointer when available, falls back to bounded context without tools or with a noncanonical workspace, and nested MEMORY.md stays in context.
What was not tested: Full release CI was not run locally; autoreview process hung after 6 minutes and returned empty output.