failed to send message: POST #1726

Closed
opened 2026-02-16 17:32:21 -05:00 by yindo · 7 comments
Owner

Originally created by @Overload119 on GitHub (Sep 15, 2025).

Originally assigned to: @thdxr on GitHub.

failed to send message: POST
"http://127.0.0.1:50567/session/ses_6b01d489effeJdVmM34PLytOet/message": 400 Bad Request
{"name": "UnknownError", "data": {"message" : "MC
PClientError: Attempted to send a request
from a closed client"}}

From OpenCode in Cursor.

Opencode version: 0.9.1

Originally created by @Overload119 on GitHub (Sep 15, 2025). Originally assigned to: @thdxr on GitHub. ``` failed to send message: POST "http://127.0.0.1:50567/session/ses_6b01d489effeJdVmM34PLytOet/message": 400 Bad Request {"name": "UnknownError", "data": {"message" : "MC PClientError: Attempted to send a request from a closed client"}} ``` From OpenCode in Cursor. Opencode version: 0.9.1
yindo closed this issue 2026-02-16 17:32:22 -05:00
Author
Owner

@Overload119 commented on GitHub (Sep 15, 2025):

This happens on the second message.

@Overload119 commented on GitHub (Sep 15, 2025): This happens on the second message.
Author
Owner

@github-actions[bot] commented on GitHub (Sep 15, 2025):

This issue might be a duplicate of existing issues. Please check:

  • #1878: Both issues report the same MCPClientError about attempting to send a request from a closed client. The error patterns are identical.

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Sep 15, 2025): This issue might be a duplicate of existing issues. Please check: - #1878: Both issues report the same MCPClientError about attempting to send a request from a closed client. The error patterns are identical. Feel free to ignore if none of these address your specific case.
Author
Owner

@rekram1-node commented on GitHub (Sep 16, 2025):

This happens on every second message or are you saying this happened on a second message

@rekram1-node commented on GitHub (Sep 16, 2025): This happens on every second message or are you saying this happened on a second message
Author
Owner

@Overload119 commented on GitHub (Sep 16, 2025):

It happens on the second message; first one seems to go through. Everything after the first will give this error.

@Overload119 commented on GitHub (Sep 16, 2025): It happens on the second message; first one seems to go through. Everything after the first will give this error.
Author
Owner

@rekram1-node commented on GitHub (Sep 16, 2025):

Didn't notice this was MCP specific at first whoops, which MCP server are you trying to use? This may not be opencode issue

@rekram1-node commented on GitHub (Sep 16, 2025): Didn't notice this was MCP specific at first whoops, which MCP server are you trying to use? This may not be opencode issue
Author
Owner

@rekram1-node commented on GitHub (Sep 16, 2025):

Isn't this the same as https://github.com/sst/opencode/issues/1878?

@rekram1-node commented on GitHub (Sep 16, 2025): Isn't this the same as https://github.com/sst/opencode/issues/1878?
Author
Owner

@rekram1-node commented on GitHub (Dec 27, 2025):

[automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!

@rekram1-node commented on GitHub (Dec 27, 2025): [automated] Closing due to 90+ days of inactivity. Feel free to reopen if you still need this!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#1726