feat(core): add debug workspace server#23590
Merged
Conversation
ubenmackin
pushed a commit
to ubenmackin/opencode
that referenced
this pull request
Apr 20, 2026
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
1 participant
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.
debugging a remote workspace is a pain, we should provide an easy environment for simulating one
This does that, it handles running a second opencode server in the background, and provides a plugin to treat it as a remote server. The plugin communicates how to run the server by writing data to file which the server reads, and the server automatically restarts whenever the file is written to (so you can create new workspaces on the fly)
Note that this only supports on fake remote workspace at a time (we just want to deal with one server running). once you create a new debug workspace, all the past ones will be treated as if they are destroyed
Instructions for using this are at the top of the plugin file