- Category
- AI Agents
- Rank
- No. 1244Tools index
Previous survey · No. 1239 ·
- Pricing
- Open Source
- Type
- TOOL
- Use case
- Coding
- Interfaces
- CLI · Agent Skill / Plugin
- GitHub
- 161 stars
- Latest release
- v0.3.38
- Date
About
Festival is a framework for organizing intent and looping work with AI coding agents, aimed at reaching the desired outcome without wasting tokens. The repository includes plugins for Claude Code and Cursor, a Go-based CLI and context-management tooling.
At a glance
Festival organizes multi-step coding-agent work into tasks and review checkpoints stored in Git. It is worth trying when work spans several sessions and a new session needs to see what was decided, what passed and what to do next.
Good fit
Developers delegating longer changes with dependencies or handoffs across sessions.
Consider something else when
Skip it for a small change that fits in one session and needs little planning or verification history.
Start here
Use one scratch repository and one goal with a measurable outcome. Create a Camp workspace and a Fest plan, complete one task, then open a second session and see whether it can find the next step and the evidence for the completed one.
Cost and requirements
The repository is Apache-2.0. The base suite needs Git and an existing coding agent. Obey is installed separately if you want a local daemon to supervise runs. Your agent provider can charge separately.
Limits to know
Task files and gates help preserve evidence, but their value depends on the checks you define. Review what gets recorded in Git before sharing the workspace. The daemon uses its own provider setup.
Sources checked 2026-11-05. Source-based assessment.
Read the source review
What it does
Three command-line tools that turn a goal you hand a coding agent into a written plan kept on disk. Fest breaks the goal into phases, sequences and tasks, stored as Markdown in numbered folders, and its next command serves the agent one task at a time with the surrounding goals attached. Camp is a workspace that links repositories you already have, without moving them, and holds research and decisions between sessions. An optional background daemon, Obey, installs separately and launches and supervises agents. Any agent that can read files and run shell commands can drive it; there is no API to integrate.
Why it's ranked here
The central bet holds up: plans, progress and review gates live in plain files under Git, so a fresh session or a different agent resumes from a record rather than a lost chat. Distribution is unusually complete for a planning tool. One release config ships static Go binaries for Linux, macOS and Windows through Homebrew, npm, Scoop, Debian, RPM, Alpine and Arch packages, all Apache 2.0. The planning and workspace engines themselves sit in separate repositories pinned into this one, so the mechanism behind the documentation is not visible here, and the payoff depends on work large enough to need phases.
What's good
The structure is the state. Folder numbering encodes order, and two phases or steps sharing a number run in parallel, so dependencies are readable in a file listing. Festivals move through planning, ready and active folders into a completed or archived pile, which makes status a directory you can inspect. Every implementation sequence ends in mandatory testing and review steps. The suite installer checks signed package metadata against a built-in key and refuses unsigned content by default. The docs are candid about limits: tracker sync is a script you write, and a finished local task does not mean the issue should close.
Tradeoffs
Windows is a partial citizen: syncing, cloning from another camp and artifact transfer are unavailable there, the npm package skips Windows, and there is no Windows ARM build. The Homebrew cask strips the macOS quarantine flag from all three binaries on install, and the Alpine instructions use an untrusted-package flag. Setup advice conflicts: the README tells agents never to run festival setup, while the Homebrew install message tells users to run it. Shell shortcuts need lines added to your shell config. And the method front-loads requirements before any implementation step exists, which is overhead a small fix does not need.
How to use it well
Fit it to multi-session work with a reviewable outcome: a feature spanning several repositories, an investigation that ends in a recommendation, a recurring dependency review. Keep small, understood changes in a single agent session. Create one camp, link one existing repository, and have the agent plan a standard festival, then read the plan before approving execution. Watch progress from a second terminal. Keep your issue tracker for discussion and priority; Festival holds the execution record. Add the Obey daemon only once the loop works by hand, and keep the agent's own permission settings tight, since the tool does not manage them.
Technical notes+
.goreleaser.yaml builds three CGO-disabled Go binaries (fest from ./cmd/fest, camp from ./cmd/camp, festival from the festival-installer directory) for linux, darwin and windows on amd64 and arm64, ignoring windows/arm64. Its comments state fest and camp are pinned submodules whose version stamps come from FEST_* and CAMP_* environment values, and the build fails if one is unset. Packaging covers nfpm deb, rpm, apk and archlinux, an AUR festival-bin, a Scoop bucket and a Homebrew cask whose post-install hook runs xattr -dr com.apple.quarantine. The cask caveat says to run festival setup, which README.md tells agents not to run. docs/install.md documents signed-metadata verification in the installer and the Alpine --allow-untrusted command. docs/methodology/overview.md defines the phase, sequence, task hierarchy with 3-digit and 2-digit prefixes.
Observed
- License
- Apache 2.0 (LICENSE; release config declares Apache-2.0)
- Language
- Go, static binaries built with CGO disabled (.goreleaser.yaml)
- Interfaces
- CLI: fest, camp and the festival installer; optional Obey daemon installed separately (README.md)
- Platforms
- Linux and macOS on amd64 and arm64, Windows on amd64 only (.goreleaser.yaml)
- Install surface
- Homebrew cask, npm, Scoop, deb, rpm, apk and AUR packages (docs/install.md)
- Windows limits
- Camp sync, clone from another camp and artifact transfer unavailable on Windows (docs/install.md)
- State storage
- Plans and progress are Markdown files and folders tracked in Git (docs/guides/agent-workflows.md)
- Tracker integration
- No native tracker sync; user supplies a script or justfile (docs/compare/festival-vs-issue-trackers.md)
- Source layout
- fest and camp built from pinned submodules (.goreleaser.yaml)
Read from README.md, LICENSE, docs/install.md, docs/getting-started/quickstart.md, docs/methodology/overview.md, docs/methodology/why-festival.md, docs/guides/agent-workflows.md, docs/compare/festival-vs-issue-trackers.md, .goreleaser.yaml.
Tags
Comments (0)
No comments yet
Editorially curated, with community endorsements as a secondary signal. Corrections welcome.