Per-worktree browser
Every Orca 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. Double-click a word to select it, like other browsers. - 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.- Open ⋯ → Open browser devtools to inspect the current page. You can dock the tools to a side of the pane, resize them, or pop them out when you need more room for the page.
- A tab that is playing sound shows a speaker indicator; select it to mute or unmute that tab. When you hover or focus a link, Orca shows its destination at the bottom of the page.
- Use Annotate and its arrow menu to annotate or grab a page element or draw on a screenshot. The ⋯ menu contains browser actions, including zoom, viewport size, profiles, and extensions. Non-default zoom and viewport sizes appear in the address field; select a chip to reset it. See Design Mode.
Cmd-T— new tab, scoped to this worktree. On macOS,Cmd-Option-Bopens a browser tab in a split to the right; you can change this shortcut in Settings → Keyboard.Cmd-Shift-T— reopen last closed tab.- Links and
window.openfollow Chrome's routing: a page link or script-opened tab that would open a new tab in Chrome opens a new Orca tab, using the opener tab's browser profile. Named or OAuth-style popups can still open in a separate window. - New tabs load in the background even when they are not active, so their URL, title, and navigation state are ready when you switch to them. Restored inactive tabs may still load lazily.
- HTML previews expose their document path in the address bar. Enter a web URL to convert the preview into a browser tab in place; enter a workspace HTML path in a browser tab to convert it back to a preview. Back crosses the conversion when the tab has no intervening history.
Orca shortcuts, split focus, and mouse back/forward buttons continue to work while a page has focus. Links opened from a terminal or chat open beside the pane that supplied them. When an agent uses the browser, its cursor and activity badge appear on the page; select the browser link in chat to jump to that page.
Worktree scoping
Tabs are filtered per worktree. Switching worktrees restores that worktree's browser tabs and scroll positions.

Remote workspaces
For a workspace on a paired Remote Orca Server, new browser pages render on this desktop by default while HTTP(S), WebSocket, DNS, and loopback traffic still go through the remote host. Input, selection, and popups stay native to this device without changing the page's network identity. The host indicator in the browser toolbar shows where traffic is going.
Under Settings → Browser → Remote server workspaces, choose This device or Server (streamed). The choice applies to new pages only; it does not move a page that is already open. If a locally rendered remote page cannot start, Reopen on server opens a new server-hosted page at its last address (signed-in or form state may differ).
For SSH workspaces, Browse through SSH workspace hosts controls whether browser traffic and DNS go through the workspace's SSH host or this device. Downloads from a client-hosted remote page stay on the remote workspace host, and uploads are staged there before the page receives them.
Link routing
Under Settings → Browser → Link Routing, choose whether http(s) links from the terminal, markdown, and editor open in Orca'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 Orca, 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 Orca's built-in browser instead (plain click stays system).
A capability-verified paired runtime or an eligible SSH workspace can offer the same Orca/system-browser choice for its terminal links. Links from older runtimes remain system-browser only. See Terminal → Link actions.
Password manager
Enable the password manager in Settings → Browser to save and fill logins in Orca’s browser. After signing in, you can save the login from the password offer in the address bar; select a saved login in a sign-in field to fill it. Use Manage in browser settings to edit logins or import passwords from Chrome and other supported browsers or a CSV file.
Each browser profile has its own vault, encrypted using your operating system’s secure storage. The vault is unavailable if secure storage is unavailable. It works for local and SSH workspace pages in the desktop browser; streamed paired-server pages and the web client do not have a vault. See Browser profiles.
Chrome extensions
To install an extension, turn on Settings → Experimental → Browser extensions and restart Orca. Open the Chrome Web Store in an Orca browser tab and choose Add to Orca. Extensions run only in local browser profiles. Ad blockers can be installed but do not block yet, and some extensions, such as Tampermonkey, do not work.
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 address field to mint a public view link through your signed-in Orca account (same opt-in gate and management surface as Markdown). Shared content is limited to 10 MiB per file. 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. Orca 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 Orca CLI — orca snapshot, orca click, orca 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.