🤖 fix: keep process alive when stdin closes in agentSessionCli #529
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
Terminal-bench was failing with all tasks showing 0 input/output tokens because the agent was exiting immediately after receiving the user message, without making any API calls.
Symptoms:
agent_timeouttotal_input_tokens: 0,total_output_tokens: 0caught-upandusermessage, but nostream-deltaorstream-endeventsRoot cause:
The
agentSessionCli.tsreads the user message from stdin via a pipe:Once stdin reaches EOF and is consumed, Bun detects no other active handles keeping the event loop alive and exits the process, even though async work (API streaming) is still pending.
Solution
Add an explicit keepalive interval that ensures the process stays alive until
main()completes. The interval runs far into the future (1000 seconds) but gets cleared in the finally block once the agent session finishes.Testing
Before fix:
After fix:
Related
Generated with
cmux