[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-74772":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":19,"rankGlobal":10,"rankLanguage":10,"license":20,"archived":21,"fork":21,"defaultBranch":22,"hasWiki":23,"hasPages":21,"topics":24,"createdAt":10,"pushedAt":10,"updatedAt":37,"readmeContent":38,"aiSummary":39,"trendingCount":16,"starSnapshotCount":16,"syncStatus":40,"lastSyncTime":41,"discoverSource":42},74772,"agent-orchestrator","ComposioHQ\u002Fagent-orchestrator","ComposioHQ"," Agentic orchestrator for parallel coding agents — plans tasks, spawns agents, and autonomously handles CI    fixes, merge conflicts, and code reviews.","https:\u002F\u002Fcomposio.dev",null,"TypeScript",7427,1014,29,471,0,82,465,40.02,"MIT License",false,"main",true,[25,26,27,28,29,30,31,32,33,34,35,36],"agent-fleet","agent-swarm","claude-code","codex-cli","git-worktrees","multi-agent","orchestration","orchestrator","parallel-agents","parallel-coding","skills","tmux","2026-06-12 02:03:28","\u003Ch1 align=\"center\">Agent Orchestrator — The Orchestration Layer for Parallel AI Agents\u003C\u002Fh1>\n\n\u003Cp align=\"center\">\n\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FComposioHQ\u002Fagent-orchestrator\">\n  \u003Cimg width=\"800\" alt=\"Agent Orchestrator banner\" src=\"docs\u002Fassets\u002Fagent_orchestrator_banner.png\">\n\u003C\u002Fa>\n\u003C\u002Fp>\n\n\u003Cdiv align=\"center\">\n\nSpawn parallel AI coding agents, each in its own git worktree. Agents autonomously fix CI failures, address review comments, and open PRs — you supervise from one dashboard.\n\n[![GitHub stars](https:\u002F\u002Fimg.shields.io\u002Fgithub\u002Fstars\u002FComposioHQ\u002Fagent-orchestrator?style=flat-square)](https:\u002F\u002Fgithub.com\u002FComposioHQ\u002Fagent-orchestrator\u002Fstargazers)\n[![npm version](https:\u002F\u002Fimg.shields.io\u002Fnpm\u002Fv\u002F%40aoagents%2Fao?style=flat-square)](https:\u002F\u002Fwww.npmjs.com\u002Fpackage\u002F@aoagents\u002Fao)\n[![License: MIT](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Flicense-MIT-blue?style=flat-square)](LICENSE)\n[![PRs merged](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FPRs_merged-61-brightgreen?style=flat-square)](https:\u002F\u002Fgithub.com\u002FComposioHQ\u002Fagent-orchestrator\u002Fpulls?q=is%3Amerged)\n[![Tests](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002Ftest_cases-3%2C288-blue?style=flat-square)](https:\u002F\u002Fgithub.com\u002FComposioHQ\u002Fagent-orchestrator\u002Freleases\u002Ftag\u002Fmetrics-v1)\n[![Discord](https:\u002F\u002Fimg.shields.io\u002Fbadge\u002FDiscord-Join%20Community-5865F2?style=flat-square&logo=discord&logoColor=white)](https:\u002F\u002Fdiscord.gg\u002FUZv7JjxbwG)\n\n\u003C\u002Fdiv>\n\n---\n\nAgent Orchestrator manages fleets of AI coding agents working in parallel on your codebase. Each agent gets its own git worktree, its own branch, and its own PR. When CI fails, the agent fixes it. When reviewers leave comments, the agent addresses them. You only get pulled in when human judgment is needed.\n\n**Agent-agnostic** (Claude Code, Codex, Aider) · **Runtime-agnostic** (tmux, ConPTY\u002Fprocess, Docker) · **Tracker-agnostic** (GitHub, Linear)\n\n\u003Cdiv align=\"center\">\n\n## See it in action\n\n\u003Ca href=\"https:\u002F\u002Fx.com\u002Fagent_wrapper\u002Fstatus\u002F2026329204405723180\">\n  \u003Cimg src=\"docs\u002Fassets\u002Fdemo-video-tweet.png\" alt=\"Agent Orchestrator demo — AI agents building their own orchestrator\" width=\"560\">\n\u003C\u002Fa>\n\u003Cbr>\u003Cbr>\n\u003Ca href=\"https:\u002F\u002Fx.com\u002Fagent_wrapper\u002Fstatus\u002F2026329204405723180\">\u003Cimg src=\"docs\u002Fassets\u002Fbtn-watch-demo.png\" alt=\"Watch the Demo on X\" height=\"48\">\u003C\u002Fa>\n\u003Cbr>\u003Cbr>\u003Cbr>\n\u003Ca href=\"https:\u002F\u002Fx.com\u002Fagent_wrapper\u002Fstatus\u002F2025986105485733945\">\n  \u003Cimg src=\"docs\u002Fassets\u002Farticle-tweet.png\" alt=\"The Self-Improving AI System That Built Itself\" width=\"560\">\n\u003C\u002Fa>\n\u003Cbr>\u003Cbr>\n\u003Ca href=\"https:\u002F\u002Fx.com\u002Fagent_wrapper\u002Fstatus\u002F2025986105485733945\">\u003Cimg src=\"docs\u002Fassets\u002Fbtn-read-article.png\" alt=\"Read the Full Article on X\" height=\"48\">\u003C\u002Fa>\n\n\u003C\u002Fdiv>\n\n## Quick Start\n\n> **Prerequisites:** [Node.js 20+](https:\u002F\u002Fnodejs.org), [Git 2.25+](https:\u002F\u002Fgit-scm.com), [`gh` CLI](https:\u002F\u002Fcli.github.com), and:\n> - **macOS \u002F Linux:** [tmux](https:\u002F\u002Fgithub.com\u002Ftmux\u002Ftmux\u002Fwiki\u002FInstalling) — install via `brew install tmux` or `sudo apt install tmux`.\n> - **Windows:** PowerShell 7+ recommended. tmux is **not** required — AO uses native ConPTY via the `runtime-process` plugin (the default on Windows). Set `AO_SHELL=bash` if you have Git Bash and prefer it.\n\n### Install\n\n```bash\nnpm install -g @aoagents\u002Fao\n```\n\n> **Nightly builds** (latest `main`, daily Fri–Tue): `npm install -g @aoagents\u002Fao@nightly`\n> Back to stable: `npm install -g @aoagents\u002Fao@latest`\n\n\u003Cdetails>\n\u003Csummary>Permission denied? Install from source?\u003C\u002Fsummary>\n\nIf `npm install -g` fails with EACCES, prefix with `sudo` or [fix your npm permissions](https:\u002F\u002Fdocs.npmjs.com\u002Fresolving-eacces-permissions-errors-when-installing-packages-globally).\n\nTo install from source (for contributors):\n\n```bash\ngit clone https:\u002F\u002Fgithub.com\u002FComposioHQ\u002Fagent-orchestrator.git\ncd agent-orchestrator && bash scripts\u002Fsetup.sh\n```\n\u003C\u002Fdetails>\n\n### Zsh Completion\n\nGenerate the completion file from the installed CLI:\n\n```bash\nmkdir -p ~\u002F.zsh\u002Fcompletions\nao completion zsh > ~\u002F.zsh\u002Fcompletions\u002F_ao\n```\n\nThen make sure the directory is on your `fpath` before `compinit` runs:\n\n```zsh\nfpath=(~\u002F.zsh\u002Fcompletions $fpath)\nautoload -Uz compinit\ncompinit\n```\n\nFor Oh My Zsh, install the same generated file into a custom plugin directory and add `ao` to your plugin list:\n\n```bash\nmkdir -p \"${ZSH_CUSTOM:-~\u002F.oh-my-zsh\u002Fcustom}\u002Fplugins\u002Fao\"\nao completion zsh > \"${ZSH_CUSTOM:-~\u002F.oh-my-zsh\u002Fcustom}\u002Fplugins\u002Fao\u002F_ao\"\n```\n\nIf you are contributing from a source checkout, you can also symlink the repo copy at [`completions\u002F_ao`](completions\u002F_ao).\n\n### Start\n\nPoint it at any repo — it clones, configures, and launches the dashboard in one command:\n\n```bash\nao start https:\u002F\u002Fgithub.com\u002Fyour-org\u002Fyour-repo\n```\n\nOr from inside an existing local repo:\n\n```bash\ncd ~\u002Fyour-project && ao start\n```\n\nThat's it. The dashboard opens at `http:\u002F\u002Flocalhost:3000` and the orchestrator agent starts managing your project.\n\n### Add more projects\n\n```bash\nao start ~\u002Fpath\u002Fto\u002Fanother-repo\n```\n\n## How It Works\n\n1. **You start** — `ao start` launches the dashboard and an orchestrator agent\n2. **Orchestrator spawns workers** — each issue gets its own agent in an isolated git worktree\n3. **Agents work autonomously** — they read code, write tests, create PRs\n4. **Reactions handle feedback** — CI failures and review comments are automatically routed back to the agent\n5. **You review and merge** — you only get pulled in when human judgment is needed\n\nThe orchestrator agent uses the [AO CLI](docs\u002FCLI.md) internally to manage sessions. You don't need to learn or use the CLI — the dashboard and orchestrator handle everything.\n\n## Configuration\n\n`ao start` auto-generates `agent-orchestrator.yaml` with sensible defaults. You can edit it afterwards to customize behavior:\n\n```yaml\n# agent-orchestrator.yaml\n$schema: https:\u002F\u002Fraw.githubusercontent.com\u002FComposioHQ\u002Fagent-orchestrator\u002Fmain\u002Fschema\u002Fconfig.schema.json\n# Runtime data is auto-derived under ~\u002F.agent-orchestrator\u002F{hash}-{projectId}\u002F\nport: 3000\n\ndefaults:\n  runtime: tmux       # default on macOS \u002F Linux; on Windows the default is `process` (ConPTY)\n  agent: claude-code\n  workspace: worktree\n  notifiers: [desktop]\n\nprojects:\n  my-app:\n    repo: owner\u002Fmy-app\n    path: ~\u002Fmy-app\n    defaultBranch: main\n    sessionPrefix: app\n\nreactions:\n  ci-failed:\n    auto: true\n    action: send-to-agent\n    retries: 2\n  changes-requested:\n    auto: true\n    action: send-to-agent\n    escalateAfter: 30m\n  approved-and-green:\n    auto: false # flip to true for auto-merge\n    action: notify\n```\n\nCI fails → agent gets the logs and fixes it. Reviewer requests changes → agent addresses them. PR approved with green CI → you get a notification to merge.\n\nKeep the `$schema` line so editors can autocomplete and validate against [`schema\u002Fconfig.schema.json`](schema\u002Fconfig.schema.json).\n\nSee [`agent-orchestrator.yaml.example`](agent-orchestrator.yaml.example) for the full reference, or run `ao config-help` for the complete schema.\n\n## Remote Access\n\nAO keeps your Mac awake while running, so you can access the dashboard remotely (e.g., via Tailscale from your phone) without the machine going to sleep.\n\n**How it works:** On macOS, AO automatically holds an idle-sleep prevention assertion using `caffeinate`. When AO exits, the assertion is released.\n\n```yaml\n# agent-orchestrator.yaml\n$schema: https:\u002F\u002Fraw.githubusercontent.com\u002FComposioHQ\u002Fagent-orchestrator\u002Fmain\u002Fschema\u002Fconfig.schema.json\npower:\n  preventIdleSleep: true  # Default on macOS; no-op on Linux and Windows\n```\n\nSet to `false` if you want to allow idle sleep while AO runs.\n\n**Lid-close limitation:** macOS enforces lid-close sleep at the hardware level — no userspace assertion can override it. If you need remote access while traveling with the lid closed, use [clamshell mode](https:\u002F\u002Fsupport.apple.com\u002Fen-us\u002F102505) (external power + display + input device).\n\n**Linux \u002F Windows:** AO does not currently hold a wake assertion on these platforms. On Linux, idle-sleep behaviour is governed by your desktop environment \u002F `systemd-logind`; configure that directly. On Windows, set the OS power plan if remote access matters while idle.\n\n## Plugin Architecture\n\nSeven plugin slots. Lifecycle stays in core.\n\n| Slot      | Default     | Alternatives             |\n| --------- | ----------- | ------------------------ |\n| Runtime   | tmux (macOS\u002FLinux) \u002F process (Windows) | process, docker |\n| Agent     | claude-code | codex, aider, cursor, opencode, kimicode |\n| Workspace | worktree    | clone                    |\n| Tracker   | github      | linear, gitlab           |\n| SCM       | github      | gitlab                   |\n| Notifier  | desktop     | slack, discord, composio, webhook, openclaw |\n| Terminal  | iterm2      | web                      |\n\nAll interfaces defined in [`packages\u002Fcore\u002Fsrc\u002Ftypes.ts`](packages\u002Fcore\u002Fsrc\u002Ftypes.ts). A plugin implements one interface and exports a `PluginModule`. That's it.\n\n## Why Agent Orchestrator?\n\nRunning one AI agent in a terminal is easy. Running 30 across different issues, branches, and PRs is a coordination problem.\n\n**Without orchestration**, you manually: create branches, start agents, check if they're stuck, read CI failures, forward review comments, track which PRs are ready to merge, clean up when done.\n\n**With Agent Orchestrator**, you: `ao start` and walk away. The system handles isolation, feedback routing, and status tracking. You review PRs and make decisions — the rest is automated.\n\n## Documentation\n\n| Doc                                      | What it covers                                               |\n| ---------------------------------------- | ------------------------------------------------------------ |\n| [Setup Guide](SETUP.md)                  | Detailed installation, configuration, and troubleshooting    |\n| [CLI Reference](docs\u002FCLI.md)             | All `ao` commands (mostly used by the orchestrator agent)    |\n| [Examples](examples\u002F)                    | Config templates (GitHub, Linear, multi-project, auto-merge) |\n| [Development Guide](docs\u002FDEVELOPMENT.md) | Architecture, conventions, plugin pattern                    |\n| [Contributing](CONTRIBUTING.md)          | How to contribute, build plugins, PR process                 |\n\n## Development\n\n```bash\npnpm install && pnpm build    # Install and build all packages\npnpm test                      # Run tests (3,288 test cases)\npnpm dev                       # Start web dashboard dev server\n```\n\nSee [docs\u002FDEVELOPMENT.md](docs\u002FDEVELOPMENT.md) for code conventions and architecture details.\n\n## Contributing\n\nContributions welcome. The plugin system makes it straightforward to add support for new agents, runtimes, trackers, and notification channels. Every plugin is an implementation of a TypeScript interface — see [CONTRIBUTING.md](CONTRIBUTING.md) and the [Development Guide](docs\u002FDEVELOPMENT.md) for the pattern.\n\n## License\n\nMIT\n","Agent Orchestrator 是一个用于并行编码代理的编排工具，能够规划任务、启动代理，并自主处理持续集成错误、合并冲突和代码审查。该项目采用 TypeScript 编写，支持多种 AI 代理（如 Claude Code、Codex 等）以及不同的运行时环境（如 tmux、Docker 等），并且可以与 GitHub 等平台无缝集成。每个代理都在自己的 Git 工作树中独立工作，当遇到 CI 失败或需要处理代码审查意见时，代理会自动进行修复或调整。此工具非常适合需要高效管理多个并行开发流程的团队使用，尤其是在大规模软件项目中，能够显著提高开发效率和质量。",2,"2026-06-06 03:51:51","high_star"]