Codex FenBrowser JavaScript Runtime Triage for Failure Stages
Reduce an engine-side JavaScript failure to a small repro and identify whether parsing, bytecode, execution, or a host contract fails first.
中文Install in Codex
Codex with a FenBrowser checkout, a local page or script fragment, observed output, and relevant tests.
- Copy the entire pinned `.codex/skills/js-runtime-triage/` directory to `.agents/skills/js-runtime-triage/` in the target checkout.
- Open Codex in that checkout and invoke `$js-runtime-triage` with the example task and desired output.
Example task
Invoke `$js-runtime-triage` on a local counter with no network requests. Ask why the displayed number does not change on the first click, retaining a minimal repro.What to check
The report names the failing stage, owning code, and verification result. The short script can reproduce the behavior.
Original SKILL.md on GitHub · Updated
Frequently asked question
Does a page that fails to update prove an engine bug?
Use the minimal example to separate execution, event binding, and layout behavior before assigning ownership.