# Cloud projects and workspaces

A Foxora Cloud workspace belongs to the signed-in user. Projects are folders inside that isolated workspace, while tasks hold the conversation, crew, autonomy mode, run state, and artifact history.

![Cloud projects and workspaces in Foxora v5.0.3](/docs/images/v5.0.3/web-cloud/projects.webp)

## Project and task are different

| Object | Contains | What happens when you switch it |
| --- | --- | --- |
| Task | Transcript, selected crew, autonomy mode, runs, and artifacts | Reopens the recorded work and its current context. |
| Project | Source files, folders, Git history, and generated project files | Changes the filesystem and command working directory. |
| Cloud workspace | All cloud project folders for the signed-in user | Is created or resumed by Foxora when cloud tools need it. |

A task without a user-selected project receives a generated per-task scratch project. That keeps its shell commands, file writes, Files tree, and downloads anchored to one location.

## Work with the project collection

1. Open **foxora → Projects**.
2. Search by the project name or generated folder identifier.
3. Use grid or list view to inspect the collection.
4. Select **Open** on the intended project.
5. Confirm the project name in the task header before asking Foxora to edit or run anything.

The collection shows cloud projects, not folders from the computer running the browser.

## Create, import, and export

- **New project** creates a folder in Foxora Cloud.
- A pasted public Git URL can be cloned into the cloud workspace.
- A repository selected through a connected GitHub account uses the authorized import path; private credentials are not copied into the sandbox.
- A single file can be downloaded directly from the Files view.
- A folder or complete project can be packaged server-side and downloaded as an archive.

Downloading is the boundary that moves project bytes from Foxora Cloud to the current computer. Confirm the browser completed the download before removing or replacing a cloud project.

## Keep projects reviewable

- Use one project for one codebase or durable body of work.
- Rename generated scratch projects that become long-lived.
- Keep secrets out of project files where possible; files in the project may be included in workspace backups.
- Preserve Git history and run the project’s own tests before exporting or publishing it.
- Archive a finished task without assuming that the underlying project folder has been deleted.