Keep agent processes alive for one-hour idle window - #165
Merged
Conversation
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
AgentStateKeyand cancel them only after one hour with no new prompt for the same state keyRoot cause
PR #103 added terminal cleanup that called
Process.Cancel/ closed the Codex RPC client immediately after each response. That correctly removed leaked foreground CLI processes, but it also killed background work started by the agent as soon as the response finished.Validation
Cancelmake checkpassed all Go packages, then stopped because the local Docker daemon exhausted its predefined network address poolsgit diff --check