Preview and browser verification

Local preview

Package scripts, dev servers, local routes, and preview windows run on the Mac that owns the workspace. They do not move into Iterel Cloud.

Verify browser

For supported engines Iterel injects its own constrained browser tools into the run. The browser can reach only loopback task previews, and its actions, console evidence, and screenshots are reflected inside Iterel rather than hidden in an engine terminal.

Remote clients

A browser or phone connected to the user's online Mac can run gates and control a task through RemoteBridge. The live loopback preview itself does not travel. Remote clients receive receipt and verification state; screenshot transport is a later storage slice.

Task-only boundary

Open Preview from the task header. Iterel starts the configured development command in that task’s exact worktree and opens the detected server URL with live updates.

Closing Preview stops its managed server unless you used Open in to hand the URL to an installed browser. That keeps the server running for the external tab. Leaving or switching tasks always stops it, including a server kept alive by Open in.

You can capture a runtime snapshot back to Design as an inert frame. Preview is not a global browser, a Build-home canvas, or a Play action on a Design frame.

The connected browser is a separate tool for working in your signed-in Chrome session. Its screenshots do not count as proof that the task’s app passed browser verification. See Desktop tools.