rivet-dev / rivet-dev/agentos

Please land the process_output/process_exited ordering fix

Open
#1,840 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Rust
Stars
4.6k
Forks
251
Avg merge
2d 15h
Merged PRs (30d)
34

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing dist/sidecar/rpc-client.js and commit 9555bf756, then inspect process-event-ordering.test.ts on the agent/acp-codex-session-benchmark branch. Run that ordering test and check the release workflow; done means the fix is on main and included in a released version.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, typescript
Domain
release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.