ai-orchestrators.md

AI Orchestrators Decision Table

An attempt to find a good agent orchestrator or two, that can support these styles of software AI dev:

1. Mostly AI assisted coding (currently leading: conductor)
2. Mostly vibe coding (currently exploring configuring pi from scratch)

Ideally one tool could be used for both.

Leave any suggestions in the comments please, all are welcome.

Feature	conductor	emdash	superset	agor	Maestro	opencode	JAT	pi
Worktrees	✅	✅	✅	✅	❌	✅	❌	❌
Task overview	✅	✅	✅	✅	✅	✅	✅	❌
Line comments	✅	❌	❌	❌	❌	✅	❌	❌
Github PRs	✅	✅	❌	❌	✅	❌	❌	❌
Claude TOS	✅	✅	✅	✅	✅	❌	✅	❌
opencode	❌	✅	✅	✅	✅	✅	✅	❌
Multi-agent workflows	❌	❌	❌	✅	✅	✅	✅	❌
Multi-agent conversations	❌	❌	❌	❌	✅	❌	❌	❌
Shared config	❌	❌	❌	❌	❌	✅	❌	✅

Legend

• Worktrees - Support for worktrees per task, with setup/teardown scripts
• Task overview - Ability to see all tasks from all projects in one place
• Line comments - Convenient UX for leaving code review line comments locally
• Github PRs - Convenient UX for creating and reviewing Github PRs
• Claude TOS - Ability to use Claude subscription while adhering to Anthropic TOS
• OpenCode - Ability to tap into existing opencode setup, run opencode models / agents / skills
• Multi-agent workflows - Automate multiple proprietary and open CLIs into workflows
• Multi-agent conversations - UI for talking to multiple agents at once
• Shared config - Ability to reuse agents and skills across different CLIs (e.g. Claude Code, Codex, opencode), when running them inside the orchestrator

For "Shared Config" is the requirement there that skills can be shared between different providers (Codex vs Claude) or that the tooling is available the same whether you're using the orchestrator or switching back to the standard CLI/TUI?

@pedramamini

TL;DR — I think the former of the 2.

In opencode, you create skills and agents in opencode config itself. Then, any model from any provider you run in opencode can tap into these common skills, and act as those agents for you. It would be great to have the same idea work in a TOS-compatible orchestrator. Common config owned by the orchestrator, that any CLI you run inside it (Claude, Codex, etc) can tap into. In my mind, I think if you run Claude/Codex standalone, outside of the orchestrator, then it doesn't have to be able to see those configs. Could be an option perhaps.

Interesting. I do have support for custom AI commands, you define them from settings. They are slash commands, basically macros, supporting template variables and work across any provider, but it's not quite what you're asking for.

Updated the gist to:

1. Add JAT
2. Clarify "Shared config" item

Added pi-coding-agent. Unironically considering it as the base for setup. It's what powers openclaw in case anyone's wondering.