# How-to guides

> Complete a specific Zuse task with verified steps, a success check, and a recovery path.

Canonical URL: https://docs.zuse.sh/how-to



Use these guides when you know the outcome you want. Each one stays focused on a single workflow and tells you how to confirm it worked before you move on.

## Build and ship from the desktop app [#build-and-ship-from-the-desktop-app]

| Goal                                            | Start here                                                                 |
| ----------------------------------------------- | -------------------------------------------------------------------------- |
| Keep concurrent tasks isolated                  | [Run tasks in parallel with worktrees](/how-to/local-parallel-worktrees.md)  |
| Delegate independent work to agents             | [Delegate work across agents safely](/how-to/local-delegate-agents.md)       |
| Give an agent the right evidence                | [Add files and context to a task](/how-to/local-add-context.md)              |
| Verify a running app with an agent              | [Test a local app in the browser](/how-to/local-test-in-browser.md)          |
| Inspect and commit completed work               | [Review and commit local changes](/how-to/local-review-changes.md)           |
| Push, open a pull request, and merge            | [Create and complete a pull request](/how-to/local-complete-pull-request.md) |
| Resume after a setup, provider, or turn failure | [Recover or continue a local task](/how-to/local-recover-task.md)            |
| Set personal and repository behavior            | [Configure Zuse settings](/how-to/local-configure-settings.md)               |
| Connect provider-native tools                   | [Configure MCP servers](/how-to/local-configure-mcp.md)                      |

For a normal feature task, create an isolated checkout, give the agent the required context, verify the running result when applicable, then review and ship the diff. Delegate only when the work has clean ownership boundaries.

## Connect and operate another device [#connect-and-operate-another-device]

| Goal                                      | Start here                                                              |
| ----------------------------------------- | ----------------------------------------------------------------------- |
| Pair a phone on the local network         | [Connect an iPhone to a nearby Mac](/how-to/remote-connect-device.md)     |
| Authorize a browser on the local network  | [Open Zuse in a local browser](/how-to/remote-local-browser.md)           |
| Reach an existing computer away from home | [Reach a computer away from its network](/how-to/remote-hosted-access.md) |
| Run a durable headless environment        | [Operate a Zuse Serve host](/how-to/serve-operate-host.md)                |
| Restore a browser or mobile session       | [Recover a remote connection](/how-to/remote-recover-connection.md)       |

Remote clients control the environment already running on your Mac or Linux computer. They do not copy repositories or move provider credentials onto the phone or browser.

## When you need exact behavior [#when-you-need-exact-behavior]

How-to guides optimize for finishing a task. Use the feature sections and [Reference](/reference.md) when you need exact command options, settings keys, schemas, platform availability, security boundaries, or diagnostic states.