Repository navigation
Truncate oversized MCP results in paginated thread history - #50458
Merged
copyberry[bot] merged 1 commit intoOct 2, 2026
Conversation
## Why Paginated thread history can persist large MCP results in completed tool-call items. Bound these stored results to avoid retaining multi-megabyte payloads. ## What changed Apply a 64 KiB preview budget when persisting oversized MCP results in paginated history. Replace the result with a truncated text preview of its serialized JSON, preserving `is_error` and clearing `structuredContent` and `_meta`. Leave small results unchanged. Share the truncation helper with the existing MCP tool-call event path. ## Testing Add helper tests for unchanged small results and oversized results with structured content and metadata. Add a thread-history test verifying that persisted MCP results contain a bounded preview with the beginning, end, and truncation marker while preserving tool arguments. GitOrigin-RevId: 09dce73c70bfd357c9b9630f456e9e5c1d8492cf
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/09dce73c70bfd357c9b9630f456e9e5c1d8492cf
branch
from
October 2, 2026 23:15
cf2ff39 to
820f85c
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/09dce73c70bfd357c9b9630f456e9e5c1d8492cf
branch
October 2, 2026 23:15
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Truncate oversized MCP results in paginated thread history
Why
Paginated thread history can persist large MCP results in completed tool-call items. Bound these stored results to avoid retaining multi-megabyte payloads.
What changed
Apply a 64 KiB preview budget when persisting oversized MCP results in paginated history. Replace the result with a truncated text preview of its serialized JSON, preserving
is_errorand clearingstructuredContentand_meta. Leave small results unchanged.Share the truncation helper with the existing MCP tool-call event path.
Testing
Add helper tests for unchanged small results and oversized results with structured content and metadata. Add a thread-history test verifying that persisted MCP results contain a bounded preview with the beginning, end, and truncation marker while preserving tool arguments.