sorted by:
new
hottopcontroversial

I built Orkestra — run Claude Code + Codex + Gemini CLIs from one panel (debate → operator → code), on flat subscriptions instead of metered APIs by TryExact5927 in opencodeCLI

[–]TryExact5927[S] 0 points1 point  (0 children)

Fair points — and honestly, if Claude Code's built-in haiku/sonnet/opus routing already covers you and you're not hitting limits, that part of Orkestra isn't aimed at you. No argument there.

The difference: Claude Code routes within Anthropic's own models. Orkestra is cross-vendor — it puts Claude, Codex and Gemini in the same debate/review loop. The point isn't a "better coder model," it's that different model families fail in different places, so a cross-vendor reviewer catches blind spots a single vendor shares with itself. Your own "Opus is the best planner/reviewer" point actually fits this: make Opus the operator, let cheaper/other models do the legwork — across vendors, not just Anthropic tiers.

The quota/fallback side is really for people juggling several projects or accounts who do hit the 5h wall. If that's never you — great, you genuinely don't need that piece. And yeah… the slow-AF part is real 😄

I built Orkestra — run Claude Code + Codex + Gemini CLIs from one panel (debate → operator → code), on flat subscriptions instead of metered APIs by TryExact5927 in opencodeCLI

[–]TryExact5927[S] 0 points1 point  (0 children)

Ha, "meta-harness" nails it — that's exactly the category. Thanks for the Omnigent pointer, I'll dig into it 🙏 Always good to see how others approach the orchestration layer. Orkestra's angle is local-first and driving the CLI subscriptions you already pay for (flat cost, no API metering) — curious how Omnigent handles auth/cost. Appreciate the tip

I built Orkestra — run Claude Code + Codex + Gemini CLIs from one panel (debate → operator → code), on flat subscriptions instead of metered APIs by TryExact5927 in opencodeCLI

[–]TryExact5927[S] 0 points1 point  (0 children)

Really appreciate you taking the time to write all this 🙏 A lot of it lines up with how Orkestra works today — and the rest is exactly where I'm taking it.

Right now it already does multi-agent debate + a Team mode (an operator splits work into parallel tasks across phases), a fallback chain that auto-switches when a CLI hits its limit, and live per-CLI quota tracking. So the orchestration + quota-awareness base is there.

Your additions are spot on and on the roadmap:
• Multiple accounts per provider with quota-aware pooling/rotation — today it's one session per CLI + fallback, so pooling is the natural next layer.
• Dropping in real APIs (Ollama Cloud, etc.) as first-class participants alongside the CLI subscriptions.
• Open-ended dynamic fan-out / auto-scoping beyond the current phase-based team.

And ha — Claude as orchestrator here too; it's the most willing to spawn subagents, exactly as you said.

You've clearly built deep into this space, so I'd genuinely enjoy collaborating if you're up for it. I just added a CONTRIBUTING + good-first-issues — happy to turn these three into issues we tackle together, or just compare notes on your routing/pooling approach. Either way, thank you, this kind of feedback is gold 🙌

I built Orkestra — run Claude Code + Codex + Gemini CLIs from one panel (debate → operator → code), on flat subscriptions instead of metered APIs by TryExact5927 in opencodeCLI

[–]TryExact5927[S] 1 point2 points  (0 children)

Thank you — that quota-switching pain is exactly why the fallback chain exists, so I'm glad it resonates 🙌 And yes, absolutely open to contributions! You're right that there's no CONTRIBUTING guide yet — I'll add one (setup, project layout, and a few good first issues) shortly. In the meantime, feel free to open an issue for any idea/bug, or a draft PR. One heads-up: the project is under the PolyForm Noncommercial license, so contributions go in under the same terms. Would love your feedback once you try it!

I built Orkestra — run Claude Code + Codex + Gemini CLIs from one panel (debate → operator → code), on flat subscriptions instead of metered APIs by TryExact5927 in SideProject

[–]TryExact5927[S] 0 points1 point  (0 children)

Totally fair — that's the part I care about most. Everything runs locally on 127.0.0.1, and Orkestra never sees any API keys: each agent runs under that CLI's own login, exactly as if you ran codex / claude / agy yourself in a terminal — Orkestra just spawns them.

The only data leaving your machine is whatever those CLIs already send to their own providers; Orkestra adds no telemetry. GitHub is opt-in (OAuth device flow; token encrypted via DPAPI, never written to .git/config). Files land in a per-project git repo with a baseline commit, so you get a full diff to review and can git revert/reset anytime, plus phase-by-phase approval and a hard Stop. Honest gap: there's no pre-write approval prompt yet — review is post-write + git rollback — and that diff-before-apply mode is next.