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.
- Back / forward / reload / stop.
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.
Cookie import from Chrome / Edge
The first time you open a browser tab, Orca offers to import cookies from your default Chrome or Edge profile. One click and you're signed into the same sites you already use, scoped to that worktree. Re-run the import later under Settings → Browser.
Search engine
Address-bar search defaults to Google. To use Kagi instead, paste a Kagi private session link under Settings → Browser — Orca stores it encrypted and routes omnibox queries through your Kagi session without re-authenticating.
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.
