feat(tui): add tui.attach config and --attach flag to connect to existing server #9683
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
This essentially allows you to be able to have a default server set for the TUI so that you don't manually have to run
opencode attach <server>every single time.It also adds an additional option in the /status that allows you to see what server you are currently attached too.
This is what it looks like when it is connected to its own spawned server:

And this is what it looks like when it is connected to a server in the attach json:
tui.attachconfig option to automatically connect TUI to an existing OpenCode server--attach <url>CLI flag for ad-hoc server attachmentUsage
Via config (
opencode.json):{ "tui": { "attach": "http://opencode.local" } }Via CLI flag:
Testing
Tested locally by running a server on
opencode.localand verifying the TUI attaches without spawning a new worker.