# Desktop versus web

Desktop and web share Foxora’s task-oriented interface, but they execute against different machines. Choose the surface from where the required files, applications, and account state actually live.

![Desktop versus web in Foxora v5.0.3](/docs/images/v5.0.3/web-cloud/new-task.webp)

| Capability | Desktop | Web app |
| --- | --- | --- |
| Working machine | This computer | Isolated Foxora Cloud workspace |
| Project files | Folders you explicitly open on the device | Cloud project folders |
| Editor and terminal | Local project and local shell | Cloud project and cloud shell |
| Desktop applications | Available through approved Computer Use permissions | Not available |
| Existing browser profile | Available when explicitly authorized | Uses browser-accessible or managed cloud behavior; it does not inherit Desktop’s local profile |
| Long-running workspace | Depends on the local app and runtime | Cloud machine can suspend and resume independently of the laptop |
| Moving files to the other surface | Open or copy them locally | Download files or a project archive |

## Choose Desktop when

- the task must edit a folder already on this computer;
- Foxora needs a local Git worktree, local development service, or installed application;
- the task needs an authenticated local browser profile;
- you need native file pickers, desktop notifications, microphone, Accessibility, or Screen Recording.

## Choose web when

- you want to begin from any supported browser without installing the app;
- the work should stay in an isolated cloud project;
- a cloud shell and web editor are sufficient;
- the task should remain available after the current browser or laptop is closed.

## Avoid false continuity

Using the same account does not mean every local object is synchronized:

- Desktop and CLI on the same device can use the same local runtime and data home.
- The web app uses cloud task and workspace state.
- Local folders remain local until you intentionally upload, clone, or copy their contents.
- Cloud output remains cloud-side until you download it or push it to an external repository.

Before continuing a task on another surface, confirm the project files, branch, task transcript, and latest artifact are actually present there.