VS Code adapter: rebase onto main + cross-adapter relay e2e - #16
Merged
Conversation
Share JoinClient/RelayServer in packages/client for reuse across hosts. Add packages/vscode with share/join/chat commands and a Session sidebar that speaks the same chorus-relay wire protocol as the OpenCode plugin.
Ship a practical Zed v1 adapter: WASM extension launches a native helper as an MCP context server. Helper speaks Chorus /ws (join, chat, collab.input, status) with CLI + daemon control and integration tests.
Keep the VS Code extension and shared client on this branch; Zed moves to a follow-up PR.
Rebase the VS Code plugin and @chorus/client extraction onto v2.0.0 main, merging network CIDR relay options into the shared client. Restore session access control in the VS Code controller (approval, email gate, pending queue). Add vscode-relay-e2e covering three cloud roles (host vscode, joiner vscode, disallowed joiner) plus VS Code↔terminal host/joiner cross-adapter scenarios. Co-authored-by: Steven Roomberg <sroomberg@users.noreply.github.com>
cursor
Bot
changed the base branch from
cursor/vscode-zed-plugins-19be
to
main
August 31, 2026 11:44
Document relay-first model, VS Code install, adapter e2e scripts, and three-environment test roles. Refresh STATUS, DECISIONS, and vscode README. Co-authored-by: Steven Roomberg <sroomberg@users.noreply.github.com>
3 tasks
Co-authored-by: Steven Roomberg <sroomberg@users.noreply.github.com>
Co-authored-by: Steven Roomberg <sroomberg@users.noreply.github.com>
Update CHANGELOG, plugin, client, vscode, and chorus-relay versions. Release notes cover VS Code adapter, @chorus/client extraction, and cross-adapter e2e. Co-authored-by: Steven Roomberg <sroomberg@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rebases the VS Code extension and
@chorus/clientextraction ontomain(v2.0.0 network lockdown). Version bump: v2.1.0. The relay interaction layer is shared between the OpenCode terminal plugin and the VS Code adapter — UI is secondary; host/joiner protocol behavior is what matters.Changes
@chorus/plugin,chorus-relay,@chorus/client, and VS Code extension versions bumpedRelayServernetwork options into@chorus/client; plugin re-exports from clientbun run test:vscode-relay-e2e(host vscode / joiner vscode / disallowed joiner + terminal cross-adapter)packages/vscode/README.mdGUI walkthrough
Release
After merge, cut the release with:
git tag v2.1.0 && git push origin v2.1.0That triggers the GitHub Release workflow (notes from
CHANGELOG.md).Test plan
cargo test -p chorus-relaybun run test:tsbun run typecheckbun run test:vscode-e2ebun run test:vscode-relay-e2e