Hey, I see this is a follow-up to your previous report. The infinite loop is fixed, but the main issue has shifted. Now any MCP output over 100,000 characters becomes a dead end because the built-in Read File can’t handle it, and external MCP tools get routed through the same temp-file pipeline.
I’ll pass this to the team as a feature request: configurable temp-file behavior and removing the Read File limit. I don’t have an ETA yet, but your detailed report really helps us prioritize.
For now, the most practical workaround is to filter inside your MCP tool before returning the result. For example, for a directory tree, filter out REFERENCE_001 directories on the server side instead of returning the full 112,000-character tree. It’s not ideal since it pushes work onto your tools, but it fully avoids the 100,000-character cap.
Let me know if you have any questions.