Local runs and workspaces
Local runs keep model funding and durable run state on the user's device. They are useful for code and document workflows that need a selected folder but not a hosted machine.
Approve a workspace
Choose a folder from Settings or the run setup. Browser permission is explicit and can be revoked. Codelit stores the handle locally and reads only files selected by the workflow's context rules.
Understand the boundary
A browser local run can read and generate artifacts, but it is not a hidden shell. Commands that require a terminal, unrestricted networking, or background execution need a managed executor or a future native runtime.
- No extension is required.
- The open tab provides the compute lifecycle.
- IndexedDB stores local checkpoints and receipts.
- User-selected files are never deleted during account deletion.
Keep it reliable
Keep the tab awake while a run or local schedule is active. Review the terminal before closing. Interrupted runs can resume from their last safe checkpoint when the same account and workspace are available.