這些公司的工程師都在用
編排代理
每個專案都有一個主代理。告訴它你想做出什麼，它就會規劃工作，為每個部分在獨立的 worktree 中啟動一個工作代理，只有需要你時才會回來找你。
看板
工作階段會依即時事實自動歸位：代理正在做什麼、它的 Pull Request、CI 與審查。你只要開啟需要你處理的，其他的不用管。
泳道由代理、它的 PR、CI 與審查決定，而不是靠某個人記得去更新狀態。
任務、代理、分支與 Pull Request 集中在一起。開啟即可查看聊天、終端機、變更的檔案與預覽。
問題、失敗的檢查與修改要求都集中在同一條泳道，不會有事情在你看不到的地方等你。
回饋循環
Orchestrator 會盯著它開出的每個 Pull Request。失敗的檢查、審查意見與合併衝突，都會連同修正所需的資訊一起送給負責該分支的工作代理，直到 PR 獲得核准。
失敗的檢查、檢查名稱與記錄連結，會直接送給負責該分支的代理。
來自真人與審查代理的意見，會依討論串逐一回到同一個工作階段。
讓審查代理在真人之前先看過每個 PR，一鍵就能把發現的問題送回去。
代理
為每個任務挑選代理與模型。在結構化聊天中協作，或開啟它的原生終端機介面。不論哪種方式，任務、分支與回饋都會保持關聯。
計畫、指令與檔案編輯都在一條清楚易讀的時間軸上，需要核准的地方就地核准。
在同一個 worktree 中開啟代理自帶的 TUI，或讓工作階段在聊天與終端機之間切換。
每個工作代理都有自己的瀏覽器可預覽應用程式，代理還能親自點選操作，檢查自己的成果。
行動版
透過你的網路或 Tailscale 將行動 App 與桌面版配對。代理需要你時會收到通知，你可以在聊天中回覆，或開啟它的終端機。
代理提問、Pull Request 就緒或檢查失敗時，都會通知你。
不必打開筆電，就能在聊天中回覆、核准計畫或開始新任務。
代理與程式碼都留在你的電腦上。手機透過 LAN 或 Tailscale 直接連線到它。
本機版免費開源。價格只適用於雲端。
在你自己的電腦上執行代理。開源，不需帳號。
$0/月
方案內容
適合個人開發者：闔上筆電後，代理仍會繼續工作。
$20/月
同時執行 2 個8 個工作階段
方案內容
適合更大的代理叢集，分散在你所有的電腦上。
$40/月
同時執行 10 個25 個工作階段
方案內容
適合需要規模、管控與支援的團隊。
客製
同時執行 25+ 個100+ 個工作階段
方案內容
來自 Orchestrator 使用者的真實回饋。
Our in house software factory, built on top of original @useOrchestrator has been delivering impressive results. Built on our code and architecture context, it helped us innovate 50x faster while increasing the quality bar substantially.
Orchestrator.inc helped me in removing the friction of using multiple harnesses at the same time. I can just work in peace without ever worrying about running grok, omp, or opencode CLI separately. I get the best of all worlds!
experimented with @useOrchestrator alongside my daily driver @orca_build this morning - Orchestrator - best for big ideas that need splitting into multiple PRs without having to babysit each one - Orca - best for tasks that need more oversight and frontend UI work going to keep testing this setup out but I like how Orchestrator eliminated the need for manually tracking individual tasks that stemmed from a big feature set across sessions It automatically did the orchestration work I had manually been doing in Orca. Well done devs
There hasn’t been a day in the last two months when I opened another IDE or ran a coding agent in a terminal app. Orchestrator.inc really changes how you think about work. It’s a mindset shift you can’t go back from.
“Of every tool I tested, Orchestrator.inc is the one that pushes hardest past session management into autonomous PR handling. Agents fix CI failures, respond to review comments, and manage their own PR lifecycle without asking me to approve each edit.”
Our in house software factory, built on top of original @useOrchestrator has been delivering impressive results. Built on our code and architecture context, it helped us innovate 50x faster while increasing the quality bar substantially.
Orchestrator.inc helped me in removing the friction of using multiple harnesses at the same time. I can just work in peace without ever worrying about running grok, omp, or opencode CLI separately. I get the best of all worlds!
experimented with @useOrchestrator alongside my daily driver @orca_build this morning - Orchestrator - best for big ideas that need splitting into multiple PRs without having to babysit each one - Orca - best for tasks that need more oversight and frontend UI work going to keep testing this setup out but I like how Orchestrator eliminated the need for manually tracking individual tasks that stemmed from a big feature set across sessions It automatically did the orchestration work I had manually been doing in Orca. Well done devs
There hasn’t been a day in the last two months when I opened another IDE or ran a coding agent in a terminal app. Orchestrator.inc really changes how you think about work. It’s a mindset shift you can’t go back from.
“Of every tool I tested, Orchestrator.inc is the one that pushes hardest past session management into autonomous PR handling. Agents fix CI failures, respond to review comments, and manage their own PR lifecycle without asking me to approve each edit.”
Our in house software factory, built on top of original @useOrchestrator has been delivering impressive results. Built on our code and architecture context, it helped us innovate 50x faster while increasing the quality bar substantially.
Orchestrator.inc helped me in removing the friction of using multiple harnesses at the same time. I can just work in peace without ever worrying about running grok, omp, or opencode CLI separately. I get the best of all worlds!
experimented with @useOrchestrator alongside my daily driver @orca_build this morning - Orchestrator - best for big ideas that need splitting into multiple PRs without having to babysit each one - Orca - best for tasks that need more oversight and frontend UI work going to keep testing this setup out but I like how Orchestrator eliminated the need for manually tracking individual tasks that stemmed from a big feature set across sessions It automatically did the orchestration work I had manually been doing in Orca. Well done devs
There hasn’t been a day in the last two months when I opened another IDE or ran a coding agent in a terminal app. Orchestrator.inc really changes how you think about work. It’s a mindset shift you can’t go back from.
“Of every tool I tested, Orchestrator.inc is the one that pushes hardest past session management into autonomous PR handling. Agents fix CI failures, respond to review comments, and manage their own PR lifecycle without asking me to approve each edit.”
Our in house software factory, built on top of original @useOrchestrator has been delivering impressive results. Built on our code and architecture context, it helped us innovate 50x faster while increasing the quality bar substantially.
Orchestrator.inc helped me in removing the friction of using multiple harnesses at the same time. I can just work in peace without ever worrying about running grok, omp, or opencode CLI separately. I get the best of all worlds!
experimented with @useOrchestrator alongside my daily driver @orca_build this morning - Orchestrator - best for big ideas that need splitting into multiple PRs without having to babysit each one - Orca - best for tasks that need more oversight and frontend UI work going to keep testing this setup out but I like how Orchestrator eliminated the need for manually tracking individual tasks that stemmed from a big feature set across sessions It automatically did the orchestration work I had manually been doing in Orca. Well done devs
There hasn’t been a day in the last two months when I opened another IDE or ran a coding agent in a terminal app. Orchestrator.inc really changes how you think about work. It’s a mindset shift you can’t go back from.
“Of every tool I tested, Orchestrator.inc is the one that pushes hardest past session management into autonomous PR handling. Agents fix CI failures, respond to review comments, and manage their own PR lifecycle without asking me to approve each edit.”
Orchestrator.inc really changes the way you develop. The orchestrator and kanban have been a game changer. I’m no longer confused about what agent is doing what; scoping tasks and spawning them off has been a breeze.
our dev team is using it @themoeapp - amazing tool
Today I shipped 5 features for Renzaflow. While playing a game using @useOrchestrator Not "vibe coding." Planned, agentic development. Here's how it worked: I planned the work and defined the outcomes. Then I handed it off to Orchestrator.inc, my agent orchestrator. Orchestrator.inc broke the work into tasks, spawned workers, handled code review feedback, resolved merge conflicts, fixed CI failures, and carried each feature through to completion. I never touched a single PR. The shift isn't "let AI write your code." It's this: Don't babysit agents. Orchestrate them. You stay responsible for direction, priorities, and quality — the things that actually require judgment. Your agents handle execution, end to end — the things that don't. That's the unlock. Not faster typing. A different job entirely.
we used Orchestrator.inc (@useOrchestrator) to red team the learning loop, and (@TensorMux) + GLM-4.7-Flash for policy induction. the result: 27 → 8 human reviews after learning 29/29 tests passed E1–E8 passed 0 incorrect autonomous applications demo ↓ youtu.be/b12UIm7X8iM?is…
Orchestrator.inc really changes the way you develop. The orchestrator and kanban have been a game changer. I’m no longer confused about what agent is doing what; scoping tasks and spawning them off has been a breeze.
our dev team is using it @themoeapp - amazing tool
Today I shipped 5 features for Renzaflow. While playing a game using @useOrchestrator Not "vibe coding." Planned, agentic development. Here's how it worked: I planned the work and defined the outcomes. Then I handed it off to Orchestrator.inc, my agent orchestrator. Orchestrator.inc broke the work into tasks, spawned workers, handled code review feedback, resolved merge conflicts, fixed CI failures, and carried each feature through to completion. I never touched a single PR. The shift isn't "let AI write your code." It's this: Don't babysit agents. Orchestrate them. You stay responsible for direction, priorities, and quality — the things that actually require judgment. Your agents handle execution, end to end — the things that don't. That's the unlock. Not faster typing. A different job entirely.
we used Orchestrator.inc (@useOrchestrator) to red team the learning loop, and (@TensorMux) + GLM-4.7-Flash for policy induction. the result: 27 → 8 human reviews after learning 29/29 tests passed E1–E8 passed 0 incorrect autonomous applications demo ↓ youtu.be/b12UIm7X8iM?is…
Orchestrator.inc really changes the way you develop. The orchestrator and kanban have been a game changer. I’m no longer confused about what agent is doing what; scoping tasks and spawning them off has been a breeze.
our dev team is using it @themoeapp - amazing tool
Today I shipped 5 features for Renzaflow. While playing a game using @useOrchestrator Not "vibe coding." Planned, agentic development. Here's how it worked: I planned the work and defined the outcomes. Then I handed it off to Orchestrator.inc, my agent orchestrator. Orchestrator.inc broke the work into tasks, spawned workers, handled code review feedback, resolved merge conflicts, fixed CI failures, and carried each feature through to completion. I never touched a single PR. The shift isn't "let AI write your code." It's this: Don't babysit agents. Orchestrate them. You stay responsible for direction, priorities, and quality — the things that actually require judgment. Your agents handle execution, end to end — the things that don't. That's the unlock. Not faster typing. A different job entirely.
we used Orchestrator.inc (@useOrchestrator) to red team the learning loop, and (@TensorMux) + GLM-4.7-Flash for policy induction. the result: 27 → 8 human reviews after learning 29/29 tests passed E1–E8 passed 0 incorrect autonomous applications demo ↓ youtu.be/b12UIm7X8iM?is…
Orchestrator.inc really changes the way you develop. The orchestrator and kanban have been a game changer. I’m no longer confused about what agent is doing what; scoping tasks and spawning them off has been a breeze.
our dev team is using it @themoeapp - amazing tool
Today I shipped 5 features for Renzaflow. While playing a game using @useOrchestrator Not "vibe coding." Planned, agentic development. Here's how it worked: I planned the work and defined the outcomes. Then I handed it off to Orchestrator.inc, my agent orchestrator. Orchestrator.inc broke the work into tasks, spawned workers, handled code review feedback, resolved merge conflicts, fixed CI failures, and carried each feature through to completion. I never touched a single PR. The shift isn't "let AI write your code." It's this: Don't babysit agents. Orchestrate them. You stay responsible for direction, priorities, and quality — the things that actually require judgment. Your agents handle execution, end to end — the things that don't. That's the unlock. Not faster typing. A different job entirely.
we used Orchestrator.inc (@useOrchestrator) to red team the learning loop, and (@TensorMux) + GLM-4.7-Flash for policy induction. the result: 27 → 8 human reviews after learning 29/29 tests passed E1–E8 passed 0 incorrect autonomous applications demo ↓ youtu.be/b12UIm7X8iM?is…
Orchestrator 本來就是設計來搭配你現有的工具。我們原生支援以深層連結開啟 Cursor 等 IDE，讓你直接在 IDE 中開啟工作區與檔案。Orchestrator 位在各個工具之上：想用哪個代理都可以，工作流程始終一致。
Orchestrator 支援 38 款程式代理，包括 Claude Code、OpenAI Codex、Cursor、OpenCode、Aider、Goose、GitHub Copilot 與 Gemini CLI，並可依專案選擇代理。每個專案都能各自指定工作代理、編排代理與審查代理。
編排代理負責規劃工作並啟動工作代理，每個工作代理都在各自獨立的 Git worktree 中執行，因此能同時處理不同的分支或功能，彼此不會衝突。Orchestrator 會盯著它們開出的每個 Pull Request：CI 失敗、審查意見與合併衝突，都會轉回給負責該分支的代理。內建的 AO 審查代理可以審查 PR，並把要求修改的內容送回同一個工作代理，而你只要看一個看板就能掌握整個代理叢集。
是的。Orchestrator.inc 是 Agent Orchestrator（AO）的新名稱。它仍是同一款開源應用程式和同一個 ao CLI，原始碼位於 https://github.com/OrchestratorInc/agent-orchestrator。
是的。本機應用程式以 Apache-2.0 授權免費開源，可在任何支援的執行框架上執行不限數量的本機代理，並包含編排代理、工作代理與 PR 審查。代理在你電腦上的 Git worktree 中工作，Orchestrator 不會轉發你的 API 呼叫，在本機執行代理也不需要帳號或信用卡。你的手機或其他電腦可以在同一個網路下連線，也能透過選用的託管 HTTPS 通道從任何地方連線；Tailscale 無法在 iPhone 或 iPad 上使用，在 Android 上也尚未驗證，目前也還沒有內建的裝置中繼。付費的 Cloud 方案每月 $20 起，提供雲端專案，以及在託管沙箱中執行的雲端代理。
可以。Orchestrator Cloud 現已推出：在桌面版登入 Orchestrator Cloud，選擇「Clone to the cloud」來挑選一個 GitHub 儲存庫，即可在託管沙箱中執行工作代理與編排代理的工作階段。在桌面版上，你可以使用聊天、遠端終端機、檔案檢視器，以及該工作階段的 Pull Request 與審查。雲端代理包含在 Starter、Pro 與 Enterprise 方案中。本機專案不需要 Cloud 也能照常運作。
可以。在本機專案中，Orchestrator 會直接執行你電腦上已安裝的程式代理 CLI，沿用它們現有的登入狀態，不論是 API 金鑰還是供應商訂閱。它不會轉發 API 呼叫，因此用量由各供應商分別計費，成本完全由你掌控。
還有疑問？
閱讀文件，查看詳細的使用指南。
