clawdis
Skills for the OpenClaw personal AI assistant, covering browser automation, routing requests to coding agents, presenting canvas widgets, running apps on temporary machines, and sharing diffs.
78 skills393k
@steipeteAgent Orchestration
Plugin
agent-orchestrator
Plans, delegates, and supervises teams of coding agents from planning through merge, with worker sessions, a kanban board, branch worktrees, and pull request tracking. Includes skills to launch the AO desktop app and to triage bug reports.
Plugin Signal86/100Strong
maintained100
capable71
documented80
adopted88
Claude Code
$ npx -y skills add OrchestratorInc/agent-orchestrator --agent claude-code
Codex
$ npx skills add OrchestratorInc/agent-orchestrator -a codex
Cursor
$ npx skills add OrchestratorInc/agent-orchestrator -a cursor
Gemini CLI
$ npx skills add OrchestratorInc/agent-orchestrator -a gemini-cli
GitHub Copilot
$ npx skills add OrchestratorInc/agent-orchestrator -a github-copilot
OpenCode
$ npx skills add OrchestratorInc/agent-orchestrator -a opencode
Windsurf
$ npx skills add OrchestratorInc/agent-orchestrator -a windsurf
What's inside
9 Skills
/ao-desktop-devLaunch, restart, or troubleshoot the real AO Electron desktop app from this repository; run a checkout against isolated or real local AO data; combine PR branches for local UI review; and diagnose stale Electron processes, port conflicts, or preload bridge mismatches. Use/bug-triageHelp clarify human bug reports, search for duplicates, and gather diagnostic evidence separately from a concise issue draft./ao-actionsDirect actions on one Orchestrator session or PR: stop or interrupt, resume, merge a PR, start a review, screenshot a session's browser, send a session's files, keep a host awake, and recurring Orchestrator automations. Use for "stop <session>", "merge <PR>", "review <session>'s
20 Commands
/automationManage durable recurring session automations through the daemon API./browser-remoteUse `ao browser` to control the configured remote Chromium browser shown in Orchestrator's Browser panel. The browser service and app must already be running; open the app's actual runtime URL with `ao browser open`./browserInspect and control the current Orchestrator-managed session's target-isolated browser. The desktop app must be open. The agent and user share the same live page, cookies, navigation state, and `WebContentsView`; the runtime remains usable while the Browser panel is hidden,
README
Orchestrator.inc
Run a fleet of coding agents while keeping branches, reviews, and CI failures manageable.
Get Orchestrator.inc • Documentation • Releases • Contributing • Discord
English · 简体中文 · 日本語 · 한국어 · Español · Français · Deutsch · Português (Brasil)
Why Orchestrator.inc
One coding agent can handle a task. Running several means splitting the work, keeping branches from colliding, and following every change through CI, review, and merge. Orchestrator.inc is a local desktop workspace for that: every task gets its own agent, branch, and worktree, and your code stays on your machine.
Features
The orchestrator runs the fleet
Tell a project's main agent what you want built. It plans the work, starts a worker for each piece in its own worktree, and comes back only when something needs you.
One board for every session
Sessions sort themselves into lanes from the agent, its PR, CI, and reviews, so whatever needs you is on top.
CI fails, the right agent fixes it
Failed checks, review comments, and merge conflicts go back to the worker that owns the branch until the PR is approved. A reviewer agent can read every PR before a person does.
Use the agent you already trust
Pick the agent and model per task, then work in structured chat or the agent's own terminal UI. Each worker also gets a browser to preview and test its app.
Supported agents
Worker, Chat, and reviewer support differ by agent; the agent setup guides have the current matrix.
Stars on GitHub
Momentum
- stars in total
- 14.4k
File tree
Similar plugins.
See 12 agent-orchestrator alternatives
@steipeteorca
Gives Claude Code users skills to drive Orca-managed worktrees, terminals and the embedded browser through the orca CLI, plus Jira and Linear ticket work and inline HTML chat visuals. Covers chart, table and mockup output.
11 skills1 MCP111k
@stablyaipaperclip
Orchestrates teams of AI agents to run work like a company, with a Node.js server and React UI. Adds skills for delegating tasks, following up on results, reviewing team status, and managing Paperclip tasks from Hermes.
22 skills4 agents1 MCP+2+1+1109k
@paperclipailobehub
Organizes your AI agents for round-the-clock operation, with tools to hire, schedule and report on your agent team. Lets you oversee the agents without staying online yourself.
84k
@lobehubQuestions about agent-orchestrator.
Install it with the command on its page. It includes ao-desktop-dev, bug-triage, ao-actions. Its skills do not fire on their own yet. Free and open source.
- What is agent-orchestrator?
- orchestratorinc/agent-orchestrator is a plugin for running and supervising teams of coding agents from planning through to merge, across any harness. It ships skills and commands, including ao-desktop-dev for working with the AO desktop app and bug-triage for clarifying bug reports.
- How do I install agent-orchestrator?
- Run these in Claude Code: npx -y skills add OrchestratorInc/agent-orchestrator --agent claude-code. Then prompt normally.
- Does agent-orchestrator auto-invoke its skills?
- Not yet. It is indexed on Flowy as a plain plugin.
- Is agent-orchestrator free?
- Yes. Flowy is free and open source, with nothing gated. You can read every skill in full before you install.
- Which coding agents can use agent-orchestrator's skills?
- agent-orchestrator installs in Claude Code, and its skills also install in Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI. Each skill's page has the install command. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.
Is this plugin yours?
Claim it with GitHubSubmit a pluginPromote it