[BUG] Per-Turn Tool Call Limit Regression Breaks Agentic MCP/SSH Workflows in Claude Desktop
### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? The per-turn tool call limit in Claude Desktop has been significantly reduced without announcement. Sessions that previously ran 60–80+ tool calls autonomously over 45+ minutes now hit "Claude reached its tool-use limit for this turn" after approximately 20 tool calls, requiring a manual "Continue" click to resume. This breaks agentic MCP/SSH workflows where Claude is given a well-specified task and expected to execute autonomously. This is not a rate limit or usage cap issue — it's a per-turn ceiling on tool calls within a single response. I am on the Max plan. Example Session (March 13, 2026) Task: Fix multiple issues in a HubSpot API integration (company name resolution via two-hop engagement→contact→company, future-dated item filtering, email volume caps, activity type filter UI). Claude chained approximately 20+ tool calls (RunRemoteCommand and Used mcp-ssh integration) across: Debugging a toObjectId string/number type mismatch in v4 batch API responses Adding company associations via v4 batch Filtering future-dated meetings/tasks Adjusting per-type fetch limits Adding a type filter dropdown to the Activity tab UI Fixing prop des
Posted by ncb0606 on Mar 13, 2026, 12:04 PM
Tags
Related issues
- This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
- I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
- the new VSCode UI, looks cute, i don't like it.
- I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
- The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
- Add PR-style review comments in Git Diff UI that feed into the active agent thread
Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments
ux (Software)
This is the biggest problem with contracts, there's simply no way to actually say "please always execute this check".
I don't disagree with you on this, I worked my whole life in corporate and haven't worked as a OSS maintainer before, though I will _and ...
the new VSCode UI, looks cute, i don't like it.
I've been working on my own private harness for the past 8 months, and I've been collecting ideas from such repos I've stumbled upon.
The way AI is able to interact with outside resources is pretty impressive, but the quality of code it produces to me is still questionab...
Add PR-style review comments in Git Diff UI that feed into the active agent thread
Thanks for indulging me so far, by the way, I really appreciate this discussion, it's very stimulating.
Migrate GDScript to the GDExtension mechanism and overhaul the implementation
[BUG] Per-Turn Tool Call Limit Regression Breaks Agentic MCP/SSH Workflows in Claude Desktop
### Preflight Checklist - [x] I have searched [existing issues](https://github.com/anthropics/claude-code/issues?q=is%3Aissue%20state%3Aopen%20label%3Abug) and this hasn't been reported yet - [x] This is a single bug report (please file separate reports for different bugs) - [x] I am using the latest version of Claude Code ### What's Wrong? The per-turn tool call limit in Claude Desktop has been significantly reduced without announcement. Sessions that previously ran 60–80+ tool calls autonomously over 45+ minutes now hit "Claude reached its tool-use limit for this turn" after approximately 20 tool calls, requiring a manual "Continue" click to resume. This breaks agentic MCP/SSH workflows where Claude is given a well-specified task and expected to execute autonomously. This is not a rate limit or usage cap issue — it's a per-turn ceiling on tool calls within a single response. I am on the Max plan. Example Session (March 13, 2026) Task: Fix multiple issues in a HubSpot API integration (company name resolution via two-hop engagement→contact→company, future-dated item filtering, email volume caps, activity type filter UI). Claude chained approximately 20+ tool calls (RunRemoteCommand and Used mcp-ssh integration) across: Debugging a toObjectId string/number type mismatch in v4 batch API responses Adding company associations via v4 batch Filtering future-dated meetings/tasks Adjusting per-type fetch limits Adding a type filter dropdown to the Activity tab UI Fixing prop des
Comments (0)
No comments yet. Start the discussion.