Revert Best Practice

Bolt.new maintains a full history of every AI action. The revert feature returns the project to any previous state instantly. Using revert immediately when a change breaks something prevents compounding complexity and is faster than trying to fix forward.

Syntax

bolt-new

// When to revert:
1. A change introduces a new bug
2. Bolt's fix broke more than it fixed
3. An unintended file was modified
4. A new library was added you didn't request

// How:
Open the history panel → select last known-good state → revert

// Then:
Approach the same change with a more scoped, targeted prompt
or use the Diagnostic Package to get a root-cause diagnosis first.

Example

bolt-new

// Scenario:
Bolt added pagination to the task list. The task list now crashes
on load. The error is in TaskList.tsx.

// Wrong approach:
Prompt: "Fix the crash in TaskList.tsx"
// This compounds — now Bolt is guessing what it broke

// Right approach:
1. Revert to before the pagination change
2. Write a more targeted pagination prompt:
   "Add pagination to TaskList.tsx only.
    Use page size of 20. Add prev/next controls.
    Do not modify the useTaskFilters hook or any other file."
3. Verify the targeted change before moving on.