{"version":"2.1.234","anchor":"a-frustration-detecting-prompt-to-file-an-issue-wired-up-but","canonical_anchor":"a-frustration-detecting-prompt-to-file-an-issue-wired-up-but","heading":"A frustration-detecting prompt to file an issue, wired up but silent","tier":"soon","area":"Proactivity","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234\/e\/a-frustration-detecting-prompt-to-file-an-issue-wired-up-but","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.234","markdown":"### A frustration-detecting prompt to file an issue, wired up but silent\n\nA nudge that watches for frustration and suggests filing an issue is registered but displays nothing.\n\n**What**\n\nA 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.\n\n**Details**\n\n- Requires at least 3 submitted messages and a 30-minute cooldown between appearances.\n- 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.\n\n**Evidence**\n\n`\"issue-flag\"`\n\n- Area: Proactivity\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 5\/5\n- Present in the build but not switched on"}