Profile imageAaron Jackson
Back to Projects
Cover image for Orchestrator

Orchestrator

2026

AI
AI Agents
AI Tools
LLM
Workflow Automation
Voice AI
API Integration
About the Project

What. Orchestrator runs AI coding agents as a fleet instead of a browser tab. It takes a task, routes it to a registered node that has the right capability and a free slot, runs the agent sandboxed in Docker or distrobox, and streams the session back. Claude Code, Codex, Copilot CLI, and OpenCode are all supported backends. Operators drive it from a React dashboard, an orch CLI, a Discord bot, or any MCP client.

Why. Agent tools are individually capable and collectively chaotic. Every session is an island: no shared task state, no cost ceiling, no memory of what the last one learned. Orchestrator is the layer underneath — one task graph, one knowledge base, one budget.

How. A Fastify server over PostgreSQL (Drizzle, pgvector) and Redis coordinates the fleet:

  • Tasks — parent/subtask hierarchies with a real dependency graph; downstream work auto-promotes as its dependencies clear.
  • Dispatch — nodes self-register and heartbeat, advertise their capabilities, and hold per-backend concurrency slots. Work queues when the fleet is full.
  • Model routing — cascades local → metered → pay-per-token, skips local models on high-complexity work, and enforces daily budget ceilings and rate limits in Redis.
  • Knowledge — hybrid semantic and full-text search (locally generated pgvector embeddings alongside a tsvector index) over a typed, weighted graph of code, docs, commits, tasks, and decisions, with community detection for neighborhood queries.
  • Memory — namespaced, TTL'd agent memory, itself indexed into the graph.
  • Reuse — installable feature packages and project templates, with verification and update propagation.
  • Interfaces — an MCP server (63 tools, stdio and streamable HTTP), Whisper-backed voice dictation, and a Discord bot with slash commands and a wake-word voice pipeline.

The node client is a Tauri v2 tray app. The dashboard renders live terminals, model-routing traces, and a 3D view of the knowledge graph.

Orchestrator has dispatched its own development since roughly week one: branches are named for its own task ids, and most of its pull requests were written by agents it scheduled.

Stack: TypeScript, Fastify, Drizzle + PostgreSQL/pgvector, Redis, BullMQ, React 19 + Vite, Tauri v2 (Rust), Docker.

Built Feb–Jul 2026, across roughly 2,800 commits.