Orca v1.4.241 lets you watch your agent click through its browser, and docks DevTools in the pane

When an agent drove Orca's browser, its clicks were invisible. Now a cursor glides to each spot before the agent clicks or types. In chat, a Show button jumps you to that page.

Slide text

You can now watch an agent click and type in Orca’s browser

A cursor lands on each spot before the agent acts, and its tab gets a badge. In chat, Show jumps to the page.

DevTools used to open in their own window. Now they dock inside the browser pane, right or bottom, and you can resize them or pop them out. Noisy tabs also get a mute button.

Slide text

DevTools dock inside Orca’s browser pane

Dock right or bottom, drag to resize, or pop out. Tabs playing sound get a speaker and mute, and a hovered link shows its URL.

A chat could run with different permissions from your terminal, because chats had their own default. Now new chats take each agent's setting from Settings, Agents. Existing chats keep the permission they saved.

Slide text

New chats start with each agent’s permission from Settings → Agents, like terminals

Gone

Settings → Chat no longer has its own permission dropdown

Kept

existing chats keep their saved permission

Per chat

a chat’s own permission menu changes only that chat

With one Claude or Codex conversation open in a terminal and a chat, two agents could write it at once. Now the chat won't send until you quit the agent in that terminal, or close it.

Slide text

A chat won’t send into a conversation a terminal is still writing

It asks you to quit the agent there or close that terminal. Then the next send goes through.

Hosts that only offer certificate keys failed in Orca's built-in SSH client. Now Orca retries through your system SSH. Saved port forwards return after a restart, and managed servers update without closing terminals.

Slide text

SSH hosts that failed in Orca now connect, and forwards come back

Certificates

certificate-only hosts retry over your system ssh

Forwards

saved port forwards return after a restart, and failures show why

Update anyway

updates a managed server while its terminals keep running

Hermes and Kimi panes now resume after Orca restarts, and Kiro reports status on its V3 engine. On four OpenCode two point oh releases, Orca refuses model picks, because those versions drop your first message.

Slide text

More agents pick up where they left off

Hermes, Kimi

panes resume after an Orca restart

Kiro

reports status on its V3 engine

OpenCode

Orca refuses model picks on 2.0.14, 2.0.15, 2.0.17 and 2.0.18, which leave the first message unsent

Terminals you already have open stay on the old terminal host until you close them. If your agents use Orca's browser, I'd update today: you finally see what they click.

Slide text

Terminals open before the update stay on the old terminal host until you close them

Agents in Orca’s browser? Update today.

Orca v1.4.241 release notes on GitHub