* docs: add OpenChamber feature docs and translations Add 30 new docs pages covering OpenChamber-specific workflows and setup: OpenCode server, providers/models/agents, MCP, skills, commands & snippets, usage, projects, context, notes/todos/plans, scheduled tasks, project actions, preview, worktrees, multi-run, git & GitHub, magic prompts, git identities, mobile/PWA, security, notifications, voice, project icons, remote instances, desktop browser, updates, and three troubleshooting pages. Rebuild sidebar into eight task-oriented sections and translate every new page into all six supported locales (uk, zh-cn, es, pt-br, ko, pl). * docs: surface new sections on homepage and cross-link tunnels Add an Explore block to the docs homepage (all seven locales) linking to the new section anchors, and cross-link the Tunnels page to Security and PWA & Mobile.
35 lines
1.3 KiB
Plaintext
35 lines
1.3 KiB
Plaintext
---
|
|
title: Multi-run
|
|
description: Run the same prompt across several models or sessions at once.
|
|
---
|
|
|
|
# Multi-run
|
|
|
|
Multi-run launches several sessions from one form — handy for trying the same task with different models and comparing the results. Open it from the button at the top of the session sidebar.
|
|
|
|
## Start a multi-run
|
|
|
|
1. Open the multi-run launcher.
|
|
2. Pick the project and name the run group.
|
|
3. Write the prompt and pick the models to run it with (up to five per group).
|
|
4. Choose whether to **isolate runs**.
|
|
5. Launch.
|
|
|
|
Each model gets its own session, and they all start with your prompt.
|
|
|
|
## Isolated runs
|
|
|
|
Turn on **isolate runs** to give every run its own [worktree](/worktrees/) and branch, so they never touch the same files. This needs a git repo — it's turned off automatically for folders that aren't one. Pick the branch the runs start from.
|
|
|
|
With isolation off, every run is a plain session in the project folder.
|
|
|
|
## Comparing results
|
|
|
|
Each run is a normal session you can open, read, and keep or discard. If you started runs to compare approaches, review them side by side and carry the best one forward.
|
|
|
|
If a single run fails to start, the others still launch — you'll just see fewer sessions than you asked for.
|
|
|
|
## Related
|
|
|
|
- [Worktree Sessions](/worktrees/) — how isolation works under the hood
|