BRIEFLOOP / GUIDES

FAQ and data

Preserve drafts, stop tasks and understand data transfers.

Applies to desktop 0.21.0 and the 0.20.x service. Labels and capabilities vary by channel; the installer version is authoritative. Development features are not implied.

Before you start

Use a workspace you can back up. Model tasks require an authenticated runtime and permission to process the chosen materials.

Steps

1. Workspaces and records are stored locally. Cloud-model use sends relevant task, source, draft or feedback content to the selected service.
2. Search queries go to the search provider and web requests to target sites. MCP parameters and necessary credentials go to the configured connector; local stdio programs may also access the network.
3. Disabling public search does not stop model data transfers or guarantee network isolation for every runtime. Custom gateways and proxies may receive requests too.
4. Use the app’s stop control and wait for a terminal state. Closing a browser does not stop an independent service; follow desktop save and task prompts when exiting.
5. Back up the entire workspace while tasks are idle. Check materials and personal information before sharing logs, audit packages or folders, and exclude credentials.

What success looks like

Saved drafts and sources should remain accessible after failure. Deleting local copies does not delete data already received by third parties; their retention rules depend on the service and account configuration.

If something goes wrong

Diagnose HTTP 403, download and dependency errors by stage rather than repeatedly uninstalling and deleting workspaces. Record the version and error, use official releases and runtime diagnostics, and remove credentials and sensitive content before public support requests.

← All guides · Installation options →