In ZeroTwo this choice sits in the Code tab of the chat | work | code | design strip. Before the first message of a Code task, the environment pill in the composer footer opens a Continue in menu with three options:
- Local: edit your project folder directly (desktop only).
- New local worktree: work in an isolated Git checkout of the project (desktop only; see Worktrees).
- Cloud: run in a sandbox on ZeroTwo's servers from a published environment (see Cloud environments).
The web app has no local option, so it offers only Cloud. On desktop, Cloud is chosen per task and does not carry over to the next new one. A Work task has a smaller picker with Work locally and Cloud, shown before you choose a project.
Using a cloud environment
Cloud needs a published environment of your own, and the repository must have a Git remote (on the web, a GitHub connection). Once Cloud is selected, the Choose environment pill lists your published environments. Pick one, or use Create environment in that menu, or go to Settings > Code Cloud. ZeroTwo runs a setup thread to work out and test the configuration before you publish it. Environments are private to you.
Isolation
A task keeps the environment it started in; the other options are disabled with a note that the task has a saved environment, so start a new task to use a different one. Edits inside a task never change the environment itself, so republish the environment to change how future tasks start. Your computer's files, processes and browser sessions are not available inside a cloud sandbox. A desktop task can later move between a local checkout and a worktree, or to another connected computer, with Move task to worktree, Move task to local checkout and Move to in the pill's menu.