Formulas (your setup as code)
A formula is your wisp setup written as files. In a repo it’s the .wisp/ folder: wisp reads every
*.wisp.yml (or .json, .toml) in it as one setup, the way Terraform reads every .tf in a folder. Split it
however you like: agents.wisp.yml, crew.wisp.yml, workflows/release.wisp.yml.
wisp: 1agents: reviewer: { harness: codex, effort: high, mode: plan } builder: { harness: claude, model: opus }skills: testing: { description: How this repo tests, path: docs/testing.md }connectors: linear: { url: "https://mcp.linear.app/sse", oauth: true }Every kind and field is in the resource kinds reference. wisp schema prints the same as
JSON Schema, for your editor.
Addresses and references
Every resource has an address <kind>.<name>: agent.reviewer, crew.ada, connector.linear. Any field can
refer to another resource or one of its fields:
tasks: nightly: { prompt: Update the dependencies, agent: "${agent.reviewer}" }References set the order things are created in, and a cycle is refused. wisp graph prints them, and
wisp mv agent.reviewer agent.critic renames one and rewrites every reference to it.
A field that names another thing takes its bare name too (agent: reviewer, goal: green-build, task: nightly,
connectors: [linear]), or the thing inline where the field allows it (goal: { text: … }). Either way the name is
checked wherever a formula is read: wisp validate, wisp apply, a run with --formula and the app’s Import all refuse
one that names nothing, and say what there is:
✗ tasks.nightly: no agent named reviwer: agents has reviewer (or claude, codex, auto)✗ crew.ada: team[].crew: a loop: crew.ada → crew.bo → crew.adaAn agent field also takes a harness (codex) or auto; a machine field a computer you added in the app, or this; a
task’s project: a project’s name as well as a folder. A module’s resources are referenced by their address:
${module.team.agent.reviewer}. Every file reads the same way, a .wisp/ folder, wisp apply -f one.yml, a
--formula and a task file’s formula alike: references, variables, locals, count and modules all work in each.
Variables, locals, outputs, count
variables: model: { type: string, default: opus } helpers: { type: number, default: 2 }locals: harness: claudeagents: critic: { harness: "${local.harness}", model: "${var.model}" } helper: count: ${var.helpers} # helper-0, helper-1 harness: codex instructions: "helper ${count.index}"outputs: critic_model: { value: "${agent.critic.model}" }Set a variable with -var model=sonnet, a --var-file, or WISP_VAR_model. wisp output prints the outputs.
Workspaces keep one set of variables each: wisp workspace new prod, wisp workspace select prod, and
${workspace} is its name.
Modules
A module is a formula folder you reuse, with inputs and outputs: a “review team” or a “nightly maintenance” setup shared across repos.
modules: team: { source: ../shared/review-team, inputs: { model: haiku } } pack: { source: "git::https://github.com/acme/wisp-modules//pack?ref=v1.2" }wisp init fetches them into .wisp/modules/ and pins them in .wisp/lock.yml; wisp init -upgrade moves
them. A module’s resources are addressed module.team.agent.reviewer.
Plan, apply, export
wisp validate # schema and checkswisp plan # what applying .wisp/ would changewisp apply # do it (asks first; --yes to skip)wisp destroy # take out everything it declareswisp export # what's set up here (in the app too), as fileswisp’s store is the state: wisp plan compares your files with what wisp has now, so a change made in the app
shows up as drift. wisp export writes it back to files, and wisp import <address> adopts one thing made in the
app into the files.
One-off overlays
A formula can run one task without being applied: its agents, skills, connectors, teams, projects and goals are that task’s alone, and nothing is left behind. Handy for trying a setup before you apply it.
wisp "review the diff" --formula f.yml # a task under it (several: --formula f.yml,g.yml)wisp run --formula f.yml "review the diff" # the samewisp run release --formula f.yml version=2.1 # the task f.yml declares as `release`, by its nameWith no --agent and one agent declared, that agent runs it; --agent may name any agent the formula declares, and a
goal it names by name is the formula’s. wisp run <name> --formula runs a task the formula declares (with
tasks.default under it and its {params} filled); any other words are the prompt.
A task file (wisp task export <id> > fix.task.yml, run with wisp run -f fix.task.yml) can name its formula
instead of carrying a copy of it: a file beside it, a module of its folder’s .wisp/, or a list of them.
wisp: 1task: { prompt: Fix the flaky test, agent: critic, goal: green-build }formula: [./wisp.yml, module.team]The names in its task (agent, goal, connectors, crew, team, project) are read against those and against what this wisp
has; one that names nothing is refused before anything runs. The same works from your harness (wisp_launch’s
formula) and in the app (+ → Formula or task file… in New task).