Real-world
Hybrid orchestration
Concrete workflows, including the tradeoffs and limitations reported by their authors.
this collection
Frontier plans the tickets, Qwen writes the code
A short but clean division of labor: a frontier model decomposes work into tickets, and a local Qwen model implements them on production code, daily.
Local as a verified subagent — but not trusted to touch files alone
A frontier orchestrator dispatching work to a local Qwen 3.8 27B subagent makes longer, harder jobs safe to hand off — but this person draws a hard line at giving any LLM unsupervised control of local files.
A local model and Codex reviewing each other's work, with a hard stop on disagreement
The same Qwen 3.8 27B instance that drives this person's Hermes agent also sits as an MCP tool for Codex, reviewing its proposals and its final output — and the task simply stops if the two can't agree.
A local model decides what's safe to send to the cloud
Before anything reaches a frontier model, a local pass screens it first — for example, checking with high confidence whether an email is non-confidential enough to triage externally.
An overnight local subagent running unfinished work through cron
Hermes uses a multi-GPU local server as a coding subagent, with cron inventorying unfinished work overnight and a cloud model reviewing the result.
A three-layer AMD ROCm agent architecture for 24/7 local automation
A Radeon 6650 XT runs quantized Qwen models through vLLM and Ollama, while a custom three-layer harness handles private, deterministic automation around the clock.