Anthropic launched Claude Reflect in beta on July 9, 2026 — a usage dashboard built into Claude’s Settings page that shows you how, when, and why you use Claude, then asks whether any of that should change.

The product occupies an unusual space: part analytics panel, part skills coach, part digital wellness tool. For builders who spend most of their day inside Claude, there are a few details worth understanding.

What the Dashboard Shows

Reflect requires Memory to be turned on and is available to Free, Pro, and Max users on Claude’s web and desktop apps. Once enabled, it summarizes your conversation history across selectable time windows: 1, 3, 6, or 12 months.

The summary covers:

  • Key topics: what you engage Claude on most often
  • Task type breakdown: the kinds of work (writing, coding, analysis, brainstorming) that fill most of your sessions
  • Usage patterns: when you use Claude, peak activity times, session frequency
  • Coming soon: total time spent (this metric isn’t live yet, only announced)

It’s closer to Spotify Wrapped or iOS Screen Time than a technical analytics dashboard. There’s no per-message token count, no cost breakdown, no latency data.

Privacy boundaries: Incognito chats are excluded. Conversations tied to health integrations are excluded. Underlying files from connected tools don’t appear (only summaries). The report data stays in the dashboard and is explicitly not fed back into training or any other purpose.

The 4D AI Fluency Framework

The part most relevant to serious Claude users: Reflect maps your usage patterns to Anthropic’s AI Fluency Framework, which defines skilled AI use across four dimensions.

Delegation — setting goals and deciding whether and how to involve AI at all. High delegation skill means you’re choosing the right tasks to hand off, not just reflexively reaching for Claude.

Description — prompting effectively: giving Claude the context, constraints, and output shape it needs to produce something usable. Low description skill shows up as lots of re-prompts and heavy editing.

Discernment — accurately evaluating Claude’s outputs. Knowing when to trust, when to verify, and when to override. Critical for code generation and factual work.

Diligence — taking responsibility for what gets done with Claude’s help. This includes verifying outputs before shipping, catching errors, and maintaining the human in the loop on consequential decisions.

Reflect doesn’t give you a numeric score on each dimension — it offers observations and recommendations based on detected patterns. If you repeatedly paste the same context block at the start of conversations, it may flag that as a Description opportunity and suggest building a Project with that context built in. If you frequently re-ask similar questions, it may suggest a custom template or skill.

Wellbeing Features

Two settings ship with the launch:

  • Quiet hours: block a time window during which Claude won’t respond (or will respond minimally — the exact behavior is configurable)
  • Break nudges: a notification after a set amount of continuous Claude use, dismissible

The dashboard also periodically surfaces a reflective prompt — for example: “What’s one thing you want to keep doing yourself, even if Claude could do it faster?” You can decline to engage with it, or talk it through with Claude directly.

Anthropic developed these features with researchers from MIT Media Lab’s Advancing Humans with AI program, the Digital Wellness Lab at Boston Children’s Hospital, and the Family Online Safety Institute.

The Tension Worth Understanding

TechCrunch characterized Reflect as “quietly selling you on AI” — noting that mapping heavy Claude use to a “Fluency Framework” reframes what could be dependency as measurable skill. The harder-to-refute version of this critique: the recommendations Reflect surfaces (use Projects, build templates, add memory context) are all actions that deepen Claude integration, not reduce it.

That’s not necessarily bad for builders, but it’s worth naming. The tool is designed to promote intentional AI use — and Anthropic’s definition of intentional use includes using Claude more effectively, not using it less.

What It Means for Builders

If you’re a heavy Claude user yourself, Reflect’s Fluency Framework gives you a vocabulary for auditing your own habits. The question “Am I using Claude where it actually helps, or where I’ve just habituated to it?” is genuinely useful to ask periodically.

If you’re building a Claude-powered product, two things are worth watching:

  1. The upcoming Cowork conversation reflection — announced but not yet live — will let users reflect on multi-agent sessions, not just individual conversations. For builders who ship agentic workflows, that means your users may eventually get a breakdown of what their Claude-powered automations did on their behalf. Transparency features like this may become table stakes.

  2. The recommendations model — Reflect’s observation that “you keep repeating this context, you should use Projects” is essentially a customer-success nudge embedded in the product. If you’re building SaaS on top of Claude, a similar pattern (detecting repeated friction and surfacing the right feature to solve it) could be valuable in your own product layer.

Memory requirement: Reflect only works if users have Memory turned on. If your product manages Claude’s memory externally (injecting context via system prompt rather than relying on Claude’s built-in Memory), your users won’t see their usage reflected here at all.

Access

Claude Settings → Reflect on web or desktop. Beta. Free, Pro, and Max accounts with Memory enabled.

Reflect is a consumer product, not a developer API. There’s no endpoint to query your team’s usage patterns or pull fluency scores programmatically. But for individual builders spending significant time in Claude, it’s the first tool Anthropic has shipped that turns usage history into something legible — and the Fluency Framework is a useful mental model regardless of whether you read your own Reflect report.