[Bug] "You should know" built-in mod never runs checks in the desktop Code tab (works in terminal)
Status Open
Reported on v2.1.295
Maintainer reply None cached
Activity 0 comments · opened Oct 9, 2026
What's wrong
The built-in You should know mod (cc-plugin-you-should-know@builtin) is enabled but never runs a check in the Claude desktop app's Code tab. The same setup works in a terminal claude session.
Environment
- Claude Code 2.1.295
- Windows 11
- Desktop app Code tab (
CLAUDE_CODE_ENTRYPOINT=claude-desktop) vs. terminalclaude - First-party API (
api.anthropic.com), telemetry on: noDISABLE_TELEMETRY,CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFICorDO_NOT_TRACKset "cc-plugin-you-should-know@builtin": trueinenabledPlugins
Steps to reproduce
- Enable the mod:
/plugin enable cc-plugin-you-should-know@builtin. - Terminal: run
claude --debugand ask "Rundate8 times, one command at a time, then say done." - Desktop Code tab: ask for the same kind of 8-step turn.
- Look at
~/.claude/plugins/store/.
Expected
Both surfaces run a check every 6th main-loop step and write cc-plugin-you-should-know_builtin-*.json.
Actual
- Terminal works. The debug log shows
hooks module cc-plugin-you-should-know@builtin loaded,plugin.register ... admitted, andturn.stepfiring on every step. The store file appears withchecks: [{ step: 6, outcome: "none" }]. - Desktop does nothing. After an 8-step turn there is no store file at all, so
askedTurnis never written and no check runs.CLAUDE_CODE_YOU_SHOULD_KNOW_DEBUG=1shows nothing either.
Already ruled out
- Telemetry and first-party gates (see Environment).
- The desktop app does ask for
AbovePromptrows: a probe mod loggedAbovePrompt asked on desktop. - Other mods'
AbovePrompthooks callnext(e)first, so they don't keep the row request from reaching the built-in. - Other built-in mods (
cc-plugin-diff) write to the store on desktop.
Guess
The turn.step hook skips a check unless session.surfaces() includes terminal, or the mod's own AbovePrompt render has already run on that surface (with the bridge prompt origin excluding terminal). On the desktop surface that check apparently never passes, so the mod sits idle for good.