Local data and browser storage
Local workspaces, indexes, checkpoints, artifacts, schedules, and receipts use account-scoped browser storage. They stay on this device unless a reviewed excerpt is sent to the model provider selected for a run.
Know what is stored
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.
Control what leaves the device
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.
Delete local data safely
Settings > 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.
- Stop any run using the workspace.
- Open Settings > Local data and delete the workspace.
- Confirm it no longer appears in Local data, the context picker, or local History.