-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Calude will return soon, blank page, empty chat during MCP responses #472
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Constantly happens to me when trying to use specifically the edit_file function. |
Experienced the same |
I get this regularly as well while using my own custom MCP servers. I've verified they work using the MCP Inspector, so I'm not sure what's going on here. The last messages in the log files (mcp.log and mcp-my-server.log) are successful responses. I'm using StreamableHTTP remote servers, but it also happened with SSE servers. Sounds like those above are having the issue with stdio too. At least visually, it happens early on in the tool call, while it's still generating the request that it sends to the MCP server. It only gets 4-10 lines in before it chokes. Hoping to see some clarity here, would love to stick to using the Claude desktop app instead of needing to switch to some other client project. Adding the full error string here for SEO reasons
|
Describe the bug
I do not have a clean repro of this. It happens only during response generation to an MCP server. I normally see this during filesystem because that is what I use the most heavily, but I've seen it in memory and other servers as well. The behavior is that during the response you get the "Claude will return soon" page. Sometimes it is just blank. I see no crash or log messages when this happens. If I use the menu option to reload the page I can get back where I was, but the partial response is not there. If it is a new conversation my prompt is gone as well. It is usually still there in edit mode when it happens during a conversation. If I resubmit that prompt it will happen again. If I rephrase I can often get a complete response and move on.
This sounds a lot like #170 but this is definitely MCP related. It happens during the MCP response. I've never seen this in the web chat interface, but I can't use MCP there so I don't really use it anymore either.
The text was updated successfully, but these errors were encountered: