Problem
agentos-core@0.2.7 ships a workaround in dist/sidecar/rpc-client.js (drainTrailingProcessOutputTurn, see the comment at the top of the file) for native-sidecar process_output events arriving up to one macrotask after process_exited.
A proper fix exists — commit 9555bf756 ("fix(sidecar): order process output before exit", 2026-07-13, includes process-event-ordering.test.ts) — but as far as we can tell it currently lives only on the agent/acp-codex-session-benchmark branch and is not on main / in any released version.
Why it matters to us
We stream agent output token-by-token to end users, and on the previous (JS runtime) architecture we had to patch around adjacent stream-frame reordering ourselves. Event ordering between guest process streams and lifecycle events is load-bearing for us; with the runtime now compiled into the sidecar binary, we have no local mitigation available anymore — we depend on upstream releases for this class of fix.
Problem
agentos-core@0.2.7ships a workaround indist/sidecar/rpc-client.js(drainTrailingProcessOutputTurn, see the comment at the top of the file) for native-sidecarprocess_outputevents arriving up to one macrotask afterprocess_exited.A proper fix exists — commit
9555bf756("fix(sidecar): order process output before exit", 2026-07-13, includesprocess-event-ordering.test.ts) — but as far as we can tell it currently lives only on theagent/acp-codex-session-benchmarkbranch and is not onmain/ in any released version.Why it matters to us
We stream agent output token-by-token to end users, and on the previous (JS runtime) architecture we had to patch around adjacent stream-frame reordering ourselves. Event ordering between guest process streams and lifecycle events is load-bearing for us; with the runtime now compiled into the sidecar binary, we have no local mitigation available anymore — we depend on upstream releases for this class of fix.