Per-worktree browser

Every DevAgent worktree has its own browser. It's a real Chromium window — address bar, history, devtools — embedded in a pane. Tabs are scoped to the worktree, so the app you're building against stays out of the way of your other work.

Controls

• Address bar with history and fuzzy URL completion. Non-URL text searches with your Default Search Engine — the same engine the new-tab omnibox uses. Prefix a query with ? in the + field to force search.
• Back / forward / reload / stop. Hover the reload control for the normal-reload shortcut; right-click (or long-press) for Reload and Hard Reload with their shortcuts — hard reload bypasses the cache when you're iterating on local frontend assets.
• Cmd-F — find in page.
• Cmd-T — new tab, scoped to this worktree.
• Cmd-Shift-T — reopen last closed tab.

Worktree scoping

Tabs are filtered per worktree. Switching worktrees restores that worktree's browser tabs and scroll positions.

Link routing

Under Settings → Browser → Link Routing, choose whether http(s) links from the terminal, markdown, and editor open in DevAgent's per-worktree browser or the system browser.

A nested Hold Shift… toggle inverts that default for one click with the platform modifier (⇧⌘-click on macOS, Shift+Ctrl+click on Windows / Linux):

• When links open in DevAgent, the modifier sends one link to the system browser.
• When links open in the system browser, turn the toggle on so the modifier opens one link in DevAgent's built-in browser instead (plain click stays system).

Remote/SSH sources still never open inside DevAgent's browser, even with the modifier. Terminal links can also open a click popover with DevAgent Browser / System Browser — see Terminal → Link actions.

Downloads

Browser downloads appear in a shelf under the toolbar while they are active or recently completed, with actions to cancel an in-progress download, open a finished file, show it in its folder, or dismiss the row.

Share as artifact

Local HTML files opened in the worktree browser can use Share as artifact in the toolbar to mint a public view link through your signed-in DevAgent account (same opt-in gate and management surface as Markdown). Relative HTML assets are not uploaded — share a self-contained file or use absolute asset URLs. See Settings → Artifacts and CLI reference → Artifacts.

Viewport-size emulation

Set a custom viewport size on a browser tab to test responsive layouts without resizing the whole pane. DevAgent uses Chrome DevTools Protocol device emulation under the hood, so the page sees the emulated dimensions in window.innerWidth and media queries.

Automation

The browser is also scriptable by agents via the DevAgent CLI — devagent snapshot, devagent click, devagent fill, and so on. Same browser you interact with, same tabs.

Next steps

• Design Mode — turn the browser into a pointer-to-code feedback loop.
• Browser-use profiles — run the browser with a specific login, cookie jar, or user agent.