Practical overview
When it fits
Use it when a deliverable calls for coordinated contributions from several AI roles and you want workflow-level organization, acceptance criteria, or human approval points.
Who it is for
- People assembling AI roles to produce structured work such as plans, analyses, articles, or code-review reports.
- Teams or individual builders who want to configure and run multi-step AI workflows through a graphical interface, CLI, or YAML.
Documented uses
- Break a broad request into role-specific tasks and coordinate their execution.
- Bring multiple AI perspectives together in a single deliverable.
- Define workflow acceptance criteria and route major decisions for human approval.
- Edit workflows visually or configure them with YAML.
Requirements & limits
The project identifies itself as Apache-2.0 licensed. Its README describes CLI installation through npm and a desktop app with the engine and Node bundled. Model access requires either a supported provider API key or an installed and authenticated compatible local CLI; the README says the latter can be detected automatically.
- A model provider or compatible local CLI is needed for AI work; the project itself is orchestration software.
- The README describes major-decision sign-off and acceptance checks, useful when workflows need explicit review points.
- The project supports graphical Studio use as well as CLI and YAML configuration.
- The implementation language is TypeScript and the repository specifies the Apache-2.0 license.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Start the local Web Studio
Open the local graphical interface for configuring and running workflows.
Before you start
- A working Agency Orchestrator CLI installation so the
aocommand is available.
Steps
Run
ao weblocally.Use the browser-based Studio to select experts, run workflows, view outputs, and intervene while they run.
Expected outcome
The local Web Studio provides a graphical interface for workflow use and monitoring.
Guide limitations
- The README does not specify a browser address or setup options for this step.
- Using CLI-based providers requires the corresponding provider CLI to be installed and logged in; API-key providers require their key to be configured.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 10 October 2026
- Original website title
- jnMetaCode/agency-orchestrator · Official homepage title · retained in its source language

