# Web App & Cloud overview

The Foxora web app brings tasks, projects, crews, runs, and generated artifacts into a browser. When a web task needs files or commands, Foxora gives the signed-in user an isolated Foxora Cloud workspace instead of reaching into the computer that opened the page.

![Web App & Cloud in Foxora v5.0.3](/docs/images/v5.0.3/web-cloud/new-task.webp)

## What the web app includes

| Area | What happens in the web app |
| --- | --- |
| Tasks | Create and resume browser tasks, choose a crew and autonomy mode, and review the transcript. |
| Projects | Work in cloud project folders or the task’s generated scratch project. |
| Files and editor | Browse, create, edit, rename, and download files stored in Foxora Cloud. |
| Terminal | Run a real cloud shell for the active project. Terminal tabs can reconnect with bounded scrollback while the browser task remains open. |
| Artifacts | Review generated Markdown, code, diagrams, tables, and other supported output in Preview or Code. |
| Runs | Follow background work without assuming that closing the Runs panel cancels it. |

Foxora Cloud is implemented with an isolated Daytona-backed workspace. Foxora owns the workspace identity, path mapping, resume behavior, and backup lifecycle; the product UI refers to the result as a Foxora Cloud workspace.

## What does not cross over automatically

- A folder opened in Desktop is not silently uploaded to the web app.
- Desktop and CLI task history stored only on a device does not automatically become web task history.
- A cloud project does not appear as a local folder until you download it or deliberately copy it into a local project.
- Local browser profiles, signed-in desktop applications, and device permissions remain on the device.

Use Desktop when the outcome depends on the current computer. Use the web app when the work should run in an isolated browser-accessible workspace.

## Complete a first web check

1. Open [app.foxora.ai](https://app.foxora.ai/) and sign in.
2. Choose **New Task**.
3. Read the selected autonomy mode and crew before sending anything.
4. Ask for one small output, such as a short Markdown comparison or a tiny project with a README.
5. Expand the tool activity if the task uses the cloud workspace.
6. Inspect the final artifact in both **Preview** and **Code** when both views are available.
7. Download or copy the output if it must exist outside Foxora Cloud.

The web runtime is ready when the task completes, the transcript shows the expected tool activity, and the final result opens or downloads successfully.