Orca bots now get their own tools on Grok, OpenCode, Pi and Antigravity
6 hours ago
Orca bots now get their own tools and identity on Grok, OpenCode, OMP, Pi and Antigravity. Also in Orca v1.4.264 and v1.4.265: Slack threads that show a bot's work, a Gmail trigger spoofing fix, opt-in automatic updates, Orca's own Claude and Codex installs, and a steadier desktop with many chats.
Links
- Orca v1.4.265 release notesgithub.com
- Orca v1.4.264 release notesgithub.com
- Compare viewgithub.com
- Tools and identity for every managed agent, PR #44837github.com
- Connector category icons, PR #44662github.com
- Slack turn activity and whole long answers, PR #44384github.com
- Slack connect dialog, PR #44383github.com
- Gmail trigger sender match, PR #44831github.com
- Access confirm dialog, PR #44580github.com
- Automatic desktop updates, PR #44541github.com
- Orca's own Claude, PR #43860github.com
- Orca's own Codex, PR #43919github.com
- The repositorygithub.com
Ask about this presentation
Chapters
0:00Tools and identity for every bot
0:15Slack threads show the work
0:27Gmail triggers match the real sender
0:38A clearer access warning
0:49Automatic desktop updates
1:01Orca installs Claude and Codex
1:11Chat commands find their workspace
1:24Busy desktops stay responsive
1:38Run bots or many chats? Update.
Show transcriptHide transcript
Orca bots now get their own tools and identity on every agent. Grok, OpenCode, OMP, Pi and Antigravity sessions start with their tools, and their Orca commands stop running as you.
A Slack thread now shows what the bot's turn is doing, like running the tests, instead of one fixed Working line. Long answers arrive whole, up to 32 kilobytes.
A Gmail trigger used to match an address typed into the display name, so anyone on a shared domain could start your automation. Now only the real sender counts.
Before a bot connects, the access dialog now leads with one line: they'll act as you on this computer. Red marks full access or your Google account.
Orca can now download, install and relaunch itself, once you switch on Automatic updates in Settings. It waits while a terminal is live or launching, or a WSL move is running.
On a host with no Claude or Codex, a chat's Install button now downloads Orca's own copy, no terminal needed. Your own install still wins.
When a Chat agent opens a browser tab from outside its workspace, the tab now lands in that chat's workspace, not the one in focus. If Orca can't tell, the command is refused.
With dozens of chats streaming, a new chat's message now goes first instead of waiting about thirty seconds. Long tab strips render only the visible tabs, and a terminal scroll loop that froze the window is fixed.
I would say yes, update, if you run bots or many chats. Automatic updates stays off until you switch it on, and Slack's live status needs connector support. The limit: phone features need a new mobile build.
Up next
1:35Orca v1.4.263 runs Hermes in Chat and opens Chrome extension side panels
@orca
1 day ago
1:36Orca v1.4.262 runs 150 agent chats in a third of the memory and adds git blame
@orca
2 days ago
1:27Orca v1.4.261 brings Cursor into Chat and frees memory from idle browser tabs
@orca
2 days ago
1:30Orca v1.4.259 clears out the workspaces your agents leave behind
@orca
5 days ago
1:30Orca v1.4.258 runs GitHub Copilot in Chat and scrolls phone chats again
@orca
1 week ago
1:34Orca v1.4.257 freezes less on long agent chats and keeps your browser notes
@orca
1 week ago
1:35Orca v1.4.256 sets up dictation in one click and keeps your phone drafts
@orca
1 week ago
0:57Orca v1.4.255 puts every agent from every desktop on your phone
@orca
1 week ago
1:33Orca adds a Git Graph tab, and /btw asks a side question mid-chat
@orca
1 week ago
1:32Orca v1.4.252 forks a chat from any reply, and /plan plans before it builds
@orca
1 week ago
1:39Orca v1.4.251 sends any file or terminal selection to your agent's chat
@orca
1 week ago
1:46Orca can keep idle chat agents running, and many terminals no longer crash it
@orca
2 weeks ago


