One Request, Two Streams: Debugging a 45-Second Deadlock in MCP's Streamable HTTP
Article summary
Quick briefing — cleaned from the original RSS feed
A tool call freezes for exactly 45 seconds, then fails. The user gets a permission popup 45 seconds too late, answers it, and the answer goes nowhere. Nothing crashed and no error was logged on the way in. That is the bug report that landed in mcp-go#932 a few days ago, observed with one Codex Desktop setup against a server built on mcp-go, a widely used Go implementation of the Model Context Protocol. I maintain a couple of MCP-adjacent packages and had two transport PRs open on mcp-go…
1Key Takeaways
- A tool call freezes for exactly 45 seconds, then fails.
- The user gets a permission popup 45 seconds too late, answers it, and the answer goes nowhere.
- Nothing crashed and no error was logged on the way in.
- That is the bug report that landed in mcp-go#932 a few days ago, observed with one Codex Desktop setup against a server built on mcp-go, a widely used Go implementation of the Model Context Protocol.
2AIWedia Score
8.7/10
High relevance — worth your attention today
Based on source trust, recency, category impact, and story depth.
3Why it matters
Coding AI shifts how fast software ships and how much human review each change needs. DEV — AI reports that a tool call freezes for exactly 45 seconds, then fails.
Explore related
Browse toolsCoding AI news
Explore curated coding ai tools on AIWedia — compare, rank, and launch from our directory.
Full story on DEV — AI
Read full articleHeadlines aggregated via RSS for discovery on AIWedia. Original content © DEV — AI. We link to the source and do not republish full articles.