A nudge that watches for frustration and suggests filing an issue is registered but displays nothing.
A frustration-detecting issue-filing prompt is registered on every build with an empty display path.
What's wrong with this entry?
A new in-session nudge watches the conversation for signs of frustration and would suggest flagging an issue. It is registered on every build, but the code that would display anything is empty, so nothing is ever shown.
- Requires at least 3 submitted messages and a 30-minute cooldown between appearances.
- One regex set disqualifies conversations that used MCP tools or ran network commands (curl, ssh, kubectl, docker, aws, git push and others); a second detects frustration phrasing in your messages.
"issue-flag"
Strings lifted out of the shipped bundle, so the claim above can be checked against them.