Skip to content

refactor: remove legacy workspace control plane - #40760

Closed
kitlangton wants to merge 4 commits into
v2from
remove-old-workspaces
Closed

kitlangton wants to merge 4 commits into
v2from
remove-old-workspaces

Conversation

@kitlangton

Copy link
Copy Markdown
Contributor

What

Remove the obsolete workspace-specific control plane from V2.

This removes workspace lifecycle persistence, public workspace events, workspace-scoped request inputs, PTY ticket scoping, and the legacy plugin adapter surface while retaining generic Location.workspaceID and persisted session.workspace_id compatibility where V2 still needs to decode existing data.

How

  • Delete the obsolete core workspace table and public workspace event definitions.
  • Stop projecting or filtering sessions by workspace and clear the compatibility column on new/moved projections.
  • Remove workspace query/header fields from Protocol, Server, CLI, TUI, and generated client requests.
  • Remove workspace scoping from PTY connect tickets.
  • Remove the legacy V1 plugin workspace adapter API.
  • Regenerate the Effect and Promise client surfaces from the V2 Protocol API.

Scope

This branch is based directly on v2. It does not include any commits from dev, and it does not remove unrelated console/account workspaces or generic location compatibility fields.

Testing

  • Pre-push bun turbo typecheck --concurrency=3: 33/33 tasks passed.
  • bun run check:generated in packages/client: passed.
  • bun run test in packages/client: 47 passed.
  • bun run test in packages/server: 15 passed.
  • Focused Core tests: 35 passed.
  • Focused CLI tests: 16 passed.
  • Focused TUI runtime tests: 6 passed.
  • Focused CodeMode OpenAPI tests: 41 passed.
  • Focused Schema and Protocol tests: passed.
  • git diff --check: passed.

@github-actions

github-actions Bot commented Sep 6, 2026

Copy link
Copy Markdown
Contributor

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

  • The PR was created more than 1 month ago
  • The PR had fewer than 2 positive reactions
  • Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant