Repository navigation
Keep long AIDE decision history retrievable by reference - #298
Closed
mikamikasuki wants to merge 9 commits into
Closed
mikamikasuki wants to merge 9 commits into
mikamikasuki wants to merge 9 commits into
Conversation
mikamikasuki
force-pushed
the
fix/aide-json-context
branch
from
October 11, 2026 19:34
7f7b941 to
977eecc
Compare
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
Reproduction
Two formal end-to-end requests were rejected before inference: AIDE at 1,505,250 transport characters and FULL at 1,051,668, above the observed 1,048,576 capacity. The failed AIDE request contains about 3.89 million source characters of prior decision history. Replaying that saved request with the history externalized produces a 107,338-character transport payload while the complete source history remains retrievable.
A campaign episode also exposed a Journal restore error after repeated-action diagnostics had stored a string in AIDE's dict-typed exception field. The original checkpoint and action history are retained; the reader translates that legacy string to the upstream exception-argument structure in memory.
Design reference
This follows the established LangGraph context-engineering pattern: keep durable state as raw data and format only the context required by the current node on demand. The complete history stays in persistent episode memory and remains retrievable through the existing paged context tool: Thinking in LangGraph.
Repeated exception metadata follows the existing upstream AIDE ExecutionResult.exc_info shape with an args list, keeping Journal serialization compatible.
Validation
Stacked on PR #297; review #296, then #297, then this PR.