Desktop & Web
Use the right entry point and know where to return for your work.
Compare the two entry points
On a narrow screen, scroll the table sideways to see all columns.
| Capability | Desktop | Web |
|---|---|---|
| Conversation | Conversations in the local workspace. | Account chat and history. |
| Writing and resources | Workshop, drafts, copy library, profiles, and knowledge. | Chat and conversation attachments. |
| Project files | User-chosen directory and separately granted tool actions. | No local project tools. |
| Model sources | Available platform models, personal APIs, and supported subscriptions. | Available platform models. |
| History | Saved on the device in the desktop workspace. | Saved for the service account. |
Find content in the right place
For a desktop conversation, return to the same desktop workspace and check recent conversations or search. For saved copy, open the desktop Copy library. For a project output, check the chosen project folder. For web chat, use the corresponding web account’s history.
Signing into the same account does not automatically upload, merge, or restore desktop conversations, drafts, knowledge, or project files on the web. A missing desktop draft in the web interface is not evidence that the draft was deleted.
Before changing devices
Save the current edits
Check the saved state in the document you are editing.
Keep independent files
Copy important text into files you manage, and keep a separate copy of the project folder. Reopen exported material to check it.
Verify before clearing data
Confirm the independent copies contain the needed work before removing local app data. Do not use web history as proof of desktop backup.
Local storage and online requests
The desktop workspace saves local content on your device. Model requests still send the selected prompt and context to the configured service, so generation depends on that connection. Handling by the provider follows the chosen service’s rules.
Your data →