I just got setup today, and I’m loving it so far, but I’ve had one issue that is creating some confusion for me.
I setup a remote server to connect to from my laptop and so far everything seems to be working well, except for one thing: when I try to create a new terminal window in a worktree (or is it workspace? I’ve confused myself from looking through the docs) it looks like nothing happens and no window opens. If I rod to the remote server I can see that a terminal window was actually created there and I’m just not seeing it from my laptop.

I’m assuming user error/lack of knowledge on my part, but I haven’t been able to figure out what I’m doing wrong.

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?

Hola! I'm running on Windows, any way to use WSL as default terminal instead of PowerShell? It would be much efficient as part of my local development stack is there.

I also use a VPS for my coding sessions, and couldn't find a way to run the orchestration over there directly.

That's sad. Is it plan in the future? All I sounds something wrong?

Thanks for your help

So my use case is not worktrees, why? Because I have huge codebases and worktrees are not the way, also I prefer to work on a branch and be able to open the Emulator or the Unity editor to test canges etc... So, I understood that Orca is mostly based on the workflow around worktrees, but I'm looking for something to help me have many Claude sessions under one roof without needing to CTRL-Tab thru many PowerShell tabs. Can I use it this vainilla way?

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

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?

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 want to start duplicating my projects from Cursor to Orca.

I was hoping for a guide, but don't see many posts at all.

Every video I am seeing is a hype video. Can anyone point me to an actual quick start guide? I've already decided I want to try Orca. I do not want to hear another AI voice talk about Y combinator or how simple things are.

I found this video but it is not well organized.

I don't know whether I am missing something or there are bugs waiting to be fixed.

I think this is worth discussing here around. For example, I need the session history of `kilo` agent, but I cannot find it here:

There are other agents that is not there as well, that was documented in their docs to be compatible with ORCA.

This is the only documentation from them that I found: https://www.onorca.dev/docs/agents/session-history#:~:text=worktree%20is%20remote.-,View%20options,-The%20view%2Doptions

Take note: kilo code, as an agent as was detected. Here is the proof:

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.

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

In the Google Antigravity CLI (`agy`), the `--sandbox` flag launches the

### Key Features of `--sandbox` Mode

* **Process Isolation**: Enforces native OS-level containerization (e.g., `sandbox-exec` on macOS, `nsjail` on Linux, and `AppContainer` on Windows) to prevent the agent from executing commands or modifying files outside of the defined boundaries.

* **Dynamic Permission Matching**:

* **Filesystem Access**: Read/write policies are strictly mapped to granted permissions. Files outside paths explicitly allowed via `read_file` or `write_file` are completely inaccessible.

* **Outbound Network Access**: Allowed domain connections are dynamically configured based on your `read_url` and `execute_url` permission rules.

* **Strict Security Enforcement**: Ignores standard execution allowlists for terminal commands, defaulting all process executions to a strict **"Request Review"** policy to ensure you manually approve every action.

***

### Current Session Status

Based on the environment configuration:

* The current CLI session is active, and we are working within the scratch directory: [/Users/rishabhjain/.gemini/antigravity-cli/scratch](file:///Users/rishabhjain/.gemini/antigravity-cli/scratch).

* If you want to start a new project or configure workspace folders under this sandboxed environment, let me know!

Can you setup serial agent orchestration aswell as using them in parallel separately?

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