x9 Agent Skills v2.3.0
Highlights
- Added an extensible
chrome-devtoolsMCP allowlist, initially containingavito.ru; matching domains bypass the browser extension in both runtimes and preserveagent-edgeonly as the unattended fallback. - Synchronized the published global-instruction examples with the current question-format and browser-retrieval fallback rules while keeping their shared core byte-identical.
- Made
x9-idea-criticturn upheld criticism into a self-contained stronger proposal, with a change map and verdict-specific handling for revised, surviving, killed, or unproven ideas. - Hardened
x9-loop-engineeringwith conditional patterns for authoritative derived state, recoverable public lifecycle mutations, version-scoped continuity, task-first self-repair, and evidence-bound realized execution traces. - Made repository-backed diagram creation source-first, preserve existing structure and supported fonts until rendered proof passes, and use a clipboard round trip for faithful browser verification.
- Tightened Excalidraw structure checks for escaped control tokens, native soft wrapping, semantic hard breaks, deleted bindings, and target-version normalization.
- Strengthened rendered diagram evidence with content-viewport fit checks, post-normalization stability, explicit whole-view versus scrollable delivery, and protection from blocking native choosers.
Install / update
- Full-plugin users can update in place; no data or skill-name migration is required.
- Selective Codex installations that use an allowlisted browser target need the
chrome-devtoolsMCP route from thex9-browser-sessionsetup guide.
Compatibility
- Browser routing outside entries in the
chrome-devtoolsMCP allowlist is unchanged; the list currently routesavito.ruthrough MCP in Codex as well as Claude Code. - Existing
x9-idea-criticmodes and provider routes are unchanged; successful critiques now include an evidence-grounded next version of the idea. - Existing simple and linear workflow guidance is unchanged; the new loop recovery, versioning, self-repair, and lineage patterns apply only when those mechanisms exist.
- Existing Excalidraw scenes remain supported, but invalid control text, dangling bindings, unstable wrapping, or unsupported hard line breaks now fail the stricter checker until corrected or explicitly allowed.
Breaking changes
None.