workflow-runner

You can execute YAML workflows without API keys by loading the agency-orchestrator file into your current session. The active LLM directly acts as the execution engine to parse and run the multi-role tasks.

Yes, multi-role collaboration tasks run directly in your current session. The workflow engine handles role-based execution and aggregates the results across different stages without external dependencies.

The execution engine handles errors by providing clear execution stages and context persistence. This ensures that multi-role orchestration failures are caught and managed within the active session.

No external dependencies are required to run agency-orchestrator YAML files. The tool operates without API keys for the current session by using the active LLM to process the workflow directly.

The best way to parse and aggregate multi-role YAML workflows is to use the active LLM as an execution engine. It triggers when a YAML file is provided, handling end-to-end orchestration and result aggregation directly.

You can run YAML workflow files without external keys in AI tools like Claude Code, OpenClaw, and Cursor. Load the file into the active session to execute multi-role orchestration directly.