---
title: "Checkpoints and rollback"
description: "Undo a wrong turn instead of starting over."
lang: en
---

Letting an agent change files is only reasonable if a wrong change can be undone. Checkpoints exist for that.

## What it does

Bi records a checkpoint at key moments, capturing the state before that step. If later changes go off track, you can return to a checkpoint and let the agent continue from there.

## How to use it

Open the change list in the artifacts panel, find the point you want to return to, and roll back. Bi restores the file state, and you can ask the agent to try a different approach.

## Relation to version control

Checkpoints are built in and need no manual history management. They suit small, rapid iterations. For long-term history, keep using a proper version control system.

## Disk usage

Checkpoints accumulate over a conversation and use some space. When they are no longer needed, clean up old checkpoints from the artifacts panel.

## Related

- [Artifacts panel](/docs/using-bi/artifacts)
- [Sessions](/docs/using-bi/sessions)