Stop fable's context from being spilled to a preview - #263
Merged
Conversation
A large additionalContext gets spilled to disk and previewed, so the raised caps were losing context instead of adding it.
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.
#262 raised the truncation caps, which pushed fable's injected context from 22KB to 65KB. Past ~64KB the harness spills
additionalContextto disk and hands the subagent a ~2KB preview, so the reviewer ended up with less than before. Codex never hit this because it already stages to a file.emit, so a throw can no longer write two JSON objectscontextFileis set after the write returns, so the path always resolvesVerified across 8 hook inputs (missing file, malformed stdin, null path, empty file, junk lines, directory as path): all exit 0, all emit exactly one object, none above 341 B.