Files
openchamber/packages/docs/content/docs/troubleshooting/opencode-connection.mdx
T
Bohdan Triapitsyn 967704a9b9 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

35 lines
1.3 KiB
Plaintext

---
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