Checkpoints

Letting an agent edit freely only works if you can undo it. Checkpoints exist for exactly that.

What it does

Bi leaves a checkpoint at key moments, recording the state before that step. If later changes go sideways, you can roll back to a checkpoint and have the agent retry from there.

How to use

In the artifacts panel’s change list, find the node you want to undo and choose to roll back. Bi restores the file state and you can send the agent off in a different direction.

Relation to git

Checkpoints are a built-in lightweight undo, tied to the session’s change record — no git bookkeeping required. They suit small experiments; for long-term history, keep using git.