OpenWork Setup and First Run
1. What installation actually gives you​
The README points to:
- desktop downloads,
- GitHub releases,
- source installation,
- and an orchestrator CLI for non-desktop hosting.
That already tells you OpenWork is more than a single local app.
2. Host mode vs client mode​
| Path | Best when |
|---|---|
| Host mode | You want OpenWork to run the local stack for you |
| Client mode | You want to connect to an existing OpenCode server |
This distinction is one of the most important onboarding concepts in the product.
3. What a successful first run looks like​
A good first run should prove:
- the desktop app launches,
- OpenCode is reachable,
- one session can be created,
- permission requests are understandable,
- one timeline or todo plan appears in the UI.
4. Source-build prerequisites are significant​
For source development, the README calls out:
- Node and
pnpm, - Bun,
- Rust and Tauri,
- OpenCode on
PATH.
That is a good sign that the desktop product is a real engineering stack, not only a thin wrapper.
5. Practical first-run advice​
Start in host mode on a low-risk local workspace before you add remote workers or shared server connectivity.