Practical overview
When it fits
Use Festival when a goal is substantial enough to need planning, review, persistent context, or continuation beyond one agent session.
Who it is for
- Developers using command-line or self-hosted coding agents.
- Teams that need planned work to continue across sessions or agents.
- People who want review points and traceable project records around autonomous agent activity.
Documented uses
- Turn a development or investigation goal into a structured plan for an agent.
- Require approval before planned execution proceeds.
- Preserve context and progress so work can continue later.
- Follow results through decisions, checks, and commits.
- Monitor a festival's progress from another terminal.
Requirements & limits
The repository is public and licensed under Apache-2.0. Documented installation covers macOS through Homebrew and macOS/Linux through Node.js and npm; Git is required. Native Windows support is being hardened, with WSL2 recommended for now.
- The workflow depends on an agent that can read files and run commands.
- Approval is supported, but the evidence does not specify the approval interface.
- Persistence uses files and Git, while file formats and synchronization behavior are not detailed.
- The primary interaction is through a CLI, including
fest nextandfest watch. - Festival supports several named agents, but the evidence does not establish compatibility guarantees for every tool.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up a camp for an existing project
Install Festival, create a camp, and link an existing local repository before starting agent work.
Before you start
- Git
- macOS with Homebrew, or macOS/Linux with Node.js and npm
- A local repository path
Steps
Install Festival with the documented Homebrew cask or npm package.
Run
festival doctorto check the installation.Run
camp init my-campfrom the directory where you keep your work, then enter the camp withcd my-camp.Run
camp project link /path/to/your-existing-repousing the full local repository path.Open the coding agent at the camp root.
Expected outcome
A camp is created with the existing repository linked under `projects/`, ready for an agent to use as its work context.
Guide limitations
- The existing repository remains in its original location; the evidence does not describe the internal attachment-file format.
- The documented setup does not by itself execute a festival or establish a completed agent workflow.
- Native Windows support is being hardened; the repository recommends WSL2 for now.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 4 October 2026
- Original website title
- Obedience-Corp/festival · Official homepage title · retained in its source language

