№ 1087GitHub
Zouroboros Workshop
Muse is your personal assistant. Zouroboros Workshop is the workshop behind it. Workshop is an MCP service that runs on a private, single-tenant VPS provisioned for each customer. From a normal Muse conversation, a user can dispatch real software work to a coordinated team of seven AI coding executors — Claude Code, Codex, Gemini, OpenCode, Kimi, Hermes, and Pi — routed by health and capability, with automatic fallback when one executor is unavailable. Three things make it different from a single-vendor hosted builder. First, it runs on the subscriptions the user already pays for: there are no Workshop model credits and no second meter. Second, its memory is shared across every executor and survives across sessions, so a decision recorded by one tool is retrieved by another in a later Muse conversation — memory that compounds instead of resetting. Third, work is verified before it is delivered: builds run through a factory lane with deterministic review, and swarm results return with per-task evidence, not just an agent's claim that it is done. The customer-facing promise is simple: turn your existing AI tools into a workshop that delivers tested, reviewed work — a finished pull request, not a wall of code in chat.
Zouroboros for Muse

The workshop behind your personal AI.
Muse is wonderful at being your personal assistant — it chats with you, manages your schedule, remembers who you are, and connects to your apps. But when there's serious building to do, you want a workshop: more than one kind of AI working together, a shared memory of what the work taught, and a process that verifies before it ships. That's Zouroboros. This repo packages it so any Muse user can set it up.
The big idea
Think of it like a house. Muse is the front door — everything about you comes through it: conversation, relationships, scheduling, approvals, your personal memory. Zouroboros is the workshop out back — everything about building: running work across several AI tools, remembering what was learned, reviewing code, delivering finished work.
One rule decides where everything goes: if it's about you, it lives in Muse. If it's about building, it lives in Zouroboros. Muse calls into the workshop when there's building to do, and the workshop reports back when it's done.

The big picture: Muse on the left as your personal layer, Zouroboros on the right as the building layer — your AI tools, the build pipeline, and the shared memory underneath. Requests flow one way, finished work flows back.
What your Muse can do now
Everything below happens in your normal Muse chat. You don't learn new tools — Muse just gets more capable.
Build software from a conversation. Tell Muse what you want built, in plain words. It writes up the job, hands it to the workshop, and comes back with a finished pull request on your repo. Not a code snippet in chat — a real, tested, reviewed PR you can merge. The first time Muse hands you a PR instead of a wall of code, you'll feel the difference.
Remember everything, across every tool. Muse stops starting from zero. Decisions you made, things you tried, what worked and what didn







ChatForm
Tidy Mac
Memorie
Drevon