Rewind & Checkpoints

Checkpoints & Undo

LakshX quietly checkpoints your files before the agent edits them, so any change is reversible — one file, one message, or the whole session. You never have to trust the agent not to make a mess; you can just undo it.

Per messageFiles changed cardSessionundo bar by the composerShortcut/undo

How checkpoints work

Before each prompt runs — and before each mutation — LakshX snapshots the affected files into a private shadow history kept outside your repo. Undoing is a precise restore from that snapshot, so it doesn’t touch your real git state or anything the agent didn’t change.

Per-message: the Files changed card

Every response that edits files gets a Files changed card. On it you can:

Click a file path to open the diff and see exactly what changed.
Hit Undo on any single row to revert just that file.
Use Undo all N files to revert everything that message did.

The same per-file undo also sits next to the thumbs-up / thumbs-down / retry controls.

Session-wide undo bar

Anchored near the composer, the session bar aggregates every file the agent has changed across the whole conversation (latest change wins), with the same open-diff and undo controls. It’s the fastest way to walk back an entire session.

It notices conflicts

If you edited a file yourself since the agent touched it — or a later prompt also changed it — undo asks before overwriting, with Cancel and Overwrite and Undo. It won’t silently clobber your own work.

Works in every mode — including Royal

Checkpoints run in all modes. Even in Royal mode, where the agent has full autonomy, workspace edits are still checkpointed and reversible. (Undo covers your workspace; changes Royal makes outside it aren’t checkpointed.)

Undo vs. rewind

Reach for undo to surgically revert specific files while keeping the conversation. Reach for rewind to roll the whole conversation back to an earlier message.