Browser previews
Loopback browser nodes, static and package previews, and safety limits.
The Browser app node shows localhost development previews inside the canvas without giving the webview general network or filesystem power.
What you can do
| Action | Who can request it | Notes |
|---|---|---|
| Show URL | Global Agent, Agent CLI, External MCP | Only loopback hosts (127.0.0.1 / localhost) |
| Close node | Same | Closes the browser node |
| Open project path preview | Global Agent + workspace-bound Agent CLI | Starts a bounded static or package preview under the project |
| Screenshot / Move to | You (node header) | Same presentation actions as other apps |
External MCP clients may display/close a loopback URL but cannot start a
project-relative preview (openPath is denied for External).
Open a browser node
- Canvas Apps → Browser, Command Search, or an agent tool call.
- Point it at a running local server, or ask the Global Agent to open a project preview path.
- Resize as needed; undersized embeds may pause with a placeholder depending on product rules for media hosts.
Safety model
- Previews are managed by the native runtime, not arbitrary remote URLs.
- Only loopback display is allowed for generic “show this URL” flows.
- Preview servers are torn down with the session / access gate / app shutdown.
- The node does not grant Tauri filesystem capabilities to page content.
Tips
- Prefer
127.0.0.1over machine LAN IPs when agents open previews. - If a preview fails, check that the project path exists and the package/static root is valid, then retry from the agent or reopen the node.
- Screenshots require the full node frame to be visible in the main window.
Related: Canvas nodes, Agents, Security.