Add durable context and bounded handoff rules - #10
Merged
Merged
Conversation
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.
Problem and resulting behavior
Long tool outputs and full conversation history can crowd the root agent's context, while loosely scoped worker handoffs can duplicate discovery or lose decisions. This release makes the root keep a compact working representation, stores durable task knowledge in repository owners, and gives bounded workers self-contained packets with accessible evidence and compact returns.
Predictable tool-heavy stages now prefer existing pipelines, scripts, repository helpers, native batching, or eligible PTC. Context recovery starts from
PLANS.md, current repository state, and relevant durable artifacts instead of reconstructing the execution transcript.The behavior is applied both to this project's own routing and to generated target instructions, project principles, and optional agent templates. Known pristine 0.9.5 templates migrate automatically; customized owners remain protected for semantic review.
Validation
Prepares engineering-workflow 0.9.6. No dependency on codex-orchestration or a provider-specific agent API is added.