All directories
AgentEngineeringProduct

Orca

stablyai/orca

Desktop (and mobile) orchestrator for running many coding agents in parallel — each in its own worktree, tracked in one place.

00

GitHub repository

https://github.com/stablyai/orca
01

Overview

Orca is an ADE (agent development environment) for fleets of coding agents. Run Codex, Claude Code, OpenCode, or Pi side by side on your own subscriptions, each in an isolated worktree, with mobile steering when you’re away from the desk. Repo (copy/paste): https://github.com/stablyai/orca

SaaSAgencyOther

Work with LimeDock

Using this skill? LimeDock can wire it into a durable automation you own.

Agents are a starting point. LimeDock turns the workflow into production automation your SaaS team owns — not another prompt library.

We sell owned automations for SaaS teams — live workflows that plug into Slack, CRM, and your internal platform — not just a skill list.

02

Link

https://github.com/stablyai/orca
03

Installation guide

Not installed into LimeDock.

1. Copy: https://github.com/stablyai/orca 2. Download the desktop app from onorca.dev / GitHub releases. 3. Connect the coding agents you already subscribe to. 4. Optional: install the mobile companion to monitor/steer.

04

How to use it

**Simple example** You want three agents working three bugs without stomping the same branch.

1. Open Orca. 2. Spawn Agent A/B/C each on its own worktree. 3. Assign one bug per agent. 4. Watch progress in one UI; nudge from your phone if needed.

05

Example prompts

  • How does Orca isolate agents with git worktrees?
  • What’s the fastest path to run Claude Code and Codex side by side?
  • When is Orca overkill vs one local Claude Code session?
06

Use cases and examples

  • Parallel coding agents without branch collisions
  • Using existing Claude/Codex subscriptions in one cockpit
  • Mobile check-ins on long agent runs
07

Prerequisites

  • Subscriptions/CLI tools for the agents you want to run
  • Git repo that supports worktrees
  • Desktop OS supported by Orca
08

Tips

  • Name worktrees after tickets so humans can find them later.
  • Parallel agents multiply review load — budget human QA time.