Introducing a new way to review your PRs.

Read the announcement

stablyai / orca

Orca lets you run a fleet of bots with your own subscription (e.g. Claude Code, Grok, Agy, Codex). Available on desktop, mobile and remote runtime.

View on GitHub

34 documents · Updated Nov 20, 2026

overview

Knowledge Base updated: 2026-11-19

Orca knowledge base

Orca is an Electron-based coding-agent workspace with desktop, mobile, cloud relay, CLI, and automation surfaces.

The desktop main process owns native capabilities, persisted local state, runtime coordination, and browser/terminal resources. Renderers and mobile clients consume those capabilities through constrained IPC, relay, and remote transport contracts.

Critical state spans local workspace/session metadata, terminal and agent runtime state, AI Vault data, bot records, credentials, and cloud relay continuity records.

flowchart TD
  Desktop[Electron desktop]
  Renderer[Renderer UI]
  Preload[Preload contracts]
  Main[Main process]
  Relay[Local relay]
  Agents[Agent runtimes]
  ACP[ACP sessions]
  Terminal[PTY terminal runtime]
  Browser[Managed browser]
  Vault[AI Vault]
  Git[Git and reviews]
  Remote[Remote runtime transport]
  Mobile[Expo mobile client]
  Cloud[Cloud relay and push]
  Bots[Bot orchestration]
  Renderer --> Preload --> Main
  Main --> Relay
  Relay --> Agents
  Relay --> Terminal
  Main --> Browser
  Main --> Vault
  Main --> Git
  Agents --> ACP
  Main <--> Remote <--> Cloud
  Mobile <--> Cloud
  Main <--> Cloud
  Bots <--> Main
  Bots <--> Cloud

Glossary

  • ACP — Agent Protocol Client integration used to acquire and operate structured agent sessions.
  • AI Vault — isolated session-data and transcript service used by Orca runtime flows.
  • Relay — local protocol server that exposes runtime, filesystem, Git, and stream operations to clients.
  • Execution host — local or remote machine selected to run workspace services and agent-capable workloads.
  • Worktree — Git working directory managed alongside workspace session ownership and cleanup metadata.

Invariants

  • Renderer code reaches privileged desktop capabilities only through preload/shared contracts; evidence: src/preload/** and src/shared/**.
  • PTY consumers are coordinated through replay, ownership, and flow-control mechanisms; evidence: src/main/pty/** and src/main/relay/**.
  • Agent session presentation is derived from provider/ACP lifecycle state rather than renderer-owned process control; evidence: src/main/acp/** and src/main/agent-hooks/**.
  • Workspace and worktree retirement must preserve ownership and cleanup safety; evidence: src/main/workspaces/** and src/main/worktrees/**.
  • Remote clients reconnect through authenticated transport and continuity mechanisms rather than directly owning local runtime resources; evidence: src/main/remote/** and cloud/**.

Routing table