Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Short answer: “Claude Motion” is not a verified Anthropic feature name in the available official documentation. Anthropic’s documented tool for reviewing your own Claude use is the Claude reflection dashboard, a beta feature in Settings on Claude for web and the desktop app. A “Claude dashboard” can also mean an interactive app you create with Claude Artifacts, such as a project tracker or campaign-metrics screen. These are different jobs: reflection helps you understand how you use Claude; an Artifact dashboard helps you manage another project or workflow.
Is Claude Motion an official Anthropic tool?
Not according to the official Anthropic sources available for this comparison. Anthropic’s July 9, 2026 announcement names the usage-review feature reflection and describes a “reflection dashboard.” It does not identify a product called Claude Motion. The phrase could be a typo, an informal description, or the name of an unrelated product, but the available documentation does not establish that it is an Anthropic feature.
That distinction matters because silently treating Motion as another name for reflection can lead you to look for the wrong controls or expect capabilities Anthropic has not announced. If you saw “Claude Motion” in a video, post, or third-party app, verify the publisher and the current Claude interface before entering account information or assuming it is supported by Anthropic.
For the official usage-review feature, use Anthropic’s terminology: Claude reflection or the reflection dashboard. For dashboards that Claude builds for a task, use Artifacts.
#1 Best Overall
What the Claude reflection dashboard does
Anthropic introduced reflection in beta on July 9, 2026. It is designed to help you examine your relationship with Claude rather than to run a project for you. Anthropic describes a breakdown of when you use Claude most and what you spent that time working on, along with key topics and usage patterns.
The feature is intended to support deliberate use of AI. Anthropic frames the broader questions as “How often should someone use AI?” and “How can it be used most effectively?” A reflection prompt may ask, “What’s one thing you want to keep doing yourself, even if Claude could do it faster?” That is a self-assessment question, not a project metric generated from an external data set.
Where to find it
Anthropic says, “Your reflection dashboard can be found in Settings on Claude for web or the desktop app.” Open Claude in a supported web or desktop session, open Settings, and look for the reflection feature. The announcement does not establish that every account, plan, country, or rollout stage has access, so the current Settings screen is the practical authority for your account.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Choose a lookback period
The announcement lists four review windows:
- 1 month
- 3 months
- 6 months
- 12 months
These are dashboard settings, not study results or benchmarks. A one-month view can help you inspect recent changes in your habits; a 12-month view can reveal longer-running patterns when enough account history exists. The available announcement does not specify how the feature handles periods with little or no activity.
What appears in the review
The documented output includes summaries of chat activity, key topics, usage patterns, and the kinds of tasks you perform. In practical terms, the dashboard is a retrospective: it describes your use of Claude over the selected period and can prompt you to decide whether that use matches your goals.
Anthropic also says reflection may periodically raise questions, and that you can set quiet hours or a reminder to take a break after a chosen duration. Reminders can be dismissed. The announcement said a view of time spent using Claude would be added “soon”; that wording described a future addition at announcement time, so do not assume the time-spent view is available on every account today.
What a Claude dashboard made with Artifacts is
An Artifact dashboard is a custom, interactive app produced through a conversation with Claude. It is not a report about your Claude activity. You describe a problem, provide or reference the information the app should use, and ask Claude to create an interface that helps you monitor, calculate, or present that information.
Anthropic’s Artifacts documentation describes interactive apps created from conversations. Its examples include project dashboards with Gantt charts, progress bars, and milestone tracking. Anthropic’s Artifacts announcement also describes campaign dashboards with performance metrics and sales-pipeline visualizations.
Examples of useful Artifact dashboards
- Project delivery: milestones, task status, dependencies, dates, and a Gantt-style timeline.
- Campaign reporting: performance metrics and a view of how activity moves through a sales pipeline.
- Personal planning: a structured view of goals or recurring tasks, provided that you define the data and rules clearly.
- Operational tracking: a visual interface for a workflow whose fields, statuses, and calculations you specify in the conversation.
These examples illustrate the central point: an Artifact is shaped around a user-selected problem. Its usefulness depends on the instructions and information supplied to Claude, not on a hidden measurement of how often you chat with Claude.
How Artifacts differ from ordinary chat answers
A normal Claude response is usually a document, explanation, list, or code sample in the conversation. An Artifact can be an interactive app or visualization that you return to and use. The app may contain controls, charts, or status views appropriate to the task you described. It is therefore closer to a lightweight custom tool than to a usage report.
Artifact access and sharing depend on the current Claude product surface and plan. Anthropic lists chat, mobile and desktop apps, Slack, and the Console/API as Claude access interfaces in its interface documentation. That page does not make every Artifact capability identical across those interfaces, so check the controls shown in the product where you created the Artifact.
Free tools Windows power users keep installed
One-click scans. No signup required.
Reflection dashboard vs. Artifact dashboard
The two uses of “dashboard” should not be treated as competing editions of one tool. They answer different questions and consume different inputs.
| Comparison point | Claude reflection dashboard | Dashboard created with an Artifact |
|---|---|---|
| Primary purpose | Review and reflect on your own Claude usage. | Operate or visualize a project, campaign, workflow, or other chosen task. |
| Official status in the cited material | Anthropic feature announced in beta on July 9, 2026. | Artifact capability documented by Anthropic; examples were announced in 2024 and described in current help material. |
| Input | Your Claude chat activity over a selected period. | The problem, instructions, and data you provide for the app. |
| Typical output | Topics, usage patterns, activity summaries, and reflection prompts. | An interactive app or visualization, such as milestones, progress bars, a Gantt chart, campaign metrics, or a sales-pipeline view. |
| Time range | 1, 3, 6, or 12 months, as announced. | Defined by the app and the data you give it; no universal Artifact time range is stated. |
| Where to start | Settings in Claude for web or the desktop app. | A conversation in which you ask Claude to create an Artifact. |
| Sharing and access | Availability depends on the account’s current web or desktop interface; plan and geographic eligibility were not established in the announcement. | Access and sharing depend on the current product surface and plan. |
| What it does not do | It is not a general project-management dashboard. | It is not an automatic report of your complete Claude usage history. |
Which one should you use?
Choose based on the outcome you need, not on the word “dashboard.”
Use reflection when you want to understand your AI habits
Open reflection if your question sounds like one of these:
- How often have I been using Claude recently?
- What subjects or task types occupy most of my Claude activity?
- Does my use support the goals I set for myself?
- Do I want quiet hours or a break reminder?
- Which parts of a task do I still want to do personally?
Reflection is especially relevant when you are reviewing boundaries, attention, learning, writing practice, or the balance between assistance and independent work. Its output is about your pattern of use, not a score that declares a correct amount of AI use.
Use an Artifact when you need a working view of another process
Start an Artifact when you need to see or manipulate information about a project, campaign, pipeline, or similar workflow. Examples include tracking milestones across a delivery schedule, monitoring campaign performance, or organizing sales stages. You must define the fields and purpose in the conversation because the Artifact is custom-built for the problem you describe.
Use both for different decisions
You can use the features sequentially without confusing them. Reflection can help you decide how you want to use Claude. An Artifact can then support a separate project that you are working on with Claude. For example, reflection may highlight that much of your recent activity concerns a long-running project; an Artifact could provide a milestone view for that project. The first feature reviews Claude use, while the second helps operate the project itself.
How to check the reflection dashboard
- Sign in to Claude on the web or open the Claude desktop app.
- Open Settings.
- Look for the reflection or reflection-dashboard entry.
- Select one of the announced lookback periods—1, 3, 6, or 12 months—if the control is available.
- Read the activity summary, topics, and usage patterns for the selected period.
- Consider the reflection questions and decide whether you want to enable quiet hours or a break reminder.
If the entry is missing, do not infer that you have found a hidden “Motion” mode. The announcement does not establish universal plan, geography, or rollout eligibility, and it labels reflection as beta. Check the current account interface and Anthropic’s latest product information for availability.
How to create an Artifact dashboard
Artifacts are created through conversation, so begin with the job the dashboard must perform. A precise request gives Claude clearer requirements than simply asking for “a dashboard.”
Recommended Free Tools
- State the decision the dashboard should support. For example, say that you need to see which project milestones are late or which campaign stages are underperforming.
- Define the data. List the fields, units, dates, statuses, categories, and any source information the app should display.
- Describe the views. Ask for the visual elements that match the task, such as a Gantt chart, progress bars, milestone cards, performance metrics, or a sales-pipeline visualization.
- Specify calculations and rules. Explain how progress, totals, status labels, or late items should be determined. If a value is unknown, say how the app should mark it rather than asking Claude to guess.
- Ask for an interactive Artifact. Tell Claude that you want a usable dashboard rather than a prose summary, and identify the controls or filters you need.
- Review the result against the source data. Check labels, dates, totals, and status logic before relying on the visualization.
- Refine it in the conversation. Request focused changes, such as a clearer milestone view or a different grouping of campaign metrics.
Anthropic’s examples show the range of possible outputs, but they do not establish a single template, universal data connector, or identical sharing workflow for every account. Treat the Artifact as a custom app whose behavior must be checked against the instructions and data you supplied.
A practical prompt pattern
You can organize a request with four parts: purpose, data, views, and rules. For example: “Create an interactive project dashboard for these milestones. Show a Gantt-style timeline, progress bars, and a list of overdue items. Use the dates and statuses in the supplied table, calculate completion from the task values, and label missing dates as unknown rather than estimating them.” This pattern keeps the dashboard tied to an explicit task and makes assumptions visible for review.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Availability, privacy, and interpretation cautions
Reflection is beta and rollout details are limited
The July 2026 announcement calls reflection a beta feature and identifies web and desktop Settings as its location. It does not state universal eligibility by subscription plan or geography, nor does it prove that rollout is complete for all accounts. Availability may therefore differ from one Claude account to another.
Do not treat product settings as research statistics
The four reflection windows—1, 3, 6, and 12 months—describe selectable product periods. They are not evidence that a certain amount of Claude use is healthy, efficient, or typical. Likewise, a summary of topics and task types describes your activity; it is not an independent evaluation of the quality of your work.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteVerify “time spent” before relying on it
Anthropic said a view of time spent using Claude would be added “soon” in the announcement. Because that was a future-at-announcement statement, confirm that the control is present in your current dashboard before making decisions based on time totals.
Check an Artifact’s assumptions
An Artifact reflects the data and rules in its request. A polished chart can still be wrong if dates, categories, formulas, or source values are incomplete. Review the underlying inputs and calculations, especially when the dashboard informs deadlines, campaign decisions, or other consequential work.
Common points of confusion
“Motion” versus “reflection”
There is no verified basis in the cited Anthropic material for calling the reflection dashboard “Claude Motion.” Use the documented name when searching Settings or asking for support, and keep the uncertainty explicit if someone else uses the Motion label.
“Dashboard” versus “Artifact”
A dashboard made with an Artifact is a custom interface for your chosen data. It does not automatically become a complete analytics console for every Claude conversation. Conversely, reflection is not a blank canvas for project charts; it is the built-in review of Claude activity.
Web and desktop versus every Claude interface
The reflection announcement specifically names Claude for web and the desktop app. Anthropic’s interface documentation lists additional ways to access Claude, including mobile apps, Slack, and the Console/API, but that list does not establish that the reflection dashboard is available in all of them.
The decision in one sentence
If you want to see how you use Claude, look for the beta reflection dashboard in Settings on web or desktop. If you want to build a dashboard with Claude for a project, campaign, pipeline, or other workflow, ask Claude to create an Artifact. “Claude Motion” remains an unverified name rather than a documented Anthropic product.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
