Repository navigation
feat: background shell wrappers, 900s codex flights, stop gate (0.0.73) - #93
Merged
Merged
Conversation
…ghts, and pipefail
…bound the capacity scan
…fs leave changes uncommitted
…d, in flight notice no longer forces a turn
…apper delivery views in stats
…ilures, runs engine host checks
… flagship default
…vation sidecars are pruned
…ell wrappers and new defaults
…arry the sandbox line
…thout an exit line, tests follow the new footers
Owner
Author
|
live check with the branch copies loaded through |
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
await-outputoperation in slices of at most 100 seconds, then return one report. claude code can deliver a subagent report throughSubagentHandback, which delivers once: on a host with that harness 13 of 17 wrappers handed back theirwaiting on <id>line and the real output never reached the orchestrator.shared/companion/await-output.mjsholds the logic, every companion andjob-collect.mjsroute to it, and the five forwarder agent files carry the protocol.SubagentHandbackis read from the transcript and counts as collected at SubagentStop for fusion's own workers (9 of 10 claude workers on that host were recorded asmissing_final_text). a peer wrapper's handed back placeholder stays uncollected.systemMessage: as hook context it forced another turn each time, 269 in a week on one host, 265 of them a one line heartbeat at 376k tokens of context.--transport-background-shell; a foreground bash call keeps 570. over seventeen days 15.6% of codex jobs timed out and those flights with their wind downs took 35% of codex wall clock, while the event ledgers show the jobs working, not hung.request_scopecall, which the companion used to end at the announcement (both write runs on devin 3000.12.43 in linked worktrees failed this way). burst briefs tell the engine to leave changes uncommitted./fusion:statsadds a last 7 days line to verification evidence and a wrapper delivery by plugin version section; verification recognition coverstimeout,env,turbo, andnx; the breaker check reads only job files inside its lookback window, raises a wrapper delivery advisory, and asks a companion for host blockers throughhost-check(grok first).rules-manifest.jsonis generated output.test plan
already verified
npm test: three full runs of 1969 tests each ended 1965 pass, 3 skipped, and one failure that was a different timing sensitive monitor test each time and passed alone. those tests waited on scans that the idle cadence had made four times slower; with their scan interval restored,node --test tests/codex-jobs-monitor.test.mjspassed 62 of 62 three times in a rowclaude plugin validatepasses for codex, grok, cursor, devin, fusion, andclaude plugin validate . --strictfor the marketplace root;node shared/sync.mjs --checkandnode bench/manifest.mjs --checkpasstimeout: 600000moved to the background at 180 seconds and ran to 700 seconds with exit code 0, so a background shell is not bound by the 600 second tool limitrequest_scopearrives as an announcement followed by a permission request; refused, the turn endedend_turn; a write run in a plain repository committedtests/codex-deadline.test.mjs), one declined (the 90 day rule matches the one codex already applies)reviewer should verify
/fusion:smokepasses, a codex dispatch that runs past 180 seconds returns its report with nowaiting onnotification, and/fusion:statsshows the wrapper delivery sectionnotes
it never executes a work packagebecomesa change that passes that gate is not a work package, and the main session never executes one, which states the same invariant and removes its conflict with the inline gate. the 570 second wording becomes one flight, with the clocks sentence naming 900 seconds through a wrapper and 570 from a foreground call.so a larger spec grade package uses gpt-6.1-sol at xhighis replaced by the flagship lane default and the one package rule for gpt-6-astra. the runtime guard paragraph is shorter and keeps every fact a model acts on. added: a delegated review checks the quality floor without authoring, the panel's third seat follows the skill's two triggers, a lane's single flight slot excuses sequential dispatch, a filtered verification starts withset -o pipefail;, and a burst brief leaves changes uncommitted. no invariant inCONTRIBUTING.mdchanges; its foreground wrapper line now also says how the wrapper waits.[exited with code N]to a background shell's output file. without that line a terminal footer that stays unchanged for 10 seconds counts instead.