How to compare model usage

A practical guide to comparing AI model usage in vibestats across reporting windows and source scopes.

Intent

Guide

Focus

How to compare model usage is a practical workflow page for turning local AI coding usage into something readable and repeatable.

Next step

Open the command reference

Highlights

Stable windows matter more than perfect totals
Model share is easier to read when grouped directly
Source context helps interpret model shifts

Relevant commands

npx vibestats --modelnpx vibestats --since 2026-01-01 --until 2026-01-31 --modelnpx vibestats all --model

Step 1

Switch to model grouping

Use the model report shape so the output groups by model instead of by day or month.

Step 2

Keep the date window stable

Use a clear date range so the comparison reflects model behavior and not a moving reporting window.

Step 3

Add cost and source context

Check whether model share also changes cost shape or differs between Claude-compatible and Codex usage.

Why this guide exists

Most AI coding reporting problems are not about one missing command. They are about choosing the right surface: daily usage, wrapped summaries, activity heatmaps, cost views, or shareable aggregate pages.

What to expect

This guide stays focused on vibestats workflows and the pages already documented in the public command reference, so you can move from local data to a readable result quickly.

FAQ

What is the fastest way to approach how to compare model usage?

Start with the relevant command, verify the output locally, then decide whether you need a share page, a wrapped summary, or a heatmap for communication.

Do I need to upload raw conversations for these guides?

No. vibestats works from local usage artifacts and only turns aggregate results into hosted pages when you explicitly publish them.

Continue by intent

View all guides

features model-breakdownOpen the related vibestats page and continue the workflow from there.compare session-breakdown-vs-model-breakdownOpen the related vibestats page and continue the workflow from there.features token-and-cost-trackingOpen the related vibestats page and continue the workflow from there.