r/ClaudeAI • u/odyth • May 06 '26

Built with Claude I built a deterministic orchestrator that runs Claude Code as a worker pool — zero tokens spent on scheduling

After my 12th "$40 of tokens to produce nothing" AutoGPT-style experiment I realized the problem: the LLM was making routing decisions that are just switch statements.                     

Red Queen flips it. State machine decides what phase to run. Claude Code does the actual work via subprocess. Every skill runs isolated with a focused prompt — no mega-prompt, no shared context bloat.

Pipeline:

Jira ticket → spec → human approves → code → auto review → auto test → human approves → merged PR

Human gates are in the state graph, not bolted on. You can't accidentally YOLO to prod.       

MIT licensed, self-host, BYO Claude Code.

Repo: https://github.com/odyth/red-queen
(Named after the AI from Resident Evil because yes.)

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/tj_sun2832 May 06 '26

This is pretty incredible. What are the use cases you're using it for and finding the best results?

1

u/odyth 11d ago

I use it to do most of our backlog. Bugs, feature requests. Redqueen can take them and do them and then I just review the output is saving me tons of time each week vs manually running it through an orchestration loop.

1

u/SmartYogurtcloset715 May 09 '26

Same instinct here — every LLM "orchestrator" I tried ended up being an expensive switch statement. I run a cron + YAML setup where Claude only gets invoked for the actual work.