Hi all,
I built an execution engine with Claude Code for AI orchestration and pipelines, so a team can share deployed agents and skills and run them through a defined pipeline. It's called **sammy-pack**, it's MIT licensed, and I'd love feedback.
One thing to keep in mind: the project works, but it's meant as a template. Feel free to fork it and adapt it to what you need. Some areas may need work, but the execution engine itself is solid. If you hit a problem, ask Claude to take a stab at it. I built it mainly on my Mac and haven't tried it on Windows yet.
**The problem:** I had a pile of Claude agents (planner, dev, reviewer, QA, etc.) and kept wiring them together by hand in chat. It worked once, then didn't repeat. I wanted to write the pipeline down once and re-run it the same way every time.
**How I built it with Claude:** almost all of the code was written with Claude Code. I acted as the architect: I decided what the engine should do and how it should behave when things go wrong, and Claude Code did most of the implementation in the repo.
- **Design first, then build.** For each feature I talked through the design with Claude (for example, how a run should pause on an approval and resume later), then had Claude Code implement it on a branch with tests.
- **Reviews by other Claude agents.** Before merging larger changes, I had separate Claude agents review the diff for bugs. Claude then fixed what they found and I checked the fixes.
- **Live runs as the real test.** I ran real pipelines on my own projects, and when one failed I had Claude dig through the run logs and code to find the actual cause. Its first guess was often wrong, so I learned to make it prove the cause from the code before fixing anything. The stall detection and sleep-aware timeouts both came out of this.
- **Claude Code also keeps it running.** The repo ships a `/sammy-pack-setup` skill, so Claude Code can install sammy-pack on a new machine and test that it works.
**What it does**
- **One JSON file per pipeline.** Steps can be a single agent, parallel branches, loops (draft → critique → revise), routing, map over a list, sub-pipelines, and so on. Agents are plain markdown files with frontmatter.
- **Two ways to run the same file:**
- inside Claude Code, as a skill (`/sammy-pack run ticket-to-pr`), with no server needed
- from a web UI that runs agents through the Claude Agent SDK, streams every step live, and saves runs to SQLite or Postgres
- **Durable runs.** A run survives closing the tab or restarting the server. It checkpoints after each step, so resuming or forking skips the finished steps and spends no tokens on them.
- **Human in the loop.** You can lock a step so the run pauses for your approval. An agent that needs something only you know can ask you a question mid-run: only that step waits, and it carries on once you answer.
- **Sleep-aware.** Close your laptop mid-run and nothing times out. Timeouts count only awake time, the way Claude Code behaves in the terminal.
- **Triggers.** Runs can start from webhooks, cron, polling or queues, as well as by hand.
- **Visual editors.** The same pipeline can be edited as a list, a graph, a tree or raw JSON. You can also drop in a draw.io, Excalidraw or image diagram and have it turned into a pipeline.
**Where I actually use it:** software delivery. Ticket → plan → code → review → PR, plus QA sweeps that run several personas in parallel. The engine is general, though: the examples include research synthesis and approval flows.
**Honest limits**
- Single-tenant: one workspace, no hosted version.
- Full agent capability (tools, MCP, subagents) goes through the Claude Agent SDK. Other providers are text-only steps.
- Web is the real UI. The mobile app is only scaffolded.
- Built and tested on macOS. Windows is untested.
**Free to try:** it's MIT licensed and there's no paid tier. Clone the repo, run `npm install` in `app/`, then `./sammy-pack start` and open the printed URL. The `smoke-test` pipeline runs with zero tokens. If you use Claude Code, run `/sammy-pack-setup` in the repo instead: it checks your machine, installs everything and runs one small test for well under a cent.
Repo: https://github.com/qvhn/sammy-pack
I'd especially like to hear from anyone running multi-agent setups: what breaks for you? For me it was steps silently stalling while everything said "healthy", which is what pushed me toward durable runs and stall detection.