Jay GuptaandBohdan Triapitsyn 46426e8495 feat(chat): /btw — side questions in a temporary forked session (#2796)
* feat(chat): /btw command — side questions in a temporary forked session

/btw <question> forks the current session (full context inheritance) and
opens a compact peek panel docked above the composer. The composer itself
becomes the btw input while the panel is open: sends route to the fork,
the placeholder and a mode chip reflect the target, and the stop button
aborts the fork's turn. Closing the panel (or the chip's ✕) destroys the
fork, leaving the main conversation untouched.

The panel shows only the fork's own tail (messages at/after the fork
creation time) and live permission/question cards scoped to the fork.

- chat/btw/BtwPanel: peek sheet (desktop + mobile), fork-tail view,
  auto-close on disappearance, Esc to close
- lib/btw: startBtwSession (fork + rename + routed send), closeBtwPanel
  (close = destroy), filterBtwTailMessages
- ChatInput: btw-mode send routing via SendMessageOptions.sessionId,
  btw-aware activity (stop/abort), placeholder + mode chip
- useSessionActivity: exported for per-session activity reads
- i18n: btw keys across all 11 locales

* fix(chat): keep btw sends isolated

* refactor(chat): rework /btw into a metadata-scoped peek panel

- Link the active btw fork through the parent session's metadata
  (openchamber.btwSessionID) so the panel exists only in the session that
  invoked /btw, follows parent navigation, and survives reloads; the fork
  carries a kind:'btw' marker with its originalSessionID.
- Replace the wall-clock history boundary with the id of the newest cloned
  message (server-generated ascending ids), stored in fork metadata.
- Derive panel identity in useBtwPanelState; useBtwStore shrinks to
  transient per-parent UI state (collapsed/creating/destroying).
- Panel UX: dropdown-style glass surface, chat ScrollShadow, single
  title+chevron collapse toggle, muted header controls, promote action
  (keep as a full session and navigate to it), Esc collapses instead of
  destroying, reserved Working indicator row, streaming auto-follow via
  ResizeObserver keyed on content readiness.
- Add a 'peek' chat surface mode that suppresses per-message controls and
  turn footers inside the panel; user bubbles keep a small gap below.
- Hide btw forks from the sidebar, session switcher, and command palette
  until promoted; mark the fork before inserting it into local stores.
- Delete/archive lifecycle: removing the fork unlinks the parent; removing
  the parent also removes its temporary fork.
- patchSessionMetadata now mirrors updated sessions into live stores.
- Localize new strings across all 12 dictionaries; add unit tests for
  metadata helpers, the btw flow, and the UI store.

* fix(chat): clamp the btw panel below the app header when the keyboard is open

Reuse useMobileAutocompleteMaxHeight (the composer autocomplete precedent)
on the panel's scroll body, reserving the panel header and bottom spacer
height, so the sheet adapts to the visual viewport instead of riding under
the app header on mobile.

* fix(lint): drop unused destructured bindings in sessionBtwMetadata

CI eslint has no underscore ignore pattern; strip metadata keys with typed
copies and delete instead of discard-destructuring.

---------

Co-authored-by: Bohdan Triapitsyn <artmore@protonmail.com>
2026-08-23 00:40:06 +03:00
2025-12-07 19:32:53 +02: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-08-03 00:32:02 +03: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, supervising, and reviewing AI coding work across desktop, browser, editor, and mobile.

OpenChamber gives you one place to direct agent work, understand the changes, and move them toward release. Your projects stay 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 the goal is complete, blocked, or reaches the limit you set — even 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 and send the agent its screenshot, styles, position, and browser errors — all the context behind “this thing here.” Desktop brings the same workflow to any web page through 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 — 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 — 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 power its coding agents. We chose it because we believe it provides the best open-source agentic coding experience today: capable, extensible, and open by design.

Around that foundation, OpenChamber brings together the work that happens before, during, and after an agent run — deciding what to try, keeping it on track, reviewing the result, connecting from anywhere, and getting the change shipped.

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 its excellent API and extensible open-source architecture
  • Pierre for its fast diff viewer and syntax highlighting
  • Ghostty-web for its Ghostty web renderer
  • Yulia Ivashko, who built the firework celebration that plays on every successful push
  • Every contributor who shaped OpenChamber with code, ideas, and attention to detail

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%