Bohdan Triapitsyn
ca33c6ae57
Add a Voice & Style section to the docs authoring guide, then bring every docs page in line with it: lead with the task, add success signals to procedures, explain jargon on first use, keep bullet casing consistent, and link out to Troubleshooting where steps can fail. Applied across English source and all localized versions (uk, zh-cn, es, pt-br, ko, pl).
27 lines
911 B
Plaintext
27 lines
911 B
Plaintext
---
|
|
title: Quickstart
|
|
description: Start OpenChamber quickly and pick the right app for the task.
|
|
---
|
|
|
|
# Quickstart
|
|
|
|
## Fastest path
|
|
|
|
1. Install [OpenCode](https://opencode.ai).
|
|
2. Install the OpenChamber CLI (see [Install](/install/) for the one-line command).
|
|
3. Run `openchamber --ui-password be-creative-here`.
|
|
4. Open the URL the CLI prints (usually `http://localhost:3000`).
|
|
5. To use it from your phone, start a [tunnel](/tunnels/) and scan the QR code.
|
|
|
|
You should see the OpenChamber session list in your browser. If it loads, you're up and running.
|
|
|
|
Use a strong UI password, especially if you plan to open the instance to the internet.
|
|
|
|
If the page doesn't load, check [Troubleshooting](/troubleshooting/).
|
|
|
|
## Which app should I use?
|
|
|
|
- use **desktop** for day-to-day work on macOS
|
|
- use **web** for remote access and reviewing from your phone
|
|
- use **VS Code** for sessions right next to your code
|