Build, verify, ship
Sessions and parallel agents
Separate workstreams, choose where each one runs, and merge when ready.
A session groups a conversation and its branch of work. Use sessions for independent features, experiments, or collaborators working at the same time.
Start separate work
Use /sprint <feature> for a dedicated sprint, /fork <prompt> in the CLI, or the session controls in the web workspace. Additional web sessions require a GitHub connection and available session capacity.
Each session has its own chat context and branch. Hosted sessions can have their own running environment and preview. CLI sessions use separate Git worktrees. Select the session before inspecting its code, messages, or preview.
Where a session runs
A session runs either in the cloud, in the project’s sandbox, or on your laptop through the CLI. Session tabs on the web show a laptop icon for a laptop session, green while the laptop is connected, and the header explains where the session runs.
| You want to | Do this |
|---|---|
| Run a web project on your machine | predev open <project link> in a folder, or the command the header offers |
| Hand a laptop session to the cloud | /cloud in the CLI, or Continue in the cloud on the web |
| Bring a cloud session back to your laptop | /local in the CLI |
A message you type on the web for a laptop session runs on the laptop while it is connected. If the laptop is offline, the web asks whether to continue in the cloud or wait for it.
Work with collaborators
Presence indicators show who is viewing a session. Give parallel tasks clear boundaries and review overlapping files before merging. Separate branches reduce interference during implementation; they can still conflict when integrated.
Merge, promote, or archive
| Action | Effect |
|---|---|
| Merge into Main | Combine the session’s changes with Main through a GitHub pull request; a clean one merges automatically |
| Make this the Main | Use this session as Main and move the main preview address to it |
| Archive session | Move the session to Archived while keeping its record |
| Revive | Restore an archived session when its backing branch is still available |
Merge and Make this the Main ask you to click again to confirm. Making a session the Main and merging its code are different operations. If a merge has conflicts, the agent in Main can resolve them.
A deleted GitHub branch can prevent revival. If needed, start a new session from the current Main. See pull requests and merges.