Skip to content

fix(windows): keep catalog discovery off request event loop #1876

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Ingwannu wants to merge 2 commits into
base: dev
Choose a base branch
from
+400 −50
Open

fix(windows): keep catalog discovery off request event loop #1876

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4612b7d
fix(windows): keep catalog discovery off request event loop
Ingwannu Aug 17, 2026
d5acd74
test(windows): pin request catalog cache boundaries
Ingwannu Aug 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions docs-site/src/content/docs/guides/sub-agent-surface.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -259,6 +259,12 @@ timestamp, an unreadable process start time, or a failed process enumeration —
separately by `ocx doctor`. `stale` clears only after every detected Codex app-server starts after
the final catalog write; it does not necessarily clear `unknown`.

On Windows, this advisory check uses asynchronous PowerShell/CIM discovery on the v2 request path.
Concurrent cold checks share one in-flight discovery and results are cached briefly. A
slow or failing CIM query can delay or suppress only OpenCodex-authored model guidance; it does not
block the Bun event loop, `/healthz`, or unrelated proxy traffic. Explicit CLI/service lifecycle
operations retain the synchronous, fail-closed process collector because they may signal processes.

Only a real change counts. A sync whose result is byte-identical to the catalog already on disk
leaves the file untouched, so restarting the proxy or re-syncing an unchanged model set does not
make a running Codex look stale.
Expand Down
Loading
Loading