BUILT-IN MOD / QUICK GUIDE
Claude Code’s You Should Know mod.
You Should Know is an optional built-in mod that adds a side agent to longer tasks. Enable it with the command below if it is available in your session. It is off by default; you do not need a community marketplace.
Updated October 17, 2026 · Documentation-based guide, not an execution test.
What does You Should Know do?
Anthropic introduced it in Claude Code v2.1.287. The side agent looks for details you or Claude might miss while work continues and can display a note above the prompt. Current documentation says this separate request uses the session’s model and has no tools to read files, run commands, or change Claude’s actions. The release notes specify first-party sessions with telemetry on. Read the release notes.
Consider it when you want another perspective during a longer task. A note is a reason to inspect the relevant work yourself: it does not establish that the result is correct, that a command is safe, or that every mistake will be caught. This is our suggested way to use the feature, rather than a performance claim.
How to enable the built-in mod
Check your installed version in a shell first:
claude --versionThen enter this slash command at the Claude Code prompt, rather than in your shell:
/plugin enable cc-plugin-you-should-know@builtinYou can also open /plugin, select Installed, and choose Show disabled. Look for cc-plugin-you-should-know under Built-in if it is available for your organization. Close the panel after changing its state; the plugin CLI reference says panel changes are applied by reloading when you close it.
Why is it missing, or not showing notes?
The entry is missing
Open /plugin → Installed → Show disabled and look under Built-in. The shell command claude plugin list does not show built-in plugins; neither does the marketplace-only /plugin list listing. An empty list does not establish that You Should Know is unavailable.
“Not installed in this project” when enabling
The current official availability checklist ties that error to sessions where the mod is not listed. Check these conditions before looking for a marketplace package:
- Use Claude Code 2.1.287 or later, with the feature available for your organization.
- Connect directly to the Claude API using a claude.ai account or Console API key. The documentation excludes LLM gateways, Claude apps gateways, and keys supplied by
apiKeyHelper. - The session must fetch the feature flags it needs.
DISABLE_TELEMETRYand a first session after installation or upgrade whose flags have not arrived can keep it from appearing.
Our recommendation is to check your existing connection and session state first. Do not change organization settings or telemetry just to make the entry appear. There is no community marketplace install command to repair eligibility.
On older builds, a failed claude plugin details cc-plugin-you-should-know@builtin lookup may point you toward the wrong list. The 2.1.302 release notes say the hint now points to /plugin. That fix improves the message; it does not grant access to the mod.
The active-mod count does not include it
The dim mods-active line in the terminal’s plugin panel excludes built-in mods. Inspect the Built-in entry’s state instead. Absence from that count is not evidence this feature is disabled.
It is enabled, but there is no note
The documented behavior is to surface something worth knowing during longer work, rather than show a continuous meter. A quiet session gives you no evidence that everything has been reviewed. If your issue affects other mod interfaces too, use the general loading and display checklist to check your session surface.
Do background checks use my plan or API budget?
Yes. The official cost explanation says checks count toward plan usage limits or API costs. They send the conversation with tool results, the mod’s instructions, and recent notes. Conversation context follows normal prompt-cache terms; the checker’s instructions and reply are billed in full each time.
A session without a visible note does not establish that no checks ran. For diagnostics, the documentation provides this shell setting before you start a session:
CLAUDE_CODE_YOU_SHOULD_KNOW_DEBUG=1 claudeWe have not measured check frequency or costs. Disable the mod with the control below if you do not want these background requests.
How to turn You Should Know off
Disable its Built-in entry in /plugin, or use the documented plugin-disable command with its identifier:
/plugin disable cc-plugin-you-should-know@builtinCheck its state in the panel afterward. Built-in mods cannot be uninstalled or updated individually. The overview says --safe-mode, --bare, and disableAllHooks do not stop built-in mods, so use the feature’s own disable control.
Sources and next steps
Official built-in mods overview · Official session plugin commands · v2.1.287 release
For a community mod with published setup, follow the installation guide. To compare what different mods display, browse the context collection and workflow collection. This guide does not claim measured cost savings, additional privacy guarantees, or tested compatibility.