# Starting a web task

A web task starts from the same outcome-first composer as Desktop, but any filesystem or command work runs inside Foxora Cloud.

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

## Start with the controls that affect the run

1. Open [app.foxora.ai](https://app.foxora.ai/) and choose **New Task**.
2. Confirm the account and credit balance shown in the workspace.
3. Open the autonomy pill below the composer:
   - Use **Ask Permissions** when you want each mutating step reviewed.
   - Use **Accept Edits** when routine file edits may proceed but riskier commands should remain gated.
   - Use **Auto mode** for a bounded, recoverable cloud task.
   - Reserve **Bypass Permissions** for an isolated project whose contents and external access are understood.
4. Open the crew picker and choose Vixen, Zenko, or Kyubi Crew according to the available plan and required depth.
5. Describe the outcome, constraints, and evidence required to call it complete.
6. Attach only the files needed for this task, then send.

## Write a request the workspace can verify

Prefer a request such as:

> Build a small responsive product-status page in this cloud project. Keep dependencies minimal, run the build, and show me the final page plus the exact verification result.

This gives Foxora an output, a scope, and a test. Avoid requests such as “make something nice,” which provide no stable completion signal.

## Understand the generated project

If no project is attached, Foxora gives the task its own scratch project folder. File tools, shell commands, the Files tree, and project download resolve to that same folder so generated work does not drift into a shared workspace root.

The project appears in **foxora → Projects** after the task has a cloud project to show. Give it a useful name once the experiment becomes durable work.

## Follow the task

- Use **Focused** transcript view for the main decisions and results.
- Use **Verbose** when diagnosing tool arguments, command output, or a failed step.
- Open **Runs** to see background work; closing the panel only closes the view.
- Interrupt the task if it targets the wrong project, account, or external destination.

The task is complete only after the real artifact, file, command result, preview, or external destination matches the acceptance criteria.