Codelit keeps a local copy of the open Thread and tracks which items the server has acknowledged. If a connection interrupts saving, keep using the same browser and account. Reopening the worker or reconnecting retries pending conversation saves; it does not run the task again or approve an external action.

• Do not clear site data or leave an incognito session before unsynced work has reached the server. Local browser storage is not a backup.
• If local and online edits differ, choose Review versions. Compare On this device with Saved online, then choose Keep my edits or Use online edits. Decide later leaves both versions untouched.
• Only the conflicting items are replaced by your choice; other local messages and online results are kept. If either reviewed version changes again, Codelit checks it again before saving.
• If browser storage is full or unavailable, keep the page open until saving is confirmed. Free storage before retrying; closing the page can lose work that exists only in memory.

Completed hosted Browser and Computer results with captured evidence offer Save report to Files. The report preserves the full result summary, whether it was complete or partial, its completion time, and references to the source run and evidence. Saving does not rerun the task or send it to another integration.

1. 1Select Save report to Files below the finished result, or ask Save these findings to Files in the Thread.
2. 2When several results could match, choose the result to save. You can also ask Save the latest Browser result to Files. A running or failed latest task does not silently save an older result.
3. 3Open the saved report immediately, or open Files > Reports later while signed in to the same account.
4. 4Use Download for a plain-text copy or Source Thread to return to the original conversation.

• Reports are private cloud records encrypted at rest, unlike the folders in Files > On this device.
• Repeating Save for the same unchanged result returns the same report.
• Reports preserve evidence references, not screenshots, browser cookies, or live-session credentials. The underlying evidence may expire.
• Deleting a report leaves the original run unchanged. Delete account & data also removes your saved reports.

Codelit stores a bounded workspace index and local Agent run state in IndexedDB. The active workspace pointer and lightweight History references use account-scoped browser storage. Switching accounts cannot reopen another account's local data.

• Workspace names, paths, and reviewed excerpts support local context selection.
• Checkpoints and artifacts make interrupted local runs resumable.
• Receipts preserve bounded inputs, outputs, evidence, and cost.
• In-tab schedules require the same browser, account, and available workspace.

The workspace review shows the exact files and excerpts selected for context. Only checked excerpts are included in the model request; Codelit does not upload the full folder by default. Secret-like content is blocked before context assembly.

Settings > Browser and local > Local data shows workspace count and index size. Deleting a workspace also removes its local checkpoints, artifacts, receipts, schedules, active pointers, and linked local History entries. Account deletion clears Codelit-owned browser state but never deletes source files from your device.

1. 1Stop any run using the workspace.
2. 2Open Settings > Browser and local > Local data and delete the workspace.
3. 3Confirm it no longer appears in Local data, the context picker, or local History.