It's Thariq from the Claude Code team here. This was my change! I made the AskUserQuestion tool so am generally in charge of maintaining it.
First, overall wanted to apologize and agree that this did not meet our bar and does not represent how we plan to ship on Claude Code.
To give you a motivating sense, as the models get more powerful, usage patterns start to change. I'd gotten a lot of feedback that AskUserQuestion tool was starting to block some long running jobs unexpectedly and so I tried a change to help that.
Our internal feedback on this was good, but the rollout should have been opt-in (like it is now) and on the Changelog.
Thanks for the feedback! We're always trying to make Claude Code better while balancing it with how people use it in many diverse ways. I did not really intend AskUserQuestion to be a safety gate when I first built it, but I realize it has evolved in that direction for some users.
I'm still exploring other ways of helping with this problem of balancing longrunning work and input, but will take lessons from the rollout here.
Hi there, Thariq from the Claude team here. Sorry this is happening, we'll fix it ASAP.
We don't want anyone to feel locked into the tool. Claude's designs are HTML/CSS/JS that any editor can handle; we'll make sure it's possible to download them even after you unsubscribe.
We've been on this since the bug surfaced. Everyone affected is getting a full refund and an extra grant of usage credits equal to their monthly subscription as our apology. You can see my original post here: https://x.com/trq212/status/2048495545375990245. We’re still working on sending emails to everyone affected.
Our support flow wasn't set up to route a complex bug like this to engineering. We’re hoping to make this better but will take some time. Sorry to everyone caught up in it.
Sorry to hear, was wondering if you could find a session where this happens and hit /feedback and just say something like stop hook not firing and we'll take a look.
Yes, we do but harnesses are hard to eval, people use them across a huge variety of tasks and sometimes different behaviors tradeoff against each other. We have added some evals to catch this one in particular.
We haven't yet found generalizable "make this model smarter" features, but there is a tradeoff of putting instructions in system prompts, e.g. if you have a chatbot that sometimes generates code, you can give it very specific instructions when it's coding and leave those out of the system prompt otherwise.