Which agents work with it?

Any agent that reads skills from a directory. Claude Code, Codex and Gemini CLI read it natively; Cursor and VS Code connect over MCP.

The voice runs on your own machine, so there is nothing to meter. The first run downloads it, about 340 MB.

Yes. The skill is MIT-licensed and the authoring format is public.

Create

Orca v1.4.226 puts your Jira sprint on a board and lets agents update the tickets

1 hour ago

@orca Subscribe

Orca v1.4.226, the IDE for coding agents: Jira issues as a sprint board, an orca jira command that lets agents read and update tickets, the Orca phone app opening workspaces on your Orca servers, a permission mode per Claude and Codex chat, and WSL distros as Orca hosts on Windows (experimental). Release notes: https://github.com/stablyai/orca/releases/tag/v1.4.226 Compare: https://github.com/stablyai/orca/compare/v1.4.225...v1.4.226 Download: https://onorca.dev/download

Ask

Ask about this presentation

Answers are generated from this presentation.

Chapters

0:00Your Jira sprint as a board
0:13Agents read and update Jira tickets
0:28The phone app opens server workspaces
0:41Each chat sets its own permissions
0:55A WSL distro as an Orca host
1:09Terminal chats resume as native chats

Show transcript

Your Jira sprint as a board

Orca now shows your Jira sprint as a board

Orca's Jira issues panel in Board view with Current sprint on: To Do, Review, Done and Waiting for release columns

Drag a card through the moves your Jira workflow allows.

Orca's Tasks panel now shows your Jira issues as a board, narrowed to the current sprint with one switch. Drag a card, and Orca offers only the status moves your Jira workflow allows.

Agents read and update Jira tickets

Agents can now read and update your Jira tickets

orca jira: read, create, comment, assign, change status
Account: the Jira login already connected to Orca
Failed writes: never print success and never retry on their own

Your agents can work Jira tickets too. The orca jira command reads and creates tickets, comments, assigns people and changes status, through the Jira account already connected to Orca. A failed write never reports success.

The phone app opens server workspaces

The Orca phone app now opens workspaces on your Orca servers

Phones need the new app release first.

Orca's phone app listing workspaces on Local Mac, a Lima VM, a ThinkPad marked Update needed, and a disconnected build server

Orca's phone app now opens the workspaces on every Orca server your desktop connects to, starts new ones there, and drives the web pages they open. Phones need the new app release first.

Each chat sets its own permissions

Each Claude and Codex chat now sets its own permissions

A change applies before your next message.

The permission menu in an Orca chat: Ask for approval, Accept edits, Approve for me, Full access

Each Claude and Codex chat in Orca now has its own permission mode, from Ask for approval up to Full access. A change takes effect before your next message, so a running reply is never cut off.

A WSL distro as an Orca host

On Windows, a WSL distro can now be an Orca host

Behind the Experimental switch “WSL distros as hosts”. WSL 1 isn’t supported.

Orca's Add a project dialog with Ubuntu (WSL) listed as a connected WSL distro host

On Windows, a WSL distro can now be an Orca host, the way an SSH machine is, so projects and terminals run inside Linux. It's behind an Experimental switch, and WSL 1 distros aren't supported.

Terminal chats resume as native chats

OpenCode, Grok and OMP terminal chats now resume as native chats

Codex chats: ask you to update an old Codex, and show context use
Cmd+J: finds Jira, Linear, GitHub and GitLab tasks by keyword

Release notes on GitHub

OpenCode, Grok and OMP conversations from a terminal now resume as native chats. Codex chats ask you to update an old Codex, and Cmd+J finds tasks by keyword. The rest is in the release notes on GitHub.