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
Describe the bug
A clear and concise description of what the bug is.
This bug was first reported to the Claude Code repo where I was told this is an issue with sequentialthinking.
When using Claude Code, after using the sequentialthinking MCP server once, I'm forced to use sequentialthinking in that session going forward unless I clear the context or restart the session.
If I tell Claude Code to stop using sequentialthinking, I can't continue the session.
To Reproduce
Steps to reproduce the behavior:
Using sequentialthinking in Claude Code
Try to move forward without sequentialthinking, it will continue to use it instead of other tools (not super consistent)
Expected behavior
A clear and concise description of what you expected to happen.
After using sequentialthinking, it's not used unless prompted to do so.
Logs
If applicable, add logs to help explain your problem.
From Claude code:
Environment Info
Describe the bug
A clear and concise description of what the bug is.
This bug was first reported to the Claude Code repo where I was told this is an issue with sequentialthinking.
When using Claude Code, after using the sequentialthinking MCP server once, I'm forced to use sequentialthinking in that session going forward unless I clear the context or restart the session.
If I tell Claude Code to stop using sequentialthinking, I can't continue the session.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
After using sequentialthinking, it's not used unless prompted to do so.
Logs
If applicable, add logs to help explain your problem.
From Claude code:
Environment Info
Platform: macos
Terminal: xterm-ghostty
Version: 0.2.27
Feedback ID: b64f05d4-49c0-4d1d-b1bb-76a9ecc32c30
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: