Skip to content
OpenChamber

OpenCode Server

OpenChamber runs on top of an OpenCode server. By default it starts one for you, so you don’t have to do anything. You only need this page if you want to point OpenChamber at a server you already run, or manage the one it starts.

How OpenChamber finds a server

When OpenChamber starts, it looks for a server in this order:

  1. reuse a server it already started
  2. connect to an external one if you told it to (see below)
  3. auto-detect a server on the default port (4096)
  4. otherwise, start and manage its own

If nothing is configured, step 4 happens automatically and you’re up and running.

Connect to a server you already run

Set these before starting OpenChamber:

Terminal window
OPENCODE_HOST=http://localhost:4096 OPENCODE_SKIP_START=true openchamber
  • OPENCODE_HOST — the full address of your OpenCode server, including the port (a value like http://localhost:4096). It must not have a path at the end.
  • OPENCODE_SKIP_START=true — tells OpenChamber not to start its own server.

If you only need to change the port, set OPENCODE_PORT instead of OPENCODE_HOST.

If OPENCODE_HOST is missing its port or has a path, OpenChamber ignores it and falls back to starting its own server. Watch the startup logs for a [config] warning if a connection you expected didn’t happen.

Manage the server from the CLI

Terminal window
openchamber status
openchamber logs
openchamber restart
openchamber stop

openchamber on its own starts the server in the background. Add --foreground to keep it attached to your terminal.

Start OpenChamber at login

Use startup enable to install a native user service. OpenChamber uses launchd on macOS, systemd --user on Linux, and Task Scheduler on Windows.

Terminal window
openchamber startup enable
openchamber startup status
openchamber startup disable

To protect the UI, set the password when enabling the service:

Terminal window
OPENCHAMBER_UI_PASSWORD='secret' openchamber startup enable

startup enable snapshots your current environment into the service so it behaves more like starting openchamber from the same shell. This keeps provider tokens, PATH, SSH agent settings, and other CLI auth/config variables available. Use --no-env-snapshot if you want a minimal service environment.

You can still manage tunnels independently for that running service:

Terminal window
openchamber tunnel start --port 3000
openchamber tunnel stop --port 3000

Stopping the tunnel does not restart the service or the app.

”OpenCode is restarting”

While the server is starting or restarting, OpenChamber shows an “OpenCode is restarting” state and pauses requests until it’s ready. This is normal right after launch or a restart. If it never clears, see OpenCode connection.