Skip to content

Track your agents' work beside your code

When agents write most of a codebase, git log tells you what changed, but not what was asked, what the agent was thinking or what it tried first. wisp keeps that next to the code: each task that built the repo is a file in .wisp/tasks/, linked to its commits, for everyone who clones the repo.

1. Turn it on

Terminal window
cd your-repo
wisp init # .wisp/ with history tracked in "ask" mode, and a note in AGENTS.md
git add .wisp AGENTS.md && git commit -m "chore: track agent work"
.wisp/wisp.yml
wisp: 1
history: { track: ask, inject: true }
  • track: ask offers to save each task you ship or mark done; auto saves them all; manual only what you save yourself.
  • inject: true starts each new task with the past tasks on the files its prompt names.

2. Save tasks

Saving writes the task’s spec, its report and its transcript into .wisp/tasks/ and .wisp/history/, for you to commit with the code, or in the same PR. Everything is scrubbed first: keys, tokens, .env values and private paths never reach the repo.

On a task wisp offers to save, press Save to repo. Any other task: ⋯ at its top right.

In the browser (wisp --browser, or your cloud wisp) it’s the same window, menus and keys.

The task's ⋯ menu open at its top right: Transcript, Shell, Rerun, Fork, Open in, Task options and moreThe task's ⋯ menu open at its top right: Transcript, Shell, Rerun, Fork, Open in, Task options and more

Old work too: a task from before the folder existed can be saved the same way.

Ship it already adds Wisp-Task: <id> to each commit it makes. For the commits an agent makes itself:

Terminal window
wisp hook install # a git hook: commits made in a task's run get the trailer
wisp hook status

4. Bring in work done outside wisp

Ran Claude Code or Codex in a terminal? Bring those sessions in as tasks:

Terminal window
wisp adopt --all --since 7d --track # the last week's sessions in this repo, saved
wisp skill install --agent claude # from now on, Claude Code hands each session to wisp when it ends

history: { adopt: ask | auto | off } says what happens to a session that ends.

5. Use the history

⌘K → Repo. Repo history lists the tracked tasks of the project, newest first. Filter by words, a path (src/auth/) or an agent. Open one to read what was asked and what happened; Resume starts a new task that carries on from there, on today’s code.

Your agents read it too: the note wisp init puts in AGENTS.md tells them to look up the tasks behind a file before they change it.

Why it’s safe to commit

  • No merge conflicts: one file per task, named by its id.
  • Small: specs and reports are short text; transcripts are compressed.
  • Reviewable: a PR shows which tasks wrote it, and anyone can read what was asked.