CRITICAL: "Interrupted by user" immediately on ANY input - macOS 15.6.1 - Makes Claude Code 100% unusable
Resolved 💬 17 comments Opened Sep 7, 2025 by danielmstoffel Closed Sep 7, 2025
💡 Likely answer: A maintainer (ollie-anthropic, collaborator)
responded on this thread — see the highlighted reply below.
Preflight Checklist
- [x] I have searched existing issues 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?
Claude Code immediately shows "Interrupted by user" the instant ANY input is entered, before any processing occurs. This happens with:
- Simple commands like "test" or "help"
- The /help command
- Even just pressing Enter with no text
- Both with and without --dangerously-skip-permissions flag
The interruption occurs within milliseconds, making Claude Code completely unusable.
What Should Happen?
Claude Code should:
- Accept input normally
- Process commands
- Execute tasks without immediate interruption
- At minimum, built-in commands like /help should work
Error Messages/Logs
╭───────────────────────────────────────────────────╮
│ ✻ Welcome to Claude Code! │
│ │
│ /help for help, /status for your current setup │
│ │
│ cwd: /Users/daniel │
╰───────────────────────────────────────────────────╯
test
⎿ Interrupted by user
╭─────────────────────────────────────────────────╮
│ > │
╰─────────────────────────────────────────────────╯
⏵⏵ bypass permissions on (shift+tab to cycle)
Steps to Reproduce
- Run
claudeorclaude --dangerously-skip-permissions - Type ANY input (even single character like "a")
- Press Enter
- Immediately see "Interrupted by user"
- Happens 100% of the time, instantly
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
N/A
Claude Code Version
Cannot run claude --version due to the bug Installation: Native installer (curl -fsSL https://claude.ai/install.sh | bash) Binary location: ~/.local/bin/claude
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
Comprehensive Troubleshooting Already Attempted:
- Complete reinstall via npm (with sudo) - FAILED
- Complete removal and reinstall via native installer - FAILED
- Removed all configuration:
rm -rf ~/.claude ~/.config/claude-code- FAILED - Tested in clean bash shell
bash --noprofile --norc- FAILED - Killed ALL Node.js processes - FAILED
- Disabled/removed ALL LaunchAgents:
- com.claude.autohealer.plist
- com.claude.aiassistant.plist
- com.claude.automonitor.plist
- com.pavisus.daemon.plist
- org.claude.pandoc-mcp.plist
All moved to ~/Library/LaunchAgents/DISABLED/
- Removed interfering scripts:
- ~/.claude/auto-healer.js (deleted)
- ~/Pavisus/automation/pavisus-daemon.js (disabled)
- Verified terminal settings:
stty -a | grep intrshows normalintr = ^C - Tested in different directories (/tmp, ~/, project dirs) - ALL FAIL
- No keyboard remapping tools active
- Fresh terminal sessions after system restart - FAILED
System Diagnostics:
- No Claude-related processes running after cleanup
- No automation scripts active
- LaunchAgents confirmed unloaded via
launchctl list - Other interactive programs work fine (python3, node, bash read)
Critical Notes:
- Welcome message and trust dialog display normally
- Only input handling is broken
- Interruption happens before ANY processing
- This is NOT an authentication, permission, or shell configuration issue
- Makes Claude Code 100% unusable for any purpose
Impact:
Complete work stoppage on critical projects. No workaround found despite extensive troubleshooting.
17 Comments
Additional Technical Details for Issue #7261
Version Information (successfully retrieved):
Complete Process Cleanup Performed:
Confirmed Clean State:
ps aux | grep claudereturns nothinglaunchctl list | grep claudeshows no active agentsAdditional Testing Performed:
claudeandclaude --dangerously-skip-permissionsTiming Characteristics:
What This Is NOT:
Suspected Root Cause:
This appears to be a signal handling or input stream issue specific to macOS 15.6.1 (Sequoia) on Apple Silicon, possibly related to:
Impact:
This makes Claude Code 100% non-functional. I cannot execute any command, not even
/helpor/exit. This is blocking critical business operations.Available for Testing:
I'm immediately available to:
Working with Anthropic support for 2+ hours exhausted all standard troubleshooting steps. This requires engineering investigation.
Please let me know if you need any specific diagnostic output or system information.
Same:
<img width="1102" height="430" alt="Image" src="https://github.com/user-attachments/assets/053de9b0-68f2-49f8-bb77-70a75c535020" />
FWIW, this also happened to me today. Same symptom, no amount of reinstalling etc. made it any better.
However, I ended up trying to remove MCP servers from my project MCP file (.mcp.json), and after removing a particular one, CC worked again (after exiting CC and starting a new session).
I have been using this exact MCP setup for months without issues, so it's odd. But I tried this because a "/doctor" showed me that I had a lot of MCP tools (over 50k tokens worth). However, removing other MCP servers that brought me well below that threshold didn't help - only removing that single MCP server made a difference (Unity-MCP). I don't think that MCP server is to blame though, since I've been using it daily in CC for months without any problems.
I'm suspecting that I was running an MCP tool from that MCP server right before my CC ended up in this broken state, and then interrupted that tool call (pressing "esc") - somehow causing corrupted state somewhere I haven't been able to clean up by deleting the ~/.claude.json file or the ~/.claude folder and uninstalling CC.
Note: I'm running CC in WSL2 (default Ubuntu distro) on Windows 11.
same issue on macOS 15.5 . Also can confirm that removing the MCP servers recover Claude functionalities.
@ebbe-brandstrup
Yes, it related with the mcp parameters definition. For example: one of my mcp tool define the parameters with complex schema like:
check: https://github.com/tjx666/vscode-mcp/commit/c7ae01f2d432ce4298227eb8cce23b4a9cb96987#diff-e46bb510c06569a4274304e8626df23eb9b19475331dcccbeb62412ac6136e18
I ran into the same issue today with new MCP server setup (using the import command from Claude Desktop to Claude Code). Will uninstall some now and hope this fixes the "Interrupted by user" issue.
I suspect it is directly related to the large context size (call /doctor):
Context Usage Warnings└ ⚠ Large MCP tools context (~146.656 tokens > 25.000)
└ MCP servers:
└ github: 90 tools (~45.641 tokens)
└ mcp-atlassian: 42 tools (~28.764 tokens)
└ atlassian: 24 tools (~16.945 tokens)
└ billing-cost-management-mcp-server: 13 tools (~15.104 tokens)
└ memory: 28 tools (~13.636 tokens)
└ (6 more servers)
PS: Removing a couple and the duplicate "atlassian" and "map-atlassian" MCP servers did the job - I can work again.
PPS: Untill it did not - two prompts later, same issue. Will follow up once I know more.
Update: Works again without any further changes. Hard to reproduce.
✅ SOLVED - Root Cause Found & Fixed!
Thank you all for the incredible detective work on this issue, especially @ebbe-brandstrup whose insights about MCP servers and configuration bloat pointed me in the right direction!
### The Problem
My
~/.claude.jsonhad grown to 4.5MB with an estimated 1.2 million tokens (48x over the safe threshold). The file was storing massive amounts of conversation history and pasted content from 240+ sessions across multipleprojects.
### The Solution
Created two maintenance scripts that completely resolved the issue:
Results:
### Key Findings
### Preventive Measures
Set up an automated LaunchAgent (macOS) that runs hourly health checks to prevent this from happening again. The monitor alerts when approaching dangerous thresholds.
### Recommendations for Others
If you're experiencing this issue:
ls -lh ~/.claude.jsonecho "Tokens: $(($(wc -c ~/.claude.json | awk '{print $1}')/4))"Thank you again to everyone who contributed to identifying this issue! Special thanks to @tjx666 for identifying the complex schema problem, @lexxx233 for confirming the MCP connection, and @mahdimanesh for documenting the token
threshold warnings.
This was a team effort and your contributions helped solve a critical blocker. The issue isn't with MCP servers themselves but rather with how conversation history accumulates over time. Regular maintenance is the key!
---
macOS 15.6.1 | Claude Code 1.0.108 | Apple Silicon M-series
[like] Mahdi Manesh reacted to your message:
________________________________
From: Daniel Manfred Stoffel @.*>
Sent: Sunday, September 7, 2025 5:54:48 PM
To: anthropics/claude-code @.*>
Cc: Mahdi Manesh @.>; Comment @.>
Subject: Re: [anthropics/claude-code] CRITICAL: "Interrupted by user" immediately on ANY input - macOS 15.6.1 - Makes Claude Code 100% unusable (Issue #7261)
[https://avatars.githubusercontent.com/u/79516989?s=20&v=4]danielmstoffel left a comment (anthropics/claude-code#7261)<https://github.com/anthropics/claude-code/issues/7261#issuecomment-3263938781>
✅ SOLVED - Root Cause Found & Fixed!
Thank you all for the incredible detective work on this issue, especially @ebbe-brandstrup whose insights about MCP servers and configuration bloat pointed me in the right direction!
The Problem
My
~/.claude.jsonhad grown to 4.5MB with an estimated 1.2 million tokens (48x over the safe threshold). The file was storing massive amounts of conversation history and pasted content from 240+ sessions across multipleprojects.
The Solution
Created two maintenance scripts that completely resolved the issue:
Results:
Key Findings
Preventive Measures
Set up an automated LaunchAgent (macOS) that runs hourly health checks to prevent this from happening again. The monitor alerts when approaching dangerous thresholds.
Recommendations for Others
If you're experiencing this issue:
ls -lh ~/.claude.jsonecho "Tokens: $(($(wc -c ~/.claude.json | awk '{print $1}')/4))"Thank you again to everyone who contributed to identifying this issue! Special thanks to @tjx666 for identifying the complex schema problem, @lexxx233 for confirming the MCP connection, and @mahdimanesh for documenting the token
threshold warnings.
This was a team effort and your contributions helped solve a critical blocker. The issue isn't with MCP servers themselves but rather with how conversation history accumulates over time. Regular maintenance is the key!
---
macOS 15.6.1 | Claude Code 1.0.108 | Apple Silicon M-series
—
Reply to this email directly, view it on GitHub<https://github.com/anthropics/claude-code/issues/7261#issuecomment-3263938781>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/A7B4ZFZRTRVYQ7FPIJ2SCND3RRWORAVCNFSM6AAAAACF2UO3RWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENRTHEZTQNZYGE>.
You are receiving this because you commented.Message ID: @.***>
Doesnt work for me. I have cleaned the claude.json but still getting the same error.
Ok so for me the issue was Directus.io MCP server. Something is wrong with this MCP
This was the same for me. I ran the /mcp command and selected to restart MCP server. Directus failed to connect, but claude became functional again.
I had to remove 2 of the 3 MCPs I had, context7 and drawio. Then Claude started to work again.
Hey, very sorry about this. It looks like this is indeed a regression for MCP servers with really large contexts. I'll aim to get a fix in for the next release.
This should be fixed in the latest version.
@ollie-anthropic
Can you explain the fix please? Is the 25k limit no longer present?
@ollie-anthropic Hey. I encountered the issue two nights ago, and it stopped working for me altogether. After upgrading to the latest CC version today, the issue persisted. At first I thought it was related to the mcp configurations, after clearing all mcp settings, leaving them empty, the issue still persisted. Once I read this thread and looked at the size of the file (mine was 3.4 mb), I used a script to shrink its size and after that it all started working again. The upgrade allowed for one command to run successfully but on the second prompt, the user interrupted behavior started again until shrinking the file per the solution above. Just a heads up. Thanks!
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.