Bohdan Triapitsyn 1294a90e52 fix(mobile): keep Android content clear of the navigation bar
Android 15+ enforces edge-to-edge, and Capacitor stops padding the WebView
once it can hand the insets to the page instead — so the app draws under
the gesture/navigation bar. Only the top inset was ever consumed: full
cover surfaces ignored the bottom one entirely, which is why a settings
list ran under the bar, and the chat shell reserved half of it, which is
enough for a home indicator but not for a bar that swallows taps.

Reserve the full inset in the shell on Android and give the surfaces that
own the bottom edge — fullscreen surfaces, the workspace drawer, bottom
sheets — an opt-in class that pads them. The sessions drawer already did
this through its footer, so it stays as it is. Capacitor reports a zero
bottom inset while the keyboard is up, so none of this stacks with the
keyboard inset. iOS deliberately keeps its softer visual inset.

Testing: package type-check and lint; drove the mobile surface in a
browser with the Android platform class and a simulated 48px inset (shell
and surfaces reserve exactly that, drawer footer unchanged, and removing
the class returns every surface to zero).
2026-09-09 17:41:14 +03:00
2025-12-07 19:32:53 +02:00
2026-09-09 17:41:14 +03:00
2026-09-05 21:39:04 +03:00
2026-06-10 12:00:10 +03:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00
2026-08-02 23:23:04 +03:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00
2026-06-16 23:40:00 +03:00
2025-12-07 19:32:53 +02:00

OpenChamber

GitHub stars GitHub release Discord Support the project

Run agent work. Keep control. Ship from anywhere.

OpenChamber is an open-source workspace for running and reviewing AI coding work on desktop, web, VS Code, and mobile.

Start agent work, see what changed, and take it through review and release. Your projects and sessions remain available when you switch devices or step away.

OpenChamber Chat

More screenshots

VS Code Extension

OpenChamber PWA chat OpenChamber PWA diff review

What you can do with OpenChamber

Goals that continue on their own

Give a session a finish line with Session Goals. OpenChamber checks the result after every turn and keeps the agent working until it completes the goal, gets blocked, or reaches the limit you set. It can continue after you close the app.

Compare and combine runs

Use Multi-run to give the same task to up to five models, each in its own session and optionally its own worktree. See what each one actually built, choose the best result, or use Fusion to combine the strongest parts into a new session.

Guided changes walkthroughs

Changes Walkthrough turns a large diff into an AI-guided tour of the change. It groups related edits into steps, puts them in the order the change makes sense, and explains how the pieces fit together.

Inspect a running app

Open your app beside the conversation with Preview. Point at an element to send the agent its screenshot, styles, position, and browser errors. No more trying to explain "this thing here." The desktop app can do the same with any web page in its built-in browser.

GitHub context from issue to pull request

Start a session from a GitHub issue or pull request with its context attached. Send failed checks or review comments back to the agent, then update or merge the pull request from OpenChamber.

Continue on another device

Open the same projects and sessions from Desktop, Web/PWA, VS Code, iOS, or Android. Check progress, answer questions, review changes, and reattach to a running terminal.

Private remote access

Pair a device with a one-time QR code and connect through Private Relay without opening ports or exposing a public server. The connection is end-to-end encrypted and can be revoked at any time. Direct connections, LAN/VPN access, Cloudflare/Ngrok tunnels, and SSH are also supported.

Track work across projects

See which sessions are working, waiting, finished, or failed, along with approvals, scheduled tasks, provider limits, token use, and costs. Organize sessions into folders and keep notes, todos, and reusable project actions nearby.

Schedule recurring work

Run a prompt once, daily, weekly, or on a cron schedule. Scheduled tasks can use Session Goals, so they continue toward an outcome instead of stopping after one response.

Use it where you work

Surface Role
Desktop The complete workspace for macOS, Windows, and Linux, with multiple windows, Mini Chat, remote machines, SSH, and native notifications
Web / PWA Open your workspace in a browser, install it as an app, and stay up to date through background notifications
VS Code Keep sessions beside your code, send selections to the agent, open results in the editor, and compare parallel runs
iOS / Android Review and steer work away from your desk, receive completion alerts, and use the terminal with touch controls
CLI / Server Run OpenChamber on a workstation or server, schedule work, manage remote access, and keep it available after login

Quick start

Desktop for macOS, Windows, and Linux

Download the latest release from GitHub Releases. Desktop bundles the matching OpenCode CLI, so no separate OpenCode installation is required.

Linux releases are available as x86_64 and ARM64 AppImages. Make the downloaded AppImage executable and keep it in a writable location for in-app updates:

chmod +x OpenChamber-*.AppImage
./OpenChamber-*.AppImage

Linux AppImages require FUSE (libfuse.so.2). Without FUSE, run with APPIMAGE_EXTRACT_AND_RUN=1.

VS Code

Install OpenChamber from the Visual Studio Marketplace, or search for "OpenChamber" in Extensions.

CLI for Web and PWA

Requires Node.js 22+. CLI/Web and VS Code use your installed OpenCode CLI.

curl -fsSL https://raw.githubusercontent.com/openchamber/openchamber/main/scripts/install.sh | bash
openchamber --ui-password be-creative-here

Common operations:

openchamber status
openchamber connect-url --qr
openchamber tunnel start --provider cloudflare --mode quick --qr
openchamber startup enable
openchamber logs
openchamber stop
openchamber update

OpenChamber binds to localhost by default. Use --lan only on a trusted network and protect browser access with --ui-password.

Guides

Go deeper with the OpenChamber guides:

For self-hosting details, see the reverse proxy guide. For custom theme authoring, see the custom themes guide.

Why OpenCode?

OpenChamber uses OpenCode to run coding agents. We chose it because it is open source, has a solid API, and is easy to extend.

OpenChamber handles the rest of the workflow. You can decide what to try, keep the agent on track, review the result, connect from another device, and ship the change.

OpenChamber is an independent project and is not affiliated with the OpenCode team.

Contributing

See CONTRIBUTING.md for development setup and contribution guidelines. Documentation authoring guidance lives in packages/docs.

Acknowledgments

Special thanks to:

  • OpenCode for the API and open-source architecture OpenChamber builds on
  • Pierre for the diff viewer and syntax highlighting
  • The T3 Code team for their browser adapter for libghostty-vt, which our terminal is built on
  • Yulia Ivashko, who built the firework celebration that plays on every successful push
  • Everyone who contributed code, reported bugs, or shared ideas

License

MIT

S
Description
No description provided
Readme MIT
82 MiB
Languages
TypeScript 74.8%
JavaScript 19.8%
MDX 4.7%
CSS 0.4%
HTML 0.1%
Other 0.1%