DEDUPED We read 1,000+ AI sources. You read one email. Subscribe free

AI USE CASES

How to let an agent create worktrees and drive the app via Orca CLI with orca

Use the Orca CLI so an agent can spin up worktrees and click through a UI on its own.

Who it is forAdvanced builder automating a repeatable agent workflow instead of clicking through the app

The problemManually creating worktrees and prompting each agent does not scale when you run the same setup daily.

The outcomeA script or agent creates worktrees and drives the browser using Orca's own commands.

What you need first

  • macOS, Windows or Linux desktop (README badge lists all three)
  • At least one coding agent CLI installed and signed in with your own subscription, such as Claude Code, Codex or OpenCode
  • A git repository to work in, since each agent runs in its own git worktree
  • Optional: iPhone or Android phone for the mobile companion app
  • Optional: a remote machine reachable over SSH for SSH worktrees

Steps

  1. Read the Orca CLI overview docs to see the available commands.
  2. Run orca worktree create for a new task branch.
  3. Use the snapshot, click and fill commands to drive a page from a script or an agent.
  4. Wire the commands into your own automation once one run works.

Prompt for your agent

Using stablyai/orca's CLI, write a short script that runs orca worktree create for <branch name> and then uses snapshot, click and fill on <local page URL>. Verify each command's output before chaining them.

Caveat. Only the command names worktree create, snapshot, click and fill appear in the README excerpt, so check the CLI docs for exact arguments before scripting.

About orca

A desktop and mobile app to run Claude Code, Codex, OpenCode and other coding agents side by side, each in its own workspace, on your own subscriptions. Part of this week's top 10 repos: ranked #5 on Repo Radar. View stablyai/orca on GitHub.

More with orca

See all use cases for stablyai/orca

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page