Description
While checking #28015, I found a smaller worker communication bug: if a TUI worker RPC method throws, the worker-side message handler rejects and the parent RPC client never receives a result or error. That can leave the request pending and make later TUI/worker communication look broken instead of surfacing the original error.
Plugins
None required.
OpenCode version
Current dev branch.
Steps to reproduce
- Register a worker RPC method that throws.
- Call it through
Rpc.client(...).call(...).
- The listener rejects and the client never receives a controlled error response.
Screenshot and/or share link
No response
Operating System
Linux
Terminal
No response
Description
While checking #28015, I found a smaller worker communication bug: if a TUI worker RPC method throws, the worker-side message handler rejects and the parent RPC client never receives a result or error. That can leave the request pending and make later TUI/worker communication look broken instead of surfacing the original error.
Plugins
None required.
OpenCode version
Current dev branch.
Steps to reproduce
Rpc.client(...).call(...).Screenshot and/or share link
No response
Operating System
Linux
Terminal
No response