Follow Discord
Sweep 22 Oct 2026 · 04:32Z Build v2.1.308 527 read Stable v2.1.308 Latest v2.1.308 Next v2.1.308 Feeds RSS JSON llms.txt llms-full.txt Unofficial

Claude Code v2.1.248 ·

A set of usage-analysis prompts sits in the build with no visible entry point

Seven prompts that analyse your Claude Code usage habits ship with no entry point.

Nothing to try yet Notable In Development
JSON All of v2.1.248
Nothing to try yetTier: how much it should matter to you
3Useful: my rating, 1 to 5
5Signal: worth watching, 1 to 5
Usage InsightsArea: what it touches
In DevelopmentKind: in v2.1.248,
What probably matters to youSection of the release

Prompts for project areas, friction, suggestions and more exist as data with nothing invoking them.

What

Seven prompts that analyse how you have been using Claude Code ship as plain data: project areas, interaction style, what works, friction analysis, suggestions, on the horizon and a fun ending. Each allows 8192 tokens and demands a strict JSON reply. The suggestions prompt describes MCP servers, custom skills, hooks, headless mode and task agents, and asks the model to prioritise CLAUDE.md additions you have repeated across sessions.

Details
  • The list splices in an empty array before the closing prompt, which is what a conditionally compiled section looks like when it is switched off.
  • Nothing in this group shows what surfaces these prompts.
Evidence

Include 3 opportunities. Think BIG - autonomous workflows, parallel agents, iterating against tests.

Strings lifted out of the shipped bundle, so the claim above can be checked against them.

See this entry in the whole of v2.1.248 →

Feedback