Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.kazzle.com/llms.txt

Use this file to discover all available pages before exploring further.

Kazzle’s file editor has two layers: a normal text editor for your changes, and a diff overlay for AI changes.

​
How AI edits appear

When the AI edits a file, changes appear as green (added) and red (removed) lines in the editor. Each changed region is one edit you can act on. While the AI is streaming, you see the edit in real time with syntax highlighting. After it completes, the view switches to a full diff.

​
Accepting and rejecting edits

Each edit has a floating bar with Keep and Undo buttons.
  • Keep accepts the change. The decoration disappears and the content stays.
  • Undo reverts the change. The AI’s text is replaced with the original.
Edits are independent. You can keep some changes and undo others in the same file. When every edit in a file is resolved, the file edit auto-resolves. Pending diff regions are read-only until you Keep or Undo. This prevents editing inside a region the AI just changed, which would break Undo.

​
Batch accept and reject

The thread’s File edits panel lets you accept or reject all pending edits for that thread at once.

​
Per-message undo

Each AI response has a Revert button. Clicking it restores all files to their state before that response and deletes subsequent messages. If other threads have pending changes on the same files, you’ll see a warning before proceeding.

​
Snapshots

Before each AI turn, Kazzle saves the previous file content to cloud storage. These snapshots power per-message undo: clicking Revert reads the old content from the snapshot and writes it back. Snapshots are storage-efficient. They cover the cloud machine’s files only, not database changes, deployed apps, or external API calls.

​
Cross-thread overlap

When a new AI edit overlaps with existing pending edits from another thread, the overlapping edits are auto-accepted. This prevents stale edits that can’t be meaningfully undone since the text is already overwritten. Non-overlapping edits from other threads remain pending.

​
Conflict handling

Multiple threads share the same cloud machine. When two threads edit the same file:
  1. Thread A edits a region. The file changes on disk.
  2. Thread B tries to edit the same region. Its edit fails because the old text doesn’t match.
  3. Thread B re-reads the file and adapts.
The AI handles this automatically. You don’t need to manage conflicts manually.