Orca’s latest release extends its built-in agent-skill installer to paired servers and SSH hosts. Developers can install skills from setup screens and choose separate browser profiles for repositories or workspaces. Shared profiles remain the default, and remote pages use their server’s profiles. The release also sets compatibility requirements for experimental native chat and keeps connector work disabled by default.
Orca, an application for working with coding agents, released version v1.4.239 with a built-in skill installer for local and remote work. Its release notes describe one-click installation from setup screens and installation or updates on paired servers and machines reached through Secure Shell, or SSH. Orca’s own installer replaces an external npx invocation. The desktop dialog and command-line tools use the same planning logic.[1]
Settings now let users assign new browser tabs a shared profile, a separate profile for each repository or one for each workspace. The default still shares a profile across work. Project-specific profiles provide separate sign-ins for local applications. Pages supplied by a paired server take their profiles from that server, and the preference applies when a new tab opens. Page menus gain more options, while failed loads receive clearer explanations.[1]
Users of experimental native chat are asked to update paired and SSH hosts along with the desktop application. Supported managed Linux SSH servers offer a recovery option after a stale-lock refusal, with confirmation that no other machine sharing the home directory is running Orca. Connector groundwork remains disabled by default. These release details come from the project’s own notes.[1]
