v0.1.1137 Aug 2026·DevTools, Tabs & interface

Visual DevTools: a live Console REPL and a Debugger panel

DevTools stops being backend-only. The engine already had a visual inspector (Elements, Console, Network pulled from the real cascade and layout), and the Debugger backend landed last release - this wires them into a panel you can actually use. The Console gains a REPL: type JavaScript and it evaluates in the LIVE page session, seeing the page's own globals and functions, and prints the result inline - a real console, not a sandbox. And a new Debugger tab surfaces the `debugger;` capture visually: enable it, reload a page that hits a breakpoint, and the paused function and every local and block variable at its real value appear in the panel, with a Resume button - read straight from the engine's own running scope. Behind it, the engine grew a real REPL that evaluates in a live session and returns the last expression's value, plus a Rust bridge exposing the debugger's pause state to the shell. DevTools moves 22 to 24; overall holds at 51.

Parity with the reference browser

74overall, as of v0.1.343

Web APIs / DOM surface42

Security architecture66

GPU / graphics acceleration68

DevTools / extensions72

Networking85

Media85

Accessibility85

Real-world site compatibility99

HTML parsing100

CSS parsing + selectors100

Layout: block / flex / grid / tables / writing-modes100

Paint + visual100

JavaScript language100

JavaScript performance (JIT)100

HTML parsing100

What changed 3 changes

Tabs & interface	Console REPL: a new input in the DevTools Console evaluates JavaScript in the page's LIVE session (Session::eval_repl), so it sees the globals and functions the page defined and returns the last expression's value; console.log output lands in the same console pane. Proven end to end: a REPL command reads a page global, calls a page function, mutates state that persists across commands, and surfaces a throw as an error rather than a crash.
Tabs & interface	Debugger panel: a new Debugger tab surfaces the `debugger;` pause visually - the paused function name and the full scope chain (each local and block variable at its captured value) read from the engine's running state, with Enable and Resume controls. Wired through a Rust bridge (debug_snapshot_json / debug_hits / debug_set_enabled / debug_resume) messaged to the thread-confined engine.
DevTools	The engine side is gate-tested: the live-session REPL (returns 105 from a page global, persists state, errors cleanly) and the Debugger JSON the panel reads (reason, function, hit count, and each scope variable at its value). Conformance gate 6375/6375 with native-JIT and no-nanbox green; the shell frontend typechecks and builds.