fix: sync manager user script runtime status - #1723
Open
Rat0323 wants to merge 1 commit into
Open
Conversation
Rat0323
marked this pull request as ready for review
July 31, 2026 07:34
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.
What changed
window.__codexPlusUserScripts.scriptsWhy
PR #1611 fixed runtime status reporting in the Codex-embedded user-script panel, but the standalone Codex++ Manager still called
UserScriptManager::inventory()without renderer state. As a result, scripts that were actively running appeared asnot_loadedin Script Market > Local scripts.The new probe opens a short-lived, read-only CDP connection and reads the existing renderer registry directly. It does not reinject scripts and does not call the renderer bridge from inside CDP.
Validation
npm test(36 passed)npm run checknpm run vite:buildcargo check -p codex-plus-managercargo test -p codex-plus-core runtime_status_tests(2 passed)cargo test -p codex-plus-core --test upstream_theme_assets(2 passed after LF normalization)cargo test --workspace: all suites passed through the launcher tests; the pre-normalization run then reproduced the known Windows byte-exact EOL failures, which are covered by the included.gitattributesfix and the focused rerun aboveFollow-up to #1611.