{"version":"2.1.191","anchor":"contextual-tips-system-gradual-rollout","canonical_anchor":"contextual-tips-system-gradual-rollout","heading":"Contextual Tips System [Gradual Rollout]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191\/e\/contextual-tips-system-gradual-rollout","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.191","markdown":"### Contextual Tips System [Gradual Rollout]\n\n**What**\n\nClaude now occasionally surfaces a short, context-aware tip after a response based on an AI analysis of the current conversation \u2014 suggesting a relevant command, shortcut, or workflow that fits what you are doing.\n\n**How it works**\n\n- After eligible responses, a lightweight sidecar classifier (using the fast model) reads the last ~30 turns of the transcript alongside your session metadata (turn count, MCP servers, team skills) and decides whether a tip is relevant.\n- Declining to tip is the expected default \u2014 tips only fire when a known situation in the catalog matches. Examples from the catalog include correction spirals, previous-session references, large context windows, and long-running commands.\n- Tips include a short 1-2 sentence message, the relevant feature ID, and an optional suggested action (e.g., `\/clear`, `claude --resume`).\n- You can give feedback on a tip by acting on it; reception is tracked.\n\n**Details**\n\n- Gated by the `allow_context_tips` feature flag and the `tengu_context_tip_classifier_outcome` telemetry gate \u2014 not all users see tips yet.\n- Team discovery metadata (teammate MCP servers and skills) is included in session context to make tips more relevant when working in a shared project.\n- Tips are not shown in non-interactive or transcript-mode sessions.\n\n**Evidence**\n\nContext tip classifier system (search for `\"[context-tips] classifier eligible, firing sideQuery\"` or `\"emit_context_tip\"`)"}