Bi

检查点与回退

出现偏差时可退回上一步继续,无需重新开始。

Markdown 原文Raw markdown

让智能体放手修改的前提是:改错了能退回来。Bi 的检查点就是为此而设。

它做什么

Bi 会在关键节点自动留下检查点,记录该步骤之前的状态。如果后续改动出现偏差,可退回某个检查点,让智能体从那里重新开始。

如何使用

在产物面板的改动清单中找到想回退的节点,选择回退。Bi 会恢复文件状态,你可以让智能体换个思路再试。

与版本管理的关系

检查点由 Bi 内置,无需你手动管理版本历史,适合「小步试错」。如果你需要长期追溯历史,仍建议使用专业的版本管理工具。

存储占用

检查点会随会话逐渐积累,占用一定空间。不再需要时,可以在产物面板中清理旧的检查点。

相关

Checkpoints and rollback

Undo a wrong turn instead of starting over.

Markdown 原文Raw markdown

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.