professorpalmer/Puppetmaster
Provider-neutral control plane for durable-state agent swarms: subprocess workers, leases, artifacts, memory, and deterministic stitching.
What it solves
Puppetmaster addresses the lack of durable state and reviewable output when using various AI agent CLIs and provider APIs for complex engineering tasks. It prevents the loss of progress and expensive context window growth by storing agent results in a structured database rather than relying on a single, ever-growing chat transcript.
How it works
It acts as a supervisor and job store that sits between "pilots" (MCP-enabled tools like Cursor Agent, Grok Bot, or Claude Desktop) and "workers" (agent adapters like Claude Code, Codex, or provider APIs).
- Routing: It routes tasks to available models or specific worker adapters.
- Execution: Independent workers claim tasks and execute them.
- Persistence: Instead of sharing a transcript, workers write typed artifacts and evidence to a SQLite database.
- Retrieval: A subsequent model can retrieve these stored artifacts to create a stitched summary or continue work without inheriting the previous model's provider KV cache.
Optional integration with CodeGraph can provide structural code indexing to enhance the context provided to workers.
Who it’s for
Developers who perform repository investigations, audits, refactors, and implementations and want a way to inspect, resume, and review the output of multi-step AI engineering workflows.
Highlights
- Durable State: Uses SQLite to store job results, allowing for inspection and resumption of work.
- Multi-Adapter Support: Integrates with various tools including Cursor, Claude Code, Codex, and Grok Bot.
- Cost Efficiency: Demonstrated lower actual spend on SWE-bench Lite through cost routing and durable retries.
- MCP Integration: Provides MCP tools for pilots to delegate larger tasks to durable workers.
- Job Dashboard: Includes a live dashboard to monitor and view job progress.
Related
- Project
- Project
- Project
- Project
- Project