fix(perf): retire idle provider resources - #517
Merged
Merged
Conversation
astyfx
requested review from
JongSikLim and
dodonmountain
and removed request for
a team
September 8, 2026 12:41
|
| Commit | Scanned at | New | Resolved | Net |
|---|---|---|---|---|
592cc31 < |
2026-09-08 12:42 UTC | 0 | 0 | 0 |
Last scanned: 592cc31 · 2026-09-08 12:42 UTC
astyfx
enabled auto-merge (squash)
September 8, 2026 12:42
Merged
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
Long-running provider sessions could retain completed Codex thread resources,
quiet streams could lose their replay window, and failed host children could
survive a transport error. This change gives provider resources explicit idle
lifetime boundaries and keeps the live chat clock local to the row that renders
it.
Changes
Fixes
release turn ownership from one outer cleanup path
through an independent timer
original child reference
message row
Refactors / Chores
and message-clock behavior
Test Evidence
bun run test:isolated— 5,247 shared tests passed; 35 isolated suites passedbun run typecheckandbun run typecheck:lens-mainpassedbun run check:licenses,check:switch-exhaustiveness,check:max-lines-ratchet,check:doc-paths, andcheck:reliability-gatespassed
bun run buildandbun run build:desktoppassedNotes
The raw
bun testcommand runs process-wide module mocks together; therepository's isolated test runner is the CI path and was used for the full
suite. Resource retirement is bounded and reversible: the next request starts
a fresh App Server and resumes the persisted thread when needed.