[BUG] ExitPlanMode tool fails with "AbortError" - hangs indefinitely when MCP servers active
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?
When Claude Code calls the ExitPlanMode tool to exit plan mode, it hangs indefinitely showing "Honking..." status in the UI, then fails with error:
Tool permission request failed: AbortError
Steps to Reproduce:
- Start Claude Code with MCP servers enabled (Chrome extension + Notion connector)
- Ask Claude to plan a multi-step task (this triggers plan mode)
- Claude successfully writes plan to
~/.claude/plans/*.md - Claude calls
ExitPlanModetool - UI shows "Honking..." status indefinitely
- Eventually fails with
AbortError - Only way to recover is killing the process (
Ctrl+Corkill)
Process details showing the hung state:
--permission-mode plan --mcp-config {"mcpServers":{"Claude in Chrome":{"type":"sdk","name":"Claude in Chrome"},"mcp-registry":{"type":"sdk","name":"mcp-registry"},"ef89416a-...":{"type":"sdk","name":"..."}}}
The plan file is written successfully before the hang occurs. This appears to be a race condition or communication issue between the permission system and MCP servers.
What Should Happen?
ExitPlanMode should display an approval prompt in the UI, allowing the user to review and approve/reject the plan. After user confirmation, Claude Code should exit plan mode and proceed with implementation.
Error Messages/Logs
Tool permission request failed: AbortError
Steps to Reproduce
- Start Claude Code v2.1.8 with MCP servers enabled (Claude in Chrome extension + Notion connector are active)
- Ask Claude to plan a multi-step implementation task, e.g.: "Help me plan making these pages visually consistent"
- Claude enters plan mode and writes a plan to
~/.claude/plans/<random-name>.md - Claude calls the
ExitPlanModetool to request user approval - Observe: UI shows "Honking..." status and hangs indefinitely
- Wait ~30-60 seconds - eventually fails with
AbortError - Only recovery:
Ctrl+Corkill <pid>
Workaround: Kill process and restart. Avoid tasks that trigger plan mode, or disable MCP servers.
Claude Model
None
Is this a regression?
I don't know
Last Working Version
_No response_
Claude Code Version
2.1.8
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
MCP Configuration from process:
{
"mcpServers": {
"Claude in Chrome": {"type": "sdk", "name": "Claude in Chrome"},
"mcp-registry": {"type": "sdk", "name": "mcp-registry"},
"ef89416a-1e16-4a1c-b8d0-156632e6d0da": {"type": "sdk", "name": "Notion connector"}
}
}
Hypothesis: The ExitPlanMode tool triggers a permission prompt that requires UI interaction, but something in the MCP server communication chain is blocking or not forwarding the approval request correctly, causing the tool to hang until it times out with an AbortError.
Environment details:
- macOS 26.2 (Build 25C56)
- Chrome extension: Claude in Chrome (active)
- Notion MCP connector (active)
15 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Additional Testing Results
I ran some automated tests to help isolate the issue:
Test 1: Non-interactive mode (
--print) without MCP serversResult:
ExitPlanModewas denied (not hung) with this in the response:This is expected behavior -
--printmode can't display approval prompts, so it correctly denies the tool rather than hanging.Test 2: Interactive mode with MCP servers (original bug)
Result: Hangs indefinitely with "Honking..." status, then fails with
AbortErrorConclusion
The bug appears to be specific to the interactive permission prompt UI when MCP servers are active:
| Mode | MCP Servers | Result |
|------|-------------|--------|
|
--print(non-interactive) | None | ExitPlanMode denied (correct) || Interactive | With MCP | Hangs → AbortError (bug) |
| Interactive | Without MCP | Untested |
This suggests the issue is in how the permission prompt system communicates when MCP SDK servers are loaded, not in the core
ExitPlanModelogic itself.Related: The duplicate issues found (#15686, #18791) also involve permission prompts and MCP config freezing, supporting this hypothesis.
I'm seeing the same hang in the Claude app (in Code mode).
I'm seeing the same issue in Claude Desktop Code. Claude can't exit Plan mode. A workaround was to start a new session to apply the plan. But this is very annoying
I'm getting this too, has stalled my work.
I'm using Claude for Windows and the ExitPlanMode tool hangs indefinitely without permission prompt or anything.
Steps to reproduce:
I'm having the same issue in Claude Code on macOS.
+1.
Similar bug here using desktop app in Code mode.
What works okay for me is stopping the prompt and telling it:
"You were stuck exiting Plan Mode so I exited for you and set the mode to 'Code'. Can you go straight to the implementation part?"
The issue is that all of its tools stop working when I do that
@tonycoderdev. So i have to start a fresh session each time to apply the
plan
On Thu, Jan 22, 2026 at 7:31 AM tonycoderdev @.***>
wrote:
Fixed the issue where permission prompts weren't showing and thus made plan mode get stuck in desktop. Please refresh or restart the app. Sorry about that folks!
<img width="840" height="151" alt="Image" src="https://github.com/user-attachments/assets/020d69bd-343c-470e-8ecf-585c42edb0fa" />
Well, there you got it. :D
Kudos. Now the Planning UI looks much better and exiting the plan mode is
so smooth.
Only thing I noticed is that after exiting plan mode, instead of switching
to code mode, it switches to ask mode.
Also another thing is that conversations keep getting longer without older
messages getting masked after compaction which at some point becomes very
heavy on the PC’s RAM and slows down the PC. Would be great if you could
fix that.
On Wed, Jan 28, 2026 at 3:36 PM mrnobody @.***> wrote:
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.