Islam NoflandBohdan Triapitsyn 21253d7fc2 feat: fork-aware issue/PR listing & OpenCode startup loading indicator (#1061)
* Add design spec: OpenCode readiness loading indicator

* Add implementation plan: OpenCode readiness loading indicator

* feat: add useOpenCodeReadiness hook

* feat: add i18n keys for common.loading

* feat: add loading state to ModelSelector

* feat: add loading state to AgentSelector

* feat: add loading state to ModelControls chat selectors

* update package-lock

* feat(github): add shared fork detection utility

* feat(github): make issue listing fork-aware

* feat(github): make PR listing fork-aware

* feat(types): add sourceRepo to issue/PR summary types

* feat(ui): add source badges to GitHub integration dialog

* feat(ui): add source badges to issue/PR picker dialogs

* feat(github): pass headRemote in PR creation for fork support

* feat(ui): add source→target label in PR tab for fork workflows

* fix(github): allow PR section on base branch when upstream remote exists

* fix(github): show PR section on any branch including main for fork→upstream PRs

* fix(github): allow PullRequestSection to render on base branch when upstream remote exists

* feat(github): auto-detect upstream repo for fork→upstream PR creation

- Add GET /api/github/repo/upstream endpoint to discover fork's upstream
- Fix PullRequestSection canShow to allow PR creation on base branch when repo is a fork
- Add virtual upstream target in remote dropdown (no explicit upstream remote needed)
- Add targetRepo parameter to /api/github/pr/create for direct upstream targeting
- Add repoUpstream() API client method and GitHubRepoUpstreamResult type

* feat(github): auto-detect upstream repo for fork→upstream PR creation

- Add GET /api/github/repo/upstream endpoint to discover fork's upstream
- Fix PullRequestSection canShow to allow PR creation on base branch when repo is a fork
- Add virtual upstream target in remote dropdown (no explicit upstream remote needed)
- Add targetRepo parameter to /api/github/pr/create for direct upstream targeting
- Add repoUpstream() API client method and GitHubRepoUpstreamResult type

* fix: complete fork→upstream PR workflow

- Server: return defaultBranch from /api/github/repo/upstream endpoint
- Server: fix cross-repo head ref construction (compare repos, not remote names)
- Server: filterActiveRemoteBranches checks all remotes, not just origin
- UI: set targetBaseBranch to upstream's default branch when using detected upstream
- UI: include all remote branches in base branch dropdown when using detected upstream
- UI: skip base===head check for cross-repo PRs (same branch name on different repos is valid)
- Types: add defaultBranch to GitHubRepoUpstreamResult

* chore: delete superpowers folder

* feat: add (local)/(remote) labels to PR branch display and adapt Repository button to selected remote

* feat: Repository button adapts to selected remote (upstream vs origin)

* fix: complete fork→upstream PR feature gaps

Server:
- Extend /api/github/repo/upstream to return defaultBranchSha and remoteName
- Reuse headRepo result instead of redundant resolveGitHubRepoFromDirectory call
- Return clear error when headRepo is null (invalid GitHub URL)

UI:
- Add upstream's default branch to availableBaseBranches when using detected upstream
- Use upstream's default branch SHA in git log for generate description (fixes 'No commits found in range main...main')
- Show qualified names (owner/repo · branch) in base branch dropdown when using detected upstream

Types:
- Add defaultBranchSha and remoteName to GitHubRepoUpstreamResult

* fix: move detectedUpstream state before availableBaseBranches to fix temporal dead zone

* fix: fetch upstream branches from GitHub API for base branch dropdown

- Add GET /api/github/repo/branches endpoint to fetch branches via Octokit
- Add repoBranches() to GitHub API client and interface
- Fetch upstream branches on detection and store in upstreamBranches state
- Include upstreamBranches in availableBaseBranches when using detected upstream
- Re-add availableBaseBranches memo and auto-correction effect that were lost
- Remove unnecessary qualified names from dropdown (upstream is already selected)

* fix: restore prStatusKey and statusEntry declarations lost during refactor

* fix: cleanly re-apply all fork→upstream PR UI changes

Restored PullRequestSection.tsx from clean base and re-applied:
- Expand detectedUpstream type with defaultBranch, defaultBranchSha, remoteName
- Add upstreamBranches state and fetch on upstream detection
- Include upstream branches in availableBaseBranches when using detected upstream
- Use upstream default branch SHA in generate description (fixes 'No commits found')
- Adapt Repository button URL to selected remote
- Add (local)/(remote)/(upstream) labels to branch display

* fix: move detectedUpstream/upstreamBranches before availableBaseBranches to fix TDZ

* style: add pill badge styling to upstream repo source labels

* fix: don't cache error PR status responses, allow force-bypass of server cache

* fix: resolve PR status cache bugs, stale directory fallback, and upstream re-detection

* fix: keep collapse button visible when scrolling long user messages

- Collapse button now sticks to top of scrollable user message content instead of scrolling away

* fix: checkbox focus ring blends into sidebar background

* fix: polish fork PR follow-ups

* fix: remove user message collapse artifact

* fix: tighten fork PR internals

* fix: check all remotes for fork PR status

* fix: recover sidebar PR status misses

---------

Signed-off-by: Islam Nofl <islamnofl.official@gmail.com>
Co-authored-by: Bohdan Triapitsyn <artmore@protonmail.com>
2026-04-29 12:03:39 +03:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00
2026-04-25 20:44:35 +03:00
2026-04-28 17:45:58 +03:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00
2026-04-28 17:45:58 +03:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00
2025-12-07 19:32:53 +02:00

OpenChamber

GitHub stars GitHub release Created with OpenCode Discord Support the project

OpenCode, everywhere. Desktop. Browser. Phone.

A rich interface for OpenCode. Review diffs, manage agents, run dev servers, and keep the big picture while your AI codes.

OpenChamber Chat

More screenshots

Tool Output Settings Web Version Diff View VS Code Extension

PWA Chat PWA Diff

Why use OpenChamber?

  • Cross-device continuity: Start in TUI, continue on tablet/phone, return to terminal - same session
  • Remote access: Use OpenCode from anywhere via browser
  • Familiarity: A visual alternative for developers who prefer GUI workflows

Features

Core (all app versions)

  • Branchable chat timeline with /undo, /redo, and one-click forks from earlier turns
  • Smart tool UIs for diffs, file operations, permissions, and long-running task progress
  • Voice mode with speech input and read-aloud responses for hands-free workflows
  • Multi-agent runs from one prompt with isolated worktrees for safe side-by-side comparisons
  • Git workflows in-app: identities, commits, PR creation, checks, and merge actions
  • GitHub-native workflows: start sessions from issues and pull requests with context already attached
  • Plan/Build mode with a dedicated plan view for drafting and iterating implementation steps
  • Inline comment drafts on diffs, files, and plans that can be sent back to the agent
  • Context visibility tools (token/cost breakdowns, raw message inspection, and activity summaries)
  • Integrated terminal with per-directory sessions and stable performance on heavy output
  • Built-in skills catalog and local skill management for reusable automation workflows

Web / PWA

  • Provider-aware tunnel access model with Cloudflare quick, managed-remote, and managed-local modes
  • One-scan onboarding with tunnel QR + password URL helpers
  • Mobile-first experience: optimized chat controls, keyboard-safe layouts, and attachment-friendly UI
  • Background notifications plus reliable cross-tab session activity tracking
  • Built-in self-update + restart flow that keeps your server settings intact

Desktop (macOS)

  • Native macOS menu integration with polished app actions and deep-link handling
  • Multi-window support for parallel project/session workflows
  • "Open In" shortcuts for Finder, Terminal, and your preferred editor
  • Fast switching between local and remote instances
  • Workspace-first startup flow with directory picker and steadier window restore behavior

VS Code Extension

  • Editor-native workflow: open files directly from tool output and keep sessions beside your code
  • Agent Manager for parallel multi-model runs from a single prompt
  • Right-click actions to add context, explain selections, and improve code in-place
  • In-extension settings, responsive layout, and theme mapping that matches your editor
  • Hardened runtime lifecycle and health checks for faster startup and fewer stuck reconnect states

Custom Themes

  • Use it from anywhere - Cloudflare tunnel with QR code onboarding. Scan, connect, code from your couch.
  • Branchable chat timeline - Undo, redo, fork from any turn. Explore different approaches without losing your place.
  • GitHub-native workflows - Start sessions from issues and PRs with context already attached. Review checks, merge - all in-app.
  • Project Actions - Run dev servers, configure SSH port forwarding, open remote URLs locally. Your project commands, one click away.
  • Connect to remote machines - Desktop app connects to remote OpenChamber instances over SSH, with dedicated lifecycle and UX flows.

Quick Start

Prerequisite: OpenCode CLI installed.

Desktop (macOS)

Download from Releases.

VS Code

Install from Marketplace or search "OpenChamber" in Extensions.

CLI (Web + PWA)

requires Node.js 20+

curl -fsSL https://raw.githubusercontent.com/btriapitsyn/openchamber/main/scripts/install.sh | bash
openchamber --ui-password be-creative-here
Advanced CLI options
openchamber --port 8080              # Custom port
openchamber --ui-password secret     # Password-protect UI
openchamber tunnel help              # Tunnel lifecycle commands
openchamber tunnel providers         # Show provider capabilities
openchamber tunnel profile add --provider cloudflare --mode managed-remote --name prod-main --hostname app.example.com --token <token>
openchamber tunnel start --profile prod-main
openchamber tunnel start --provider cloudflare --mode quick --qr
openchamber tunnel start --provider cloudflare --mode managed-local --config ~/.cloudflared/config.yml
openchamber tunnel status --all      # Show tunnel state across instances
openchamber tunnel stop --port 3000  # Stop tunnel only (server stays running)
openchamber logs                     # Follow latest instance logs
OPENCODE_PORT=4096 OPENCODE_SKIP_START=true openchamber                    # Connect to external OpenCode server
OPENCODE_HOST=https://myhost:4096 OPENCODE_SKIP_START=true openchamber  # Connect via custom host/HTTPS
openchamber stop                     # Stop server
openchamber update                   # Update to latest

Connect to an existing OpenCode server:

OPENCODE_PORT=4096 OPENCODE_SKIP_START=true openchamber
OPENCODE_HOST=https://myhost:4096 OPENCODE_SKIP_START=true openchamber

Bind managed OpenCode server to all interfaces (use only on trusted networks):

OPENCHAMBER_OPENCODE_HOSTNAME=0.0.0.0 openchamber --port 3000
systemd service (VPN / LAN access)

Run OpenChamber and OpenCode as separate persistent services — useful when you want to access your dev machine over a VPN (e.g. Tailscale) or LAN without a Cloudflare tunnel.

How it works:

  • OpenCode runs as its own service, binding only to localhost.
  • OpenChamber connects to it via OPENCODE_HOST and --host 0.0.0.0 makes it reachable on your VPN IP.
  • --foreground keeps the CLI process alive so systemd can track and restart it.

~/.config/systemd/user/opencode.service

[Unit]
Description=OpenCode Server

[Service]
Type=simple
ExecStart=opencode serve --port 4095
Environment="PATH=/home/linuxbrew/.linuxbrew/bin:/home/linuxbrew/.linuxbrew/sbin:/home/YOU/.local/bin:/home/YOU/.npm-global/bin:/usr/local/bin:/usr/bin:/bin"
Environment=SSH_AUTH_SOCK=%t/ssh-agent.socket
Restart=on-failure
RestartSec=5

[Install]
WantedBy=default.target

Why set PATH and SSH_AUTH_SOCK? systemd user services start with a minimal environment — no shell profile is sourced. Without an explicit PATH, OpenCode won't find tools installed via Homebrew, npm, or ~/.local/bin. Without SSH_AUTH_SOCK, git operations over SSH (push, pull, clone) will fail because the agent socket isn't inherited. Adjust the PATH to match your own tool installation paths. %t expands to $XDG_RUNTIME_DIR (e.g. /run/user/1000), where most SSH agents write their socket.

~/.config/systemd/user/openchamber.service

[Unit]
Description=OpenChamber Web Server
After=opencode.service

[Service]
Type=simple
ExecStart=openchamber serve --port 3000 --host 0.0.0.0 --ui-password your-password --foreground
Environment="OPENCODE_HOST=http://localhost:4095"
Environment="OPENCODE_SKIP_START=true"
Restart=on-failure
RestartSec=5

[Install]
WantedBy=default.target
systemctl --user daemon-reload
systemctl --user enable --now opencode openchamber

OpenChamber will be reachable at http://<your-vpn-hostname>:3000 from any device on your VPN.

Note: --host 0.0.0.0 is required to listen on all interfaces. The default bind address is 127.0.0.1 (localhost only). Use --host <ip> or OPENCHAMBER_HOST=<ip> to bind to a specific interface instead.

Docker
docker compose up -d

Available at http://localhost:3000.

UI Password:

environment:
  UI_PASSWORD: your_secure_password

Cloudflare Tunnel (optional):

environment:
  OPENCHAMBER_TUNNEL_MODE: quick # quick | managed-remote | managed-local
  OPENCHAMBER_TUNNEL_PROVIDER: cloudflare

For managed-remote mode, provide:

environment:
  OPENCHAMBER_TUNNEL_MODE: managed-remote
  OPENCHAMBER_TUNNEL_HOSTNAME: app.example.com
  OPENCHAMBER_TUNNEL_TOKEN: <token>

For managed-local mode, optionally provide:

environment:
  OPENCHAMBER_TUNNEL_MODE: managed-local
  OPENCHAMBER_TUNNEL_CONFIG: /home/openchamber/.cloudflared/config.yml

Managed-local path note: OPENCHAMBER_TUNNEL_CONFIG must point to a path inside the container user home (/home/openchamber/...). If your Cloudflare config references a credentials JSON file, that file path must also be accessible inside the container (mount with volumes).

Reverse proxy notes

  • For a complete reverse proxy setup guide, see docs/REVERSE_PROXY.md.
  • Website docs source lives at packages/docs/content/docs/reverse-proxy.mdx.

Tunnel behavior notes

  • OpenChamber supports one active tunnel per running instance (port).
  • Starting a tunnel with a different mode/provider on the same instance replaces the current tunnel.
  • Replacing or stopping a tunnel revokes existing connect links and invalidates remote tunnel sessions for that instance.
  • Connect links are one-time tokens; generating a new link revokes the previous unused link.

Data Directory Permission Note: The data/ directory is mounted into the container for persistent storage (config, sessions, SSH keys, workspaces). Before running, ensure the directory exists and has proper permissions:

mkdir -p data/openchamber data/opencode/share data/opencode/config data/ssh
chown -R 1000:1000 data/

SSH/Git: If git push/pull fails, run ssh -T git@github.com in terminal.

Features

Chat & Interaction
  • Branchable chat timeline with /undo, /redo, and one-click forks from any turn
  • Multi-agent runs from one prompt with isolated worktrees for safe side-by-side comparisons
  • Voice mode with speech input and read-aloud responses for hands-free workflows
  • Plan/Build mode with a dedicated plan view for drafting and iterating steps
  • Inline comment drafts on diffs, files, and plans - send feedback back to the agent
  • Shell mode via leading ! with inline output
  • Share messages as images
  • Mermaid diagrams render inline with copy/download actions
  • Smart tool UIs for diffs, file operations, permissions, and task progress
Git & GitHub
  • Full Git sidebar with staging, commits, push/pull, branch management, and rebase/merge flows
  • PR creation with AI-generated descriptions, status checks, and merge actions
  • Start sessions from GitHub issues and pull requests with context baked in
  • Multi-remote push and fork-aware PR creation
  • Worktree integration: isolated sessions per branch, merge back with conflict handling
  • Git identities, gitmoji support, and multi-account GitHub auth
Files, Diff & Terminal
  • Workspace file browser with inline editing, syntax highlighting, and markdown preview
  • Beautiful diff viewer with stacked/inline modes, lazy loading for large changesets
  • Integrated terminal with per-directory sessions, tabbed interface, and stable heavy-output performance
  • Clickable file paths in messages - jump to exact line locations
  • File-type icons across all views for faster visual scanning
Web / PWA
  • Cloudflare tunnel with quick, managed-remote, and managed-local modes, secure one-time connect links, and QR onboarding
  • Mobile-first: optimized chat controls, keyboard-safe layouts, drag-to-reorder projects
  • Background notifications and cross-tab session tracking
  • Self-update + restart flow that keeps your server settings intact
  • Installable as PWA with project-aware naming
Desktop (macOS)
  • Connect to remote OpenChamber instances over SSH with dedicated lifecycle flows
  • Project Actions: run dev servers, SSH port forwarding, open remote URLs locally
  • Multi-window support for parallel project workflows
  • "Open In" shortcuts for Finder, Terminal, and your preferred editor
  • Fast switching between local and remote instances
  • Native macOS menu, deep-link handling, and polished startup
VS Code Extension
  • Editor-native: open files from tool output, keep sessions beside your code
  • Agent Manager for parallel multi-model runs from a single prompt
  • Right-click actions: add context, explain selections, improve code in-place
  • Session editor panel, responsive layout, and theme mapping to your editor
  • Edit-style tool results open directly in focused diff views
Customization
  • 18+ built-in themes with light/dark variants
  • Custom themes via JSON files in ~/.config/openchamber/themes/ - hot reload, no restart
  • Configurable keyboard shortcuts for chat, panels, and services
  • Font size, spacing, corner radius, and layout controls
  • Customizable project icons with upload and automatic favicon discovery
  • Skills catalog and local skill management for reusable automation

Read the Guide: Custom Themes

Context & Productivity
  • Token usage, cost breakdowns, and raw message inspection panel
  • Usage quota tracking across multiple providers with pace/prediction indicators
  • Favorite model cycling via keyboard shortcuts
  • Session folders and subfolders with drag-to-reorder
  • Persistent project notes and todos per project
  • Draft persistence per session with expanded focus mode for longer prompts

Roadmap

Active development. Here's what's being worked on or planned:

  • Windows and Linux desktop apps
  • Mobile app with remote instance and laptop connectivity
  • More built-in tunneling options
  • Kanban board for multi-agent management - keeping the human in the loop and in control
  • Custom OpenCode plugins/tools built-in catalog
  • Linear integration
  • Built-in browser for running dev apps with agent integration

Acknowledgments

Independent project, not affiliated with the OpenCode team.

Special thanks to:

  • OpenCode - For the excellent API and extensible architecture.
  • Flexoki - Beautiful color scheme by Steph Ango.
  • Pierre - Fast, beautiful diff viewer with syntax highlighting.
  • Tauri - Desktop application framework.
  • Ghostty-web - Great implementation of a Ghostty web renderer.
  • David Hill - Who inspired me to release this without overthinking.
  • My wife, who - with zero AI background - sat down with the app for the first time and built the firework celebration that plays on every successful push.
  • Every contributor who shaped this project with their PRs, ideas, and attention to detail.

Contributing

See CONTRIBUTING.md for development setup and guidelines.

Docs source lives in packages/docs.

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%