CanvasCode 1.52.3: right-click opens the WebKit inspector in the browser panel

What changed: in CanvasCode 1.52.3, released on August 16, 2026, right-clicking inside the browser panel and choosing "Inspect Element" opens the WebKit Web Inspector, the same inspector Safari uses, because the panel is a WKWebView. Until 1.52.2 the panel could show a page and reload it, and there was no way to open an inspector on it at all.

In CanvasCode the browser is a panel like any other. It sits next to the agent writing the code, showing the page that just changed. Until this release it was half a browser: you could look, you could reload, and the moment you wanted to know why a box was 4 pixels off you had to leave for Chrome.

What the inspector gives you inside the panel

Three things cover almost every reason you used to switch apps. You select an element and see where it lives in the DOM tree. You edit CSS and the page answers immediately, in the panel, with the agent beside it looking at the same screen. You follow the network requests the page made, and you run JavaScript in the console against the page as it is loaded right now.

The module panels, the small pages you keep inside the canvas, got the same thing on the same release.

What this inspector is not

It is the WebKit Web Inspector, not Chrome DevTools, and that difference is worth stating plainly because it decides when the panel is enough and when it is not. You are looking at how WebKit renders your page, so a layout bug that only appears in Blink will not appear here. Chrome extensions do not exist in this panel, and neither do the Chrome specific audit panels. If your bug is "it breaks in Chrome", this inspector will not find it, and switching apps is still the right move.

What it does cover is the loop that made you leave in the first place: read the tree, change a rule, watch the request, ask the console. That loop now happens in the window where the work already is.

The way in is the usual one: right-click the page, "Inspect Element".