# Send a coding task to the cloud

Cloud coding gives a teammate a separate task workspace for changes in a GitHub repository. You describe the outcome, then follow the task's progress, published branch, and any available preview.

## Connect GitHub first

An enabled GitHub connection with write access to the repository is required, including for public repositories. Provide the repository URL and a bounded task with its acceptance checks.

> **Try this**
> In my connected GitHub repository at [repository URL], fix the mobile navigation overlap. Preserve the current styling, verify the affected mobile layout, and open a pull request with a short explanation and the checks performed.

## Know what will be published

A completed cloud coding task publishes collected changes to a remote task branch. The option to open a pull request controls PR creation; it does not turn off task-branch publication.

A queued task is still waiting to launch. When the task finishes, inspect its GitHub link and commit. A local branch name alone does not establish that the changes reached GitHub.

## Review and refine

Use **Open preview** on the task card when the preview is ready. A running task does not always have a usable preview. Send a follow-up instruction to the existing task for corrections, or cancel an active run when its work is no longer needed.

Review the diff and checks before merging or releasing. The task's report should distinguish code changes, tests, publication, and anything still unresolved.