Status
Workaround: 8 guides
The upstream issue was closed without a fix (not planned, stale or duplicate). The steps get you unblocked.
- LangGraphWorkaround
Agent repeats the same tool call until it hits the recursion limit
A prebuilt agent keeps calling tools step after step and only stops when GraphRecursionError is raised.
Last checked#loop#tool-calls5 steps → - Hermes AgentWorkaround
Error messages name the symptom, not the cause
You fix what the error says, and it still fails. For example, a 'payment/credit error' when there is simply no API key.
Last checked#error-messages3 steps → - CrewAIWorkaround
Every tool call arrives with empty arguments and fails validation
Each tool call fails with 'Field required ... input_value={}' and the agent repeats until max iterations.
Last checked#tool-calls#schema3 steps → - LangChainWorkaround
JSON output parser returns None instead of raising on bad JSON
A chain returns None for some malformed outputs, and later code fails far from the cause.
Last checked#parsing#error-messages3 steps → - LangChainWorkaround
Parser fails when the model wraps JSON in ```JSON instead of ```json
parse_json_markdown raises on output that is valid JSON inside a code fence.
Last checked#parsing2 steps → - LangGraphWorkaround
Setting recursion_limit to 10000 silently does nothing
with_config({"recursion_limit": 10000}) has no effect on a subgraph or agent.
Last checked#config3 steps → - MCP Python SDKWorkaround
Stateless MCP server logs ERROR every time a client disconnects
Two ERROR records appear whenever a client cancels a request, and alerts fire.
Last checked#error-messages#transport3 steps → - ContinueWorkaround
Tool calls fail because arguments come back as XML-like text
In agent mode, tool calls break with empty arguments or list/index errors when using a self-hosted compatible endpoint.
Last checked#tool-calls#serving3 steps →