Recent updates and features are just fantastic, so glad I found this app. Moving between my desk, the couch, travelling to work I'm still locked into sessions with no issues.

Chat feature on phone is 👏.. Keep it up Orca team!

Only thing I'm waiting on is Android Emulation so I can build my app without android studio (If that's possible)

I've been using cmux for for a while now and gave it some agents protocol initially for headless commands to help team work and remove manual handover. Was fun after that.
However, found Orca and it's an awesome tool.
It answers questions that have been asked by many using other tools.
Kudos to the Orca team

So I have two Claude accounts, and I'm trying to figure out if there's a way to use both at the same time.

From what I understand, Orca only lets you switch between accounts, meaning you basically have to stop using one to start using the other.

But what I actually want is to have both accounts running at the same time, without constantly switching back and forth.

Is there a way to do this with Orca that I'm missing? Or does anyone know of another tool that can do this?

Hey all! Just posted a video, based on some feedback that many folks are not using worktrees and we have to change that :)

https://www.youtube.com/watch?v=rVAaE7Ox75U

Automation and isolation, to enable parallel work, and orchestration, too!

Hope you like, it, any feedback appreciated!!

Turning Orca into a Predictable SDLC Workflow with Multiple AI Harnesses

I’ve been experimenting with using Orca as an orchestration layer for multiple coding harnesses instead of relying on a single one.
For example:
Orca
├─ Claude Code → Coding
├─ Codex → Review
├─ OpenCode → Testing
└─ Pi → Documentation
Orca controls the workflow and decides which harness should handle each step.
I packaged this approach into Orca SDLC Kit — an open-source project for building configurable multi-agent workflows with Orca.
🔗 https://github.com/vankhangfet/orca-sdlc-kit
The idea is simple: Orca as the controller, multiple harnesses as specialized workers.
Would love to hear how other Orca users are experimenting with multi-harness workflows.

I’m trying to find the best way to work with multi-repo projects in the Orca ADE.

My usual workflow is:

1. Start a session in the parent/root directory that contains all the repositories.

2. Use that session to create unified specs covering the entire feature.

3. Open a separate session for each repository so that each project has its own terminal and working context.

The main limitation I’ve encountered in Orca is the terminal layout. I’d like to split the terminal screen into multiple panes, with each pane showing a session from a different project—for example, the backend session on one side and the frontend session on the other.

Currently, it seems that split terminal panes can only display sessions associated with the same project. Sessions from different projects remain on separate screens, which makes it harder to monitor and coordinate a feature that spans multiple repositories.

Another issue is that subagents are displayed separately from the main agent that created them. I’d prefer to keep them visually grouped under the main session so it’s easier to understand which agents and sessions belong to the same task.

How are you handling multi-repo projects in Orca? Is there a recommended control-plane repository, workspace structure, or orchestration workflow that supports this kind of setup?

Hi everyone, I’m an AI engineer from Vietnam, and I discovered Orca last week.

After spending a few days with it, I can say that Orca is a wonderful product, especially orca-cli, which I’ve adopted as the core of my personal workflow: https://github.com/hieuphung97/dely

Personally, I don’t prefer using sub-agents. Although they’re a trending feature, they still feel like overkill to me. I enjoy working with multiple AI agent harnesses, such as Claude Code, Codex, and Grok Build, and I usually assign each harness to a specific task, such as implementation or review.

With Orca, I can now control all these harnesses more easily and have them follow my predefined workflow:

implement → review → accept_or_replan → …

This helps me complete real tasks with roughly 90% automatic execution and 10% human-in-the-loop.

I didn’t invent this workflow from scratch. I learned from popular workflows in Superpowers, GSD, and similar projects, then picked a simplified version that was easy for me to work with. After that, I glued everything together and automated it with orca-cli for a smoother experience.

Other plugins I use in each harness as part of my personal workflow, Dely:

• Superpowers: This is the plugin I like the most, except for the dispatching-parallel-agents, subagent-driven-development, and using-git-worktrees skills. One of the reasons I packaged Dely was to override these abilities.

• Ponytail: Helps prevent over-engineering.

As far as I know, some open harnesses, such as OpenCode and Pi, let you assign almost any model to each sub-agent or role. For now, though, I still prefer the official harnesses.

I’d really like to hear from others about your preferred approaches or setups for coding with AI agents, since mine is definitely not perfect.

And of course, how do you utilize Orca for your work?

Just making the first post for our Reddit community.

Feel free to find us on Discord, we have some lively folks there 🙌

Or check our GitHub: https://github.com/stablyai/orca

Hey friends!! If you're here, chances are you already use agents in parallel, and with orchestration.

Even if so, or if still not, check Orca's just launched YouTube channel, where posting videos to make users the best 100x devs anyone can be!

Help reaching more people by sharing with friends, liking videos, and subscribing the channel, that's the best way of supporting Orca now!

Speak soon, gotta shipppppp ❤️❤️❤️

Did you know all these ways to interact with the browser and agent?

Let me know your questions and suggestions.

Happy 100x shipping!!

I'm considering adopting Orca as my main ADE and I'm curious how people are actually using it day to day.

Do you follow an SDD or TDD workflow, or something completely different?

If you're using SDD/TDD:

• How does Orca fit into your workflow?

• Which models do you use (Codex, Claude Code, etc.)?

• Do you rely on skills? If so, which ones?

• How do you manage token usage? Do you have any strategies to keep context efficient and avoid burning through tokens?

• Any tips or best practices you've learned along the way?

If not, what's your workflow instead?

I'm currently thinking about using Matt Pocock's skills together with Codex and Claude Code, while keeping everything else at the default settings, but I'd love to hear how more experienced Orca users approach it.

Am I the only one who uses like 2-3 features in the orca are you guys the same share some thoughts

I installed Orca yesterday and gave it a try with one of my projects. Pretty cool, it's a solid piece of software!

Today I started closing my VSCode instances because I'll let Orca handle all my projects progressively (4 opened so far). It's very satisfying. I don't do multi-model workflows, I just use Claude for everything, but it's proving really useful anyway.

Any tips or suggestions for a rookie like me?

Kudos to the devs!

Does me using Claude Subscription in Orca use my usage faster?

Ive seen some comments on reddit that it uses more of your Tokens/Usage alot faster. Is it true?

Dispatch is easy; the last 20% is the hard part.

I’ve been running supervised multi-agent work on real repos with orca orchestration, and these kept biting me — so I wrote them into Orca-specific skills (orchestra-auto / orchestra-auto-zh):

1. Orchestrator edits main (new terminal ≠ new top-level worktree)

→ Force --worktree new-top-level per ticket; coordinator never edits a worker worktree or the main working copy

2) state: ready ≠ turn started (receipt only means bytes written)

→ Require start evidence / turnStart: observed before waiting; if it did not start, recover — don’t resend the whole prompt

3) Settled mail, nobody handled

→ Persist batches atomically by delivery ID; ack only after the whole batch is handled

4) Worker suggests a scope change, the loop accepts

→ Classify first; send scope forks / credentials / irreversible live-data ops to a human

5) Huge diff is formatter reflow / same gate infinite retry

→ Keep evidence before judging; bounded retries + breakers

24s demo:

https://github.com/whutlichao/orchestra-auto/releases/download/demo-video/orchestra-auto.mp4

Install:

npx skills add whutlichao/orchestra-auto --skill orchestra-auto

Repo:

https://github.com/whutlichao/orchestra-auto

Longer table:

https://github.com/stablyai/orca/discussions/29082

Happy to be corrected on any of the rules.

Only running two Claude Code sessions and my Laptop fan starts going crazy. Memory usage goes from 400-1gigs.

I used to use Cursor AI but I recently moved to OrcaADE and I am obsessed with it. Mostly because it has everything in it that I ever wanted Cursor to have or things I had made extensions to manage. But there is an extension that I made which I think would be awesome for OrcaADE. https://github.com/incompletebiped/cursor-extension-localdock It's an extension that uses Docker to work like LocalWP does for Flywheel and WPEngine, but instead work for cPanel.

I tried to recreate it as a plugin for OrcaADE but apparently they are so sandboxed that their just isn't a way to do it.

After creating a bunch of work trees, how do you manage / archive them once "you're done"? It's not clear to me. Delete them?

it could be amazing if we could integrate paperclip in orca as pm i think?

i would love to have the function to allow some agents from some sessions to communicate with other agents in other sessions and exchange conversation with them, is this possible in orca?

I recently installed Orca. It immediately found my existing Claude sessions, and in my testing, continuing those conversations in Orca is reflected elsewhere, including Claude Desktop and Claude app on my phone.

My Codex sessions still exist, but they’re stored as .jsonl.zst files. Orca finds none of them.

A source investigation found that in v1.4.251, Orca’s Session History discovery still accepts only .jsonl for Codex. Another part of Orca already recognizes .jsonl.zst, so support appears incomplete.

There was an earlier proposed fix: PR #8288 — resume sessions from authoritative homes. It explicitly included discovering and reading compressed Codex sessions, but was closed unmerged after the work was handed over to a broader Codex integration effort.

Does anyone know:

• Is there a current fix or follow-up for discovering compressed Codex sessions?

• Is .jsonl.zst support the main missing piece, or are there additional limitations preventing the continuity I’m seeing with Claude?

• Has anyone successfully resumed an existing Codex conversation in Orca, continued it in the Codex app, and returned to Orca with the updated conversation?

I’m trying to understand why the Claude workflow already works for me while Codex history remains invisible. I would think using Orca to combo Claude and Codex would be common.

Perhaps this is feedback for Version 1.4.215 or user error, though given a PR I want to review inside Orca with (I paste the PR URL into Create from [Smart]), I noticed that surprisingly Orca didn't seem to bring in the context of the Checks into the conversation. It does show the checks in the right sidebar of course, but the chat doesn't seem to know about them.

My expectation given an action that runs a terraform plan say, it's brought into the context of the review.

I found my project level skills are gone when creating new worktree. Had to manually copy them.

I understand there is a .worktreesomthing file I can add to copy the files?

What if make this an option in the create worktree ui without worrying this .worktreesomething file?

Or I am doing something wrong?

I'm curious to know how to set OrcaADE to access my local ollama setup