Skip to content

fix: sync manager user script runtime status - #1723

Open
Rat0323 wants to merge 1 commit into
BigPizzaV3:mainfrom
Rat0323:agent/manager-user-script-runtime-status
Open

fix: sync manager user script runtime status#1723
Rat0323 wants to merge 1 commit into
BigPizzaV3:mainfrom
Rat0323:agent/manager-user-script-runtime-status

Conversation

@Rat0323

@Rat0323 Rat0323 commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

What changed

  • add a read-only one-shot CDP probe for window.__codexPlusUserScripts.scripts
  • merge live renderer status into the standalone Manager's local script inventory
  • refresh live status when opening Script Market and after enabling, disabling, or deleting a script
  • gracefully fall back to filesystem inventory when Codex is not running or CDP is unavailable
  • normalize all byte-exact upstream theme assets to LF to prevent recurring Windows checkout hash failures

Why

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 as not_loaded in 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 check
  • npm run vite:build
  • cargo check -p codex-plus-manager
  • cargo 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 .gitattributes fix and the focused rerun above

Follow-up to #1611.

@Rat0323
Rat0323 marked this pull request as ready for review July 31, 2026 07:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant