agency-orchestrator
🚀 One sentence → your one-person company of AI experts → complete deliverable in minutes. 276 CN + 184 EN + 5 more languages (ko/ru/pt-BR/id/ar) · zero-code YAML · auto-verified acceptance · Web Studio / Desktop / Docker · 15 LLM providers (11 key-free). 一句话组建你的「一人公司」AI 专家团队，几分钟交付完整方案；验收自动核验，网页 / 桌面 / Docker 全渠道。
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit bed66133356b
TypeScript, Apache-2.0 licensed. The project labels itself: agency agents, agent orchestration, ai agents, autogen alternative, claude, codex, copilot and crewai alternative.
agency-orchestrator runs, with stand-ins for the services it depends on. An Argusic agent installed it in 5 minutes and hit 4 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Agency Orchestrator 0.19.2 installed and built successfully on Node.js v22, CLI answers version/validate/roles commands, web Studio API serves health/workflows/roles endpoints, and the majority of unit tests pass.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 too old (needs >=20)2 minutes
- website/dist/ missing for web server SPA routing
- local-sdcpp.ts test fails: 2GB RAM insufficient for video model (needs >=24GB)
- Some tsx test files timeout in container (tsx cold start + limited RAM)
- Install time
- 5 minutes
- Cold machine to finish
- 49 minutes
- Errors hit and fixed
- 4 hit, 4 fixed with no human help
- How the result was proved
- npm install && npm run build (tsc) succeeded; node dist/cli.js --version returns 0.19.2; node dist/cli.js validate workflows/en/product-review.yaml passes; web server /api/health returns 200 with version; 60+ individual test files pass with 0 failures
- Model tokens used
- 163,013
- Exact commit tested
- bed66133356b
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
raise JSONDecodeError("Expecting value", s, err.value) from None
json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
The web server startup and curl race condition is due to background process timing. Earlier we veri…
I have all the data I need. The project is working. Here's my final report:
2026-10-03T23:05:19.069921Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-03T23:05:19.070197Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-03T23:05:19.070216Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
2026-10-03T23:05:19.070231Z ERROR codex_core::session: failed to record rollout items: thread 01a10…
tokens used
163,013
The web server startup and curl race condition is due to background process timing. Earlier we veri…
I have all the data I need. The project is working. Here's my final report:Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 5 minutes.
- Recovered from all 4 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.29 |
Topics (from GitHub)
agency-agentsagent-orchestrationai-agentsautogen-alternativeclaudecodexcopilotcrewai-alternativecursordeepseekgemini-clilanggraph-alternativemcp-servermulti-agentno-api-keyollamaopenaiorchestratorworkflowyaml-workflow
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/agency-orchestrator)Questions
- Does agency-orchestrator run?
- agency-orchestrator runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test agency-orchestrator?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit bed66133356b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test agency-orchestrator?
- The run that produced this verdict cost $0.29: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does agency-orchestrator take to install?
- 5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does agency-orchestrator need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing agency-orchestrator?
- 4 things broke in the recorded run, and 4 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for agency-orchestrator?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.