You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
agent frequently hangs indefinitely (indicated by a persistent loading spinner) after a Sequential_Thinkingcall #2762
When using Sequential_Thinking mode with either the augment agent or claude code, the agent frequently hangs indefinitely (indicated by a persistent loading spinner) after an mcp call. It fails to automatically proceed to the next thought or action, causing the entire task to stall.
To Reproduce
Steps to reproduce the behavior:
Start a task that requires multi-step reasoning using either augment agent or claude code.
Ensure the Sequential_Thinking mode is triggered.
Monitor the agent's execution flow until it makes an mcp call within its THOUGHT process.
Observe that after the current THOUGHT is complete, the agent gets stuck in a loading state and does not advance to the next step.
Workaround:
The user must manually stop the generation and then send a new message (e.g., "continue" or "go on") to prompt the agent to resume the task. However, the issue may recur in subsequent steps.
Expected behavior
Within a Sequential_Thinking flow, after completing a THOUGHT step that includes an mcp call, the agent should seamlessly and automatically proceed to the next THOUGHT until the task is complete, without requiring any manual intervention.
Logs
While detailed text logs are not available, the attached screenshot illustrates the point of failure. As shown, the agent has completed the 7th thought (THOUGHTNUMBER: 7) and recognizes that a next step is required (NEXTTHOUGHTNEEDED: true), but it fails to automatically advance to the 8th thought.
// State similar to the one in the screenshot
THOUGHT
... (mcp call and reasoning) ...
NEXTTHOUGHTNEEDED
true
THOUGHTNUMBER
7
TOTALTHOUGHTS
8
// <<< Agent hangs here and does not proceed to THOUGHT 8
Additional context
This issue occurs frequently and severely impacts the continuity of automated workflows for complex tasks. The manual workaround is inefficient and disrupts the user experience.
Could you share more info on what app or framework and model is being used here when you see this issue? This seems like behavior that is related to the client and/or model more than the server implementation.
Thank you for reporting this, and apologies for the long wait for a response.
Since this was filed, the reference servers have been rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers). Each server now runs on v2 of its SDK, and the behavior described here has either been fixed or no longer exists in the same form. The agent stalling between thoughts is client or model behavior; the server returns its result for each call and no server defect has been identified.
This is not a judgment on whether the problem was real; it's a consequence of the code it describes having been replaced. This is happening as part of the backlog triage in #4875.
If this still happens on the v2 release, we'd genuinely like to know. Please open a fresh issue with the version you're running and steps to reproduce, and we'll look at it. Note that this repository accepts contributions as issues rather than pull requests; see CONTRIBUTING.md.
Activity
olaservo commentedon Oct 19, 2025
Could you share more info on what app or framework and model is being used here when you see this issue? This seems like behavior that is related to the client and/or model more than the server implementation.
cliffhall commentedon Oct 19, 2026
Closing: superseded by the v2 release.
Thank you for reporting this, and apologies for the long wait for a response.
Since this was filed, the reference servers have been rebuilt for the 2026-07-28 MCP specification (#4857) and released as v2 (2.0.0 on npm for the TypeScript servers, 2026.10.19 on PyPI for the Python servers). Each server now runs on v2 of its SDK, and the behavior described here has either been fixed or no longer exists in the same form. The agent stalling between thoughts is client or model behavior; the server returns its result for each call and no server defect has been identified.
This is not a judgment on whether the problem was real; it's a consequence of the code it describes having been replaced. This is happening as part of the backlog triage in #4875.
If this still happens on the v2 release, we'd genuinely like to know. Please open a fresh issue with the version you're running and steps to reproduce, and we'll look at it. Note that this repository accepts contributions as issues rather than pull requests; see
CONTRIBUTING.md.Thanks for taking the time to report it.