Files
openchamber/packages/vscode
Serhii DziupinandSerhii Dziupin 86e6a2ae76 Remove verified dead declarations (#2714)
* chore: remove verified dead declarations

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: narrow unused internal exports

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: remove newly exposed dead helpers

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: remove unused deep-link serializer

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: drop two tests that assert on copies of the code

mainLayoutMobileSidebarMount read MainLayout.tsx and SessionSidebar.tsx as
strings and asserted on source substrings down to exact indentation, so it
failed on formatting rather than behaviour. useProjectSessionSelection.test
reimplemented the hook's visitNodes logic inside the test file and asserted
against that copy, so it could not observe the hook at all.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: repair sync suites that had rotted while unrunnable

No runner executed packages/ui, so these drifted from the source unnoticed:
two imported helpers that are no longer exported, one directory-store stub
predated the session field routeMessage reads, and the WebSocket fake missed
the mandatory url-token mint plus the close event the socket wrapper reads.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: stop the web suite failing on timeouts and a hand-copied mock

The Git suites drive a real git binary, so the 5s default made a valid suite
fail differently per run. The gitApiHttp mock listed ~70 export names by hand
and fell behind the source; it now derives every stub from the real module,
which the added shared-UI aliases make resolvable.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: run every suite from one command and in CI

packages/ui (232 files) and packages/vscode (22) had no test script at all, CI
ran neither, and 9 vscode files could never run because Node cannot resolve
their extensionless TypeScript imports. Three electron files sat outside every
script list, one of them importing vitest, which that package does not depend
on. A runner gives each file its own process, since these suites keep
module-level singletons and fail by load order when sharing one.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* chore: delete a superseded repro harness and a completed plan

The issue-2638 harness needed lsof, overrode process.platform and spawned real
servers, and nothing referenced it; event-stream/rebind.test.js now covers the
same hub-pinned-to-the-old-port behaviour. The pairing v2 plan described relay
and the pairing UI as out of scope, both of which shipped.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* docs: point at the theme tools and record the github barrel invariant

convert-vscode-theme and harmonize-theme were referenced nowhere, so the
theme-authoring reference now names them. The github barrel is loaded through
await import('./index.js') and destructured per route, which no static report
can see; documenting that is what stops the next cleanup from deleting it.

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>

* test: repair merge drift in bridge and route-registry mocks

upstream/main gained upsertProviderConfig on bridge-system-runtime and a
PATCH scheduled-task route after this branch forked. Their test doubles
were never updated to match:
- bridge-system-runtime.test.js: add upsertProviderConfig to the
  opencodeConfig mock so the import resolves.
- sse-routes.test.js: add app.patch to the route registry stub.

---------

Co-authored-by: Serhii Dziupin <makeittech@users.noreply.github.com>
2026-08-13 15:30:54 +03:00
..
2025-12-13 16:34:17 +02:00
2026-08-10 20:57:44 +03:00
2025-12-13 16:34:17 +02:00
2025-12-25 17:57:31 +02:00

OpenChamber VS Code Extension

GitHub stars GitHub release Discord Support the project

OpenCode AI coding agent, right inside your editor. No tab-switching, no context loss.

VS Code Extension

Like the extension? There's also a desktop app and web version with even more features.

What you get

  • Chat beside your code — responsive layout that adapts to narrow and wide panels
  • Agent Manager — run the same prompt across multiple models in parallel, compare results side by side
  • Right-click actions — add context, explain selections, and improve code in-place
  • Click-to-open — file paths in tool output open directly in your editor; edit-style results land in a focused diff view
  • Session editor panel — keep chat sessions open alongside files
  • Theme-aware — adapts to your VS Code light, dark, and high-contrast themes

Plus everything from the shared OpenChamber UI: branchable timeline, smart tool UIs, voice mode, Git workflows, and more.

Commands

Command Description
OpenChamber: Focus Chat Focus the chat panel
OpenChamber: New Session Start a new chat session
OpenChamber: Open Sidebar Open the OpenChamber sidebar
OpenChamber: Open Agent Manager Launch parallel multi-model runs
OpenChamber: Open Session in Editor Open current or new session in an editor tab
OpenChamber: Settings Open extension settings
OpenChamber: Restart API Connection Restart the OpenCode API process
OpenChamber: Show OpenCode Status Debug info for development or bug reports

Right-click menu

Select code in the editor, right-click, and find the OpenChamber submenu:

Action Description
Add to Context Attach selection to your next prompt
Explain Ask the agent to explain the selected code
Improve Code Ask the agent to improve the selection in-place

Configuration

Setting Default Description
openchamber.apiUrl (empty) URL of an external OpenCode API server. Leave empty to auto-start a local instance.
openchamber.opencodeBinary (empty) Absolute path to the opencode CLI binary. Useful when PATH lookup fails. Requires window reload to apply.

Requirements

  • OpenCode CLI installed and available in PATH (or set OPENCODE_BINARY env var)
  • VS Code 1.85+
Development
bun install
bun run vscode:dev

bun run vscode:dev now starts watchers + opens an Extension Development Host automatically. Webview UI changes use Vite HMR automatically.

Optional overrides:

  • OPENCHAMBER_VSCODE_BIN=cursor bun run vscode:dev
  • OPENCHAMBER_VSCODE_DEV_WORKSPACE=/path/to/workspace bun run vscode:dev
  • bun run vscode:dev /path/to/workspace

To package manually:

bun run --cwd packages/vscode build
cd packages/vscode && bunx vsce package --no-dependencies

Install locally: code --install-extension packages/vscode/openchamber-*.vsix

License

MIT