Computer Use native pipe only initializes when the bundled marketplace is (re)written; every normal app restart leaves it "helper paths unavailable"

What version of the Codex App are you using (From “About Codex” dialog)?

OpenAI.Codex_26.527.3686.0_x64__2p2nqsd0c76g0

What subscription do you have?

GPT PRO

What platform is your computer?

Windows 11 Pro, build 10.0.26200

What issue are you seeing?

On Windows, the Computer Use native pipe fails to start on a normal app launch with Windows Computer Use helper paths are unavailable. It only reaches a working ("ready") state on a launch that happens to rewrite the bundled-plugins marketplace (e.g. right after a repair/rebuild). On the next ordinary restart it breaks again. The helper binary itself is present the whole time.

What steps can reproduce the bug?

Launch that rebuilt the marketplace → works:

computer-use notify config ensure finished status=already-present (or status=repaired)
computer-use native pipe startup ready pipePath=\\.\pipe\codex-computer-use-...
... (then later it can flip:)
computer-use native pipe helper paths changed
computer-use notify config ensure finished reason=missing-helper-path status=skipped
computer-use native pipe startup failed errorMessage="Windows Computer Use helper paths are unavailable"
Ordinary restart (no marketplace rewrite) → fails repeatedly:

computer-use notify config ensure finished reason=missing-helper-path status=skipped
computer-use native pipe startup failed errorMessage="Windows Computer Use helper paths are unavailable"
(repeats every few seconds)

What is the expected behavior?

I should be able to see the page of computer use plugin in Codex app working normal.

Additional information

The Computer Use helper-path resolution only succeeds while/just after the bundled marketplace is being written for that session; on a normal launch the resolver returns missing-helper-path even though the helper exists in the plugin cache. Looks like the resolved helper path is tied to a transient marketplace-write path rather than the stable plugin-cache install location.