Skip to main content

Browser Panels

The Browser panel kind: a Chromium pane in the grid or dock with per-project sessions, URL history, host approval, find in page, DevTools, the Element Picker on local pages, and the limits of agent access.

Updated
Reviewed

Overview

A Browser panel is a Chromium pane that lives in your workspace like any other panel. It is meant for looking at something running locally (a dev server, a staging build, a docs site you keep open while an agent works) with enough developer tooling attached that you don't have to leave for a real browser.

A Browser panel is where the toolbar's links launcher opens a local address when no Dev Preview is already serving it, and where a Cmd/Ctrl-clicked localhost link in a terminal lands. Outside addresses from the launcher open in your system browser instead.

In a window on a remote host, localhost in a Browser panel means the host's localhost. Opening http://localhost:5173 forwards the host's port 5173 to the same port number on this machine, so the page keeps its address. If that port is already in use here, Daintree says so rather than picking another. See Dev Servers and localhost.

Opening one

The launcher in the toolbar is the primary route: open it and pick Browser, or press Option-Command-B Control-Alt-B Control-Alt-B to open one in the current worktree. The panel palette (Command-N Control-N Control-N ) still works and lands in the same place. On a fresh profile the browser and dev-preview buttons sit in the launcher's panel tray rather than as standalone toolbar buttons; existing saved layouts are untouched.

A new Browser panel starts at localhost:3000. Type another address into the address bar to navigate elsewhere.

Browser panels can move to the dock, like terminals, Dev Preview and the file panels (Review and the diff viewer are the exceptions): the page opens from its dock chip rather than vanishing. When a Browser panel leaves the grid, focus returns to whatever you were last looking at rather than jumping to the first terminal. Like every panel kind it can also be presented as a dialog and promoted back into the grid. See Terminals & Panels.

Sessions and logins

Browser panels no longer share a single Chromium session. Each project gets its own persist:browser-<project> partition, created lazily the first time a panel attaches, so cookies, localStorage and IndexedDB for a site like localhost:3000 (or a forge you signed into) belong to that project and do not bleed into the next one. Two projects can be signed into the same app as different users without fighting over one cookie jar.

Dev previews are partitioned more narrowly still, per project, worktree and panel. Every one of these partitions is locked down to the same untrusted permission set as it is created: camera, microphone, geolocation and the rest are denied.

Toolbar

From left to right:

  • Back / Forward: sourced from Chromium's own navigation history, so the tooltips name the page you would land on rather than guessing from a local stack. Long-press either button, right-click it, or press ArrowDown on it for the list of earlier (or later) pages, and jump straight to one
  • Reload: Shift+click for a hard reload that bypasses the HTTP cache. The tooltip says so. While a page is loading the button becomes Stop loading
  • Address bar: type a URL to navigate, with a history dropdown described below. A lock or globe at its left shows whether the page is https or http, and the resting address shows the host first with the path after it. Copy URL sits at the right end of the field. When the page zoom isn't 100%, a zoom chip appears there too; click it for zoom out, zoom in and Reset
  • Element Picker: shown while the panel has a local page open and belongs to a worktree. See Element Picker
  • Copy screenshot to clipboard (camera icon): captures the viewport as a PNG and copies it to the clipboard
  • Open in external browser: hands the current URL to your system's default browser
  • More page actions (…): page zoom (Zoom in, Zoom out, Actual size) and Toggle DevTools, which opens Chromium DevTools for the panel in a separate window

In a narrow panel, Copy URL moves into More page actions so the address stays readable.

There is no keyboard shortcut bound to hard reload by default; the same action is in the command palette as Hard reload browser (browser.hardReload), so you can bind it yourself in Keyboard Shortcuts.

Note
Browser panels do not capture the page's console. That tooling lives in Dev Preview, whose drawer has Output, Console and Diagnostics tabs, and it is the dev-preview panel that browser.getConsoleMessages reads over MCP. For a Browser panel, use DevTools.

Element Picker

The Element Picker that every Dev Preview has works in a Browser panel too, on a local page. Its button, Element Picker, sits after the address bar while the panel shows an http or https page at a local address and the panel belongs to a worktree. A local address here is localhost or a name under .localhost, .local, .test or .internal, 127.x, [::1], 0.0.0.0, [::], or a private 10.x, 172.16.x to 172.31.x or 192.168.x address. On any other page the button is hidden, except that a picker you already switched on keeps its button so you can switch it off.

Switch it on and pick an element on the page. The picker traces the element into the panel's worktree as far as the page reports its source, and lets you write a request about it and send it to an agent in that worktree, one already running or a new one. If the page is served from a localhost server that Daintree can see is running in a different worktree, it doesn't trace into this one and tells you to open the page in that worktree instead. It is the same tool, with the same strip and drawer, as in Dev Preview.

The address is checked again on every navigation. Follow a link or a sign-in redirect to a page that isn't local and the picker is removed from that page; it comes back if you return to a local page with the picker still switched on. A Browser panel hosts only the picker: Dev Preview's Output, Console and Diagnostics drawer stays in Dev Preview.

Address bar and history

Focus the address bar and a dropdown opens with up to five suggestions, ranked by frecency: visit count weighted by how recently you were last there, in buckets from 4 days out to 90. Each row shows the page favicon, then the title and URL. Typing filters by substring against either.

ArrowDown and ArrowUp move through suggestions, Enter navigates to the highlighted one, Escape dismisses the dropdown. With no dropdown open, Escape works the way it does in Chrome: on an address you have edited it puts the current address back, selected, without leaving the field; on an unchanged address it hands focus back to the page. Hover a row and a small × appears at its right edge to remove that entry; from the keyboard, Shift+Delete or Shift+Backspace removes the highlighted row, and a live region announces the removal.

History is per project, capped at 500 entries, and entries older than 90 days age out. Favicons come from the page's own favicon events as you navigate, debounced and stored with the entry; an inline data: favicon larger than 8 KiB is dropped to keep the store small, and that row falls back to a globe icon. The unfocused address bar shows only a scheme indicator (a lock for https, a globe for http), not a live page favicon.

Tip
URLs that look sensitive are kept out of the address-bar history and the back and forward history lists. OAuth callbacks carrying code and state, signed S3/GCS/Azure URLs, URLs with embedded basic-auth credentials, and URLs with token fragments are excluded before the entry is persisted, so they don't reappear in the dropdown. This filter covers those lists only: the panel's own saved state, which restores its page and back and forward history after a relaunch, can still hold a visited URL.

Host approval

The address bar accepts any http: or https: URL, but a host that isn't obviously local is confirmed before it loads. Type a new host into the address bar, or pick one from the back or forward history list, and a banner appears across the top of the page area, under the toolbar: "Allow browser panel to load hostname?" with an Allow button and a dismiss ×. Nothing loads until you answer. Choose Allow and navigation proceeds immediately. The approval holds for this pane while Daintree saves the hostname to this project's approved hosts. If that save fails, the current pane still has your approval, but another pane may ask again. The Linux release update also keeps this banner above a previous page's load-error overlay and merges the approved host without reverting other project settings.

Approve a new public host before loading it

Some hosts never prompt:

  • localhost, 127.0.0.1, ::1
  • Any host under .localhost, .test, .local, or .internal
  • Loopback, RFC 1918 private, link-local and IPv6 unique-local addresses: 10.x, 172.16.x through 172.31.x, 192.168.x, 169.254.x, fc00::/7
  • 0.0.0.0, which is rewritten to localhost before any check runs

Everything else prompts when you enter it, unless you approved it before: public hostnames and IPs, and bare hostnames with no dot other than local, test and internal. The prompt is for addresses you give the panel. A page that is already loaded can follow its own links and redirects to public http: and https: sites without one. host.docker.internal is implicitly allowed because it ends in .internal. The check classifies the hostname string and IP literal; it is not a DNS-based guarantee about where a name resolves. Credentials embedded in a URL are stripped before it is used.

Note
Restored URLs skip the prompt. If a panel was pointing at a host when you quit, reopening Daintree puts you back on that page: this restores the page that was open when the panel was saved.

Approved hostnames are stored in your project's local-scoped settings under browserAllowedHosts. They are never written to .daintree/settings.json, so they aren't committed to git or shared with your team. The file lives outside the project directory, in Daintree's per-user data folder:

~/Library/Application Support/Daintree/projects/<project-id>/settings.json

%APPDATA%\Daintree\projects\<project-id>\settings.json

~/.config/Daintree/projects/<project-id>/settings.json

Warning
There is still no Settings UI for reviewing or revoking approved hosts. To revoke one, edit that JSON file and remove the entry from browserAllowedHosts. The folder is keyed by the project's stable id, which survives relocation; do not recompute it from a moved path. Close Daintree before editing local settings and keep a backup of the file.

Find in page

Press Command-F Control-F Control-F to open the find bar in the top-right of the webview. It has a Find in page field, a Match case (Aa) toggle, a match counter ("3 of 12", or "No results"), previous and next buttons, and a close button. The search runs as you type, and the shortcut works even when the page itself has keyboard focus.

Move through matching text without leaving the page
ActionShortcut
Open find barCommand-F Control-F Control-F
Next matchEnter, or Command-G Control-G Control-G
Previous matchShift+Enter, or Shift-Command-G Control-Shift-G Control-Shift-G
Close find barEscape

Dev Preview uses the same find bar, and the shortcuts are identical there.

Cross-origin navigation

A page in a Browser panel can follow http: and https: links and redirects to external domains without a host prompt, which is what makes OAuth and OIDC flows work: a localhost app can redirect through an external identity provider and back again. If a navigation is blocked (a non-HTTP scheme, for example), a banner reads Can't open host here (or Can't open this link here when there is no host to name), with the full URL beneath it, and offers Open in external browser and Copy URL. It auto-dismisses after 10 seconds, or clears on the next successful navigation. If handing the URL to the system browser fails, the banner changes to Couldn't open in external browser and offers Retry.

JavaScript dialogs

When a page calls alert(), confirm() or prompt(), Daintree renders it as a styled in-app modal rather than an OS-level dialog, which keeps focus inside the panel and avoids blocking the main process.

  • Alert: the message with an OK button. Escape also dismisses it
  • Confirm: Cancel and OK. Enter confirms, Escape cancels
  • Prompt: a pre-filled text input alongside Cancel and OK

Several dialogs arriving at once are queued and shown one at a time, and focus returns to whatever opened the modal session once the queue drains. If the page navigates away or its renderer crashes, queued dialogs are dropped rather than left on screen: the page context behind them is gone, so they could never receive a meaningful answer.

When the page misbehaves

If the panel's renderer process dies, Daintree reloads it once on its own. A second crash within a minute stops the loop and shows a Page process crashed banner that names the reason and exit code and offers Reload. If the page stops responding (usually a long-running script), a Page not responding banner appears with the same reload escape, and clears itself if the page recovers. Both are dismissible, and neither takes the panel down with it.

A page that fails to load is replaced by a named error (Connection failed, Page load timed out, Certificate error, Load cancelled or Unable to display page) with Retry and Open in external browser. Like Dev Preview, a background panel can be paused under memory pressure ("Browser paused to save memory") and reloads when you open it.

Agent and MCP control

The in-app Assistant's Full tool set exposes browser.getConsoleMessages for a Dev Preview panel. It reports an explicit error if pointed at a Browser panel, which has no captured console. Navigation (browser.navigate, browser.openUrl) and browser.captureScreenshot are on no tier, so no agent moves a panel or captures it through Daintree. None of these is on the external API-key MCP tool surface. Beyond those, the panel's own controls (back, forward, reload, hard reload, zoom, copy URL, DevTools, console toggle, open external) exist as actions so they can be bound to keys or driven from the command palette.