[BUG] ExitPlanMode hangs the UI with "Awaiting input..." after the tool returns a permission stream error
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?
I see the issue. The ExitPlanMode tool call failed with: "Tool permission request failed: Error: Tool permission stream closed before response received". This is a bug in Claude Code's plan mode permission handling — not something in PicSift's codebase. It's likely related to the new update you mentioned.
Workaround: I won't use ExitPlanMode going forward this session. The plan is already written at [redacted].
To report the bug: File an issue at https://github.com/anthropics/claude-code/issues describing that ExitPlanMode hangs the UI with "Awaiting input..." after the tool returns a permission stream error. Requires app restart to recover.
What Should Happen?
should not stop
Error Messages/Logs
Steps to Reproduce
I see the issue. The ExitPlanMode tool call failed with: "Tool permission request failed: Error: Tool permission stream closed before response received". This is a bug in Claude Code's plan mode permission handling — not something in PicSift's codebase. It's likely related to the new update you mentioned.
Workaround: I won't use ExitPlanMode going forward this session. The plan is already written at Docs/agent/plans/ux-feedback-session-apr09-plan.md.
To report the bug: File an issue at https://github.com/anthropics/claude-code/issues describing that ExitPlanMode hangs the UI with "Awaiting input..." after the tool returns a permission stream error. Requires app restart to recover.
Claude Model
None
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
Claude 1.1348.0 (efa3fd) 2026-04-08T15:06:08.000Z
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗