ai-orchestrator
Frameworks & Eval · tested 2026-06-17 · re-test due 2026-09-17 · by the Hlido desk, not the vendor
In short: Clever Claude Code + Ollama hybrid that uses local LLMs for the expensive coding work — promising cost optimization pattern, still early (97 stars).
4 PASS · 1 FAIL of 5 public-surface claims
Quick answer
ai-orchestrator scores 58/100 (STEADY) on Hlido’s independent, hands-on test (reviewed 2026-06-17). STEADY (58) because the cost-optimization architecture is a real insight worth borrowing, the CI passes, and the pipeline design is methodical. Pricing: Open source (free entry point documented).
The core insight in ai-orchestrator is sound: route the expensive thinking steps to Claude and the mechanical code generation to local Ollama models, coordinated by a TypeScript dependency-graph orchestrator. It's an attempt to reduce API costs by splitting the pipeline — Claude for triage, planning, and review (the hard reasoning), Ollama for the bulk code generation (where repetition is tolerable). The 6-step pipeline (triage → plan → orchestrate → code → pre-review → build → review → fix loop) is methodical and shows domain knowledge. CI passing and the documented architecture add credibility beyond a typical 97-star experiment. What the project is not: a polished product. There's no GUI, no installer, no hosted option. It requires both Claude Code and Ollama configured locally. The described pipeline reads as an internal dev tool that was open-sourced — useful for developers who want to clone and adapt the pattern, less useful for teams wanting to deploy it as-is. 97 stars suggests early adoption but not community validation.
Why STEADY
STEADY (58) because the cost-optimization architecture is a real insight worth borrowing, the CI passes, and the pipeline design is methodical. Not higher because 97 stars = early experiment, no installer/packaging, and requires two separately configured systems (Claude Code + Ollama) to work. Borderline FADING but held STEADY because the concept is more useful than the project's footprint implies.
Public-surface checklist
- PASS Homepage loads (required)
- PASS Primary value prop (required) — 'Portable multi-agent AI developer setup for Claude Code + Ollama'
- PASS Cta present (required) — GitHub repo with README install instructions
- PASS Pricing or access — Free and open source (MIT)
- FAIL Evidence or demo — No demo — must configure and run locally
What we saw
1 screenshot captured by the Hlido engine during the reviewed run (run-e696e47d43edf6ae-github-com). Our own captures — not vendor marketing material.
What it does well
- Claude + Ollama routing is a genuine cost optimization — uses the right model for each task step
- 6-step pipeline with dependency graph execution is more sophisticated than typical coding assistants
- TypeScript orchestrator with documented architecture — not a throwaway script
- CI badge passing adds credibility for an experimental project
- Zero external dependencies beyond Claude Code + Ollama — self-contained for what it does
What it fails at
- Requires both Claude Code AND Ollama configured — double setup barrier
- 97 GitHub stars = early experiment, not validated approach
- No installer, no GUI, no deployment story — clone-and-configure only
- No published benchmark showing cost savings vs pure Claude approach
- Fix loop limited to 3 rounds with no graceful recovery — may leave broken code
Best for
- Developers already running both Claude Code and Ollama who want to reduce API costs
- Teams with high code-generation volume wanting to experiment with hybrid routing
- Engineers who want to study and adapt the dependency-graph pipeline pattern
- Projects where bulk code generation can tolerate lower model quality (Ollama) and review quality is paramount
Not recommended for
- Teams without existing Ollama deployment (setup cost exceeds benefit for occasional use)
- Projects requiring high code correctness from the Ollama generation stage
- Production deployments without additional reliability engineering beyond the current fix loop
- Non-TypeScript/Claude Code projects
Pricing & access
- ModelOpen source
- Free entry pointYes — a free tier or open-source edition is documented
- Pricing findable on the public surfacePASS Free and open source (MIT) (tested 2026-06-17)
Derived from Hlido-held evidence only (engine checklist + editorial text); quotes are verbatim from the scorecard; not vendor-supplied; re-derived daily. Verify current prices on the vendor's pricing page. Last verified 2026-06-17.
Compared to
-
OpenAcme
claude-code-cost-optimization
OpenAcme is a full AI workforce platform with multi-provider LLM and web/CLI UI. ai-orchestrator is a focused cost-optimization pipeline for Claude Code + Ollama. OpenAcme is broader; ai-orchestrator is a sharper tool for a specific optimization.
Agent relevance
CLI MCP
Agentic-Commerce Readiness 54/100 · INTEGRABLE
Independent readiness for agent delegation & transaction. How it’s scored · check live
Claude Code skill-based invocation. Uses /implement trigger in Claude Code to start the pipeline. MCP integration mentioned. Not designed to be called externally — it operates as a Claude Code skill that orchestrates Ollama subagents.
Agent-friendly score: 6/10
Score over time
The longitudinal record — every point is the score as published on that date. Raw series.
Evidence
scorecard.json · transparency passport · registry · methodology
Embed this trust badge
Markdown
[](https://hlido.eu/check/?agent=mybono-ai-orchestrator)HTML
<a href="https://hlido.eu/check/?agent=mybono-ai-orchestrator"><img src="https://hlido.eu/badge/mybono-ai-orchestrator.svg" alt="Hlido trust score"></a>