Our take
Activeregular commits and releases- Activity
- 90
- Community
- 93
- Issues
- 75
- Pull requests
- 61
+1,369 stars in the last 30 days
- Releases more often than 93% of the projects we track
- Merges more pull requests than 87% of the projects we track
- More contributors than 77% of the projects we track
An actively maintained, cross-platform agent-supervision workspace with broad harness support, suitable for teams prepared to add another local desktop tool to their development workflow.
Good fit if
- You coordinate multiple coding agents and need task isolation plus a shared view of pull requests, CI, and reviews.
- You want planning and implementation workers in one workflow, while retaining a choice of agent harnesses.
- You can use a desktop application and are comfortable with the project's Apache-2.0 license.
Look elsewhere if
- You need a documented Docker, Compose, or Helm deployment, which the project does not provide.
- You want a lightweight CLI-only tool rather than a desktop workspace with a local daemon.
- You need a project with a small open-issue queue; the repository currently has a substantial number of open issues.
All health signals
| Last commit | 2026-10-18 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 100+ (latest v0.14.3-nightly.202610182020, 2026-10-18, pre-release) |
| Contributors | 100+ (top contributor: 14% of commits) |
| Issues closed, last 90 days | 13+ (typically closed in 1 day) |
| Pull requests merged, last 90 days | 80 (typically merged in 1 day) |
| Project age | 8 months |
Checked on 2026-10-19 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
14,515Forks
1,983Change since Nov 12, 2026: +54 stars·+10 forks
Overview
Orchestrator.inc is a Go-based desktop workspace for planning, running, and supervising teams of coding agents. It addresses the coordination work that comes with parallel development: splitting project goals into focused tasks, isolating worker changes, and following each task through pull requests, CI, review, and merge.
The project supports a broad range of coding-agent harnesses and offers both a persistent project orchestrator for planning and individual workers for implementation. Its desktop app runs a local daemon and is available for macOS, Windows, and Linux. Git-backed workers receive separate branches and worktrees; standalone agents can use managed directories without a repository.
Key Features
- Create worker sessions with a task, selected agent and model, and either structured chat or the agent's native terminal interface.
- Plan project-wide work with a persistent orchestrator that can delegate focused tasks to workers.
- Isolate Git-backed worker changes using individual branches and worktrees.
- Track worker activity, pull requests, CI, reviews, and merge readiness on a live Kanban board.
- Keep conversations, terminals, changed files, browser previews, and review feedback attached to each worker session.
- Return CI failures and requested changes to the agent responsible for the work.
- Use the built-in browser with isolated temporary profiles or deliberately reused named profiles.
Use Cases
- A developer wants several coding agents to work on separate tasks without sharing one branch or conversation context.
- A technical lead needs to turn a larger product goal into delegated tasks and monitor their progress in one place.
- A team using different agent harnesses wants a common workflow for tracking implementation, pull requests, CI, and review.
- A maintainer wants to route review or CI feedback back to the worker that owns a change.
What you need
Detected in the repository
- Node.js (from package.json)
- A test suite and automated checks on GitHub Actions
License in plain words
Apache-2.0permissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the license, the NOTICE file and a note of your changes
- Share your changes: no
- Includes an explicit patent grant from the contributors:
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
Download the desktop app for your platform from the latest releases, then point it at a repository. The app runs the daemon for you. See the README and installation guide for agent setup and platform-specific details.
Alternatives
- orca: Orca focuses on steering coding agents in isolated worktrees, while agent-orchestrator tracks tasks through pull requests, CI, and reviews in a Kanban.
- tessera: Tessera centers on coordinating local coding-agent sessions and Git workflows, rather than tracking tasks through PRs, CI, and reviews.
- codeg: Codeg coordinates agents through the Agent Client Protocol across desktop, server, Docker, and mobile, rather than emphasizing Git worktrees and PR tracking.
- multica: Multica assigns issues to existing agent CLIs and links runs to team review, rather than organizing work around isolated Git branches and worktrees.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| agent-orchestrator | Go | Apache-2.0 | 13.3k | Active |
| orca | TypeScript | MIT | 101k | Active |
| tessera | TypeScript | AGPL-3.0 | 314 | Active |
| codeg | Rust | Apache-2.0 | 4k | Active |
| multica | Go | – | 53.2k | Active |
Considerations
The repository is actively developed, with regular commits and releases, and its measured contributor activity is not concentrated in one person. It has a substantial open-issue queue, so teams should check current issues and release notes when evaluating unresolved needs. The project requires Node.js for development, includes CI and tests, and does not list Docker, Compose, or Helm support. Its Apache-2.0 license is permissive, but adopters should review the license terms for their distribution and use.
Found this useful?
Share it with someone who would like agent-orchestrator.