[BUG] "Yes, always for this project" and --dangerously-skip-permissions both cause broken session: all prompts return "Interrupted · What should Claude do instead?"

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?

After granting permissions via "Yes, always for this project" or using --dangerously-skip-permissions (claudedg), every subsequent prompt in the session returns "Interrupted · What should Claude do instead?" regardless of what is typed. The session becomes completely unusable.

What Should Happen?

Claude should continue working normally after permissions are granted, executing bash commands and responding to prompts without interruption.

Error Messages/Logs

Interrupted · What should Claude do instead?

Steps to Reproduce

1. Open terminal and run: claude
2. Give Claude a task that requires bash commands (e.g. create project files)
3. When permission prompt appears, select "Yes, always for this project" OR exit and run claudedg instead
4. Type any prompt — Claude returns "Interrupted · What should Claude do instead?"
5. Every single subsequent prompt returns the same, session is broken
6. Only workaround: fully close terminal and start new session (losing all context and wasting tokens)

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.80

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

Issue started approximately 21:00 CET on March 19, 2026. Previously working on version 2.1.79.