Iris — client front
Local edge component on your development machine. Routes requests to your fleet or falls back to Anthropic automatically.
Pantheon
Agent teams across Anthropic and local models — on the compute you already own, coordinated across networked machines without a shared harness.
Install
Section titled “Install”curl --proto '=https' --tlsv1.2 -fsSL https://pantheon.lhocke.dev/installs/install.sh | shOne script, three configuration profiles — client front, orchestrator host, or model backend. Run it on each machine in your fleet and answer the role prompt.
What you get
Section titled “What you get”minotaur — orchestrator
Sits on your most capable local host. Routes teammate traffic, owns the work-host auth boundary, and schedules work across the fleet.
hydra — translator
Anthropic↔local model protocol bridge. Converts between the Anthropic Messages API and Ollama-compatible endpoints transparently.
hermes — message bus
Fleet coordination layer. Handles capability discovery, live topology, and message routing between components across machines.
How it works
Section titled “How it works”Pantheon is not a cloud service. Every component runs on hardware you control — your laptop, a homelab node, a workstation, or any mix. Networked machines coordinate via hermes without requiring a shared harness or central authority.
Agents run on whichever model fits the task: Anthropic Sonnet for reasoning depth, a local Qwen or Llama for volume work, or a GPU workstation for batch inference. Iris handles routing; your policy decides the split.
Read the architecture
Architecture overview → — the three-role topology and install flow.
Operations guide
Operations → — health checks, log tailing, and fleet management.