Repository navigation
Keep outcome-sized work guidance in Worker prompts - #9123
Open
loopx-agent wants to merge 1 commit into
Open
loopx-agent wants to merge 1 commit into
loopx-agent wants to merge 1 commit into
Conversation
Signed-off-by: LoopX Agent <337587101+loopx-agent@users.noreply.github.com>
This branch has not been deployed
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.
Follow-up to #9045, the work-segment review, targeting its branch at
9944eaa8. The standard accounting clause stays with the executor. Both built-in Worker renderers now explain thatone_stepis a work segment and ask the Worker to choose the largest coherent result it can reliably complete and verify within the admitted task, execution profile, capabilities and budget. Related actions toward the same result stay together; separate work at an independent outcome or a real dependency, approval or validation boundary. No new permission or state field is introduced.The projection omits only the recognized standard clause. An unfamiliar policy, including a legacy clause with an added stop condition, remains visible. The signed source, executor policy, and native replay contract are unchanged.
Validation: a standalone Core wheel on File and SQLite passed the actual Codex CLI prompt capture, malformed-request refusal, original-source readback, and one-settlement replay tests (2 tests). Both prompt renderers, source verification, and scoped approvals passed 10 focused tests. Turn-envelope TypeScript tests (67), control-plane typecheck, Ruff, configured mypy, RFC parity, and the changed-file public boundary scan passed. The broader local qualification did not complete on this host; premerge and CLI differential hit local disk exhaustion, and the full-tree scan flagged an unchanged base fixture. No live model outcomes or token savings were measured.