[FEATURE] spinnerTipsEnabled is all-or-nothing - no way to keep useful tips without filler phrases

Resolved 💬 2 comments Opened Apr 16, 2026 by four-rainy-days Closed Apr 16, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

spinnerTipsEnabled controls two very different categories of content with a single boolean:

  1. Actually useful tips: keyboard shortcuts, feature hints, things that teach you something about Claude Code
  2. Filler phrases: "Thinking through it", "Double checking the double checks", "This one needs a moment"

These have completely different value to the user. Category 1 is worth reading. Category 2 is noise that trains you to ignore the tip area entirely, which defeats the purpose of category 1.

The only option today is spinnerTipsEnabled: false, which kills both.

Proposed Solution

Separate the two categories so users can opt into useful tips without the filler. Some options:

  • A setting like "spinnerTipStyle": "useful-only" | "all" | "none"
  • Tag tips internally by category and let spinnerTipsOverride.excludeDefault work per-category
  • Simply remove the filler phrases from the tip pool (I don't see how they help anyone)

Alternative Solutions

spinnerTipsEnabled: false (lose useful tips)

Priority

Low - Nice to have

Feature Category

Configuration and settings

Use Case Example

_No response_

Additional Context

_No response_

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗