modelcontextprotocol / modelcontextprotocol/servers
agent frequently hangs indefinitely (indicated by a persistent loading spinner) after a Sequential_Thinkingcall
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Describe the bug
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 agentorclaude code. - Ensure the
Sequential_Thinkingmode is triggered. - Monitor the agent's execution flow until it makes an
mcpcall within itsTHOUGHTprocess. - Observe that after the current
THOUGHTis 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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Sequential_Thinking flow in augment agent or claude code, focusing on the transition after an MCP call when NEXTTHOUGHTNEEDED is true. The issue is resolved when the agent automatically advances to the next thought without requiring a manual stop and continuation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100