docs: add OpenChamber feature docs and translations (#1400)

* 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.
2026-05-24 14:15:55 +03:00
parent bf6043a472
commit 967704a9b9
225 changed files with 7523 additions and 12 deletions
@@ -0,0 +1,34 @@
+---
+title: OpenCode Connection
+description: Fix OpenChamber not connecting to its OpenCode server.
+---
+
+# OpenCode Connection
+
+If OpenChamber loads but never gets past "OpenCode is restarting," or chat won't respond, the server it talks to isn't reachable. Work through these.
+
+## It's stuck on "OpenCode is restarting"
+
+- give it a moment right after launch — this state is normal while the server starts
+- check whether the server is alive with `openchamber status`
+- restart it with `openchamber restart`
+- view startup details with `openchamber logs`
+
+## You're connecting to your own server
+
+If you set OpenChamber to use an existing server, double-check the setup from [OpenCode Server](/opencode-server/):
+
+- `OPENCODE_HOST` must include the port, with no path — for example `http://localhost:4096`
+- set `OPENCODE_SKIP_START=true` so OpenChamber doesn't also start its own
+- if the address is invalid, OpenChamber ignores it and starts its own server instead — look for a `[config]` warning in the logs
+
+## Still failing
+
+- confirm Node.js is version `20` or newer
+- reinstall the latest CLI
+- open `http://localhost:3000` directly before testing any tunnel or remote link
+
+## Related
+
+- [OpenCode Server](/opencode-server/) — how OpenChamber finds and manages the server
+- [Troubleshooting](/troubleshooting/) — other common issues
@@ -0,0 +1,38 @@
+---
+title: Remote Access
+description: Fix tunnels, remote instances, and reaching OpenChamber from another device.
+---
+
+# Remote Access
+
+When you can't reach OpenChamber from your phone or another machine, the fix depends on how you're connecting.
+
+## Check the basics first
+
+- open `http://localhost:3000` on the same computer first — if that fails, it's not a remote problem; see [OpenCode connection](/troubleshooting/opencode-connection/)
+- confirm the server is running with `openchamber status`
+
+## Tunnel link doesn't work
+
+- run `openchamber tunnel status --all`
+- restart the tunnel from the same instance and port
+- regenerate the connect link if the previous one was already used
+
+See [Tunnels](/tunnels/) for the full setup.
+
+## Remote instance won't connect (desktop)
+
+When a [remote instance](/remote-instances/) stalls, OpenChamber names the step that failed:
+
+- **auth** — your SSH or UI password was rejected; re-enter it
+- **install / start** — OpenChamber couldn't set up or start the server on the remote machine; check that machine's requirements
+- **forwarding** — the connection is up but the port isn't reaching you; try a different local port
+
+## Behind your own server
+
+If you put OpenChamber behind a reverse proxy and it loads oddly or won't connect, see [Reverse Proxy](/reverse-proxy/).
+
+## Related
+
+- [Tunnels](/tunnels/) · [Remote Instances](/remote-instances/) · [Reverse Proxy](/reverse-proxy/)
+- [Security](/security/) — protect the UI before exposing it
@@ -0,0 +1,35 @@
+---
+title: Worktrees & Git
+description: Fix common worktree and git problems.
+---
+
+# Worktrees & Git
+
+Issues that come up with [worktree sessions](/worktrees/) and the [git view](/git/), and how to clear them.
+
+## A worktree needs attention
+
+OpenChamber flags a worktree when something's off:
+
+- **folder missing** — the worktree's folder was deleted or moved outside OpenChamber; remove the session and create a fresh worktree
+- **detached or unborn branch** — the worktree isn't on a normal branch; check it out onto one
+- **merge, rebase, or cherry-pick in progress** — an operation was left half-finished; finish or abort it from the git view
+
+## Can't create a worktree
+
+- **branch already exists** — pick a different branch name, or use the existing-branch option
+- **name already in use** — choose a different worktree name
+
+## Commit or PR generation fails
+
+Generating a commit message or PR description runs in your active session, so you need a session open with a working model selected. Open or pick a session and try again.
+
+## SSH or Windows path issues
+
+- make sure the SSH key the repo uses is the one set in your [git identity](/git-identities/)
+- on Windows, git uses Unix-style paths (like `/c/Users/...`) — OpenChamber handles this, but custom SSH key paths should follow the same form
+
+## Related
+
+- [Worktree Sessions](/worktrees/) — how worktrees are created and removed
+- [Git Identities](/git-identities/) — set the right key and identity per repo