Your repo's .wisp folder
wisp init gives your repo a .wisp/ folder. It holds two things:
- Your agent setup, as code: which agents, crew, skills, MCP servers, rules and workflows this repo uses
(
*.wisp.ymlfiles). See Formulas. - The tasks that built the code: one file per task, with what was asked, what the agent answered, its transcript and the commits it made. See The .wisp folder.
cd your-repowisp initgit add .wisp && git commit -m "chore: wisp setup"wisp init writes .wisp/wisp.yml, adds a short note to AGENTS.md (and CLAUDE.md when there is one) so
agents know about the folder, and fetches and locks any modules the setup uses.
Which tasks the repo keeps
.wisp/wisp.yml says it:
wisp: 1history: { track: ask } # auto | ask | manualask(the default): when a task in this repo is shipped or marked done, its answer offers Save to repo.auto: every such task is saved.manual: nothing is saved unless you save it, with Save to repo orwisp track <id>.
A saved task is written to .wisp/tasks/ for you to commit, scrubbed of secrets and private paths. Commits that
Ship it makes carry a Wisp-Task: trailer, so the code and the task point at each other.
Use it
wisp log # the tasks that built this repo, newest firstwisp log src/auth # the ones that touched a pathwisp blame src/auth/login.ts:42 # which task wrote that line, and what it was askedwisp resume <id> # a new task that carries on from where that one stoppedAgents can read it too. With history: { track: ask, inject: true }, a new task starts with the past tasks on the
files its prompt names (the five most relevant), so it knows the decisions already made there.