Compare two slices of your AI work

This walkthrough assumes you have already exported and imported at least one source and can read the dashboard without fooling yourself. Comparison does not create new metrics. It asks whether two filtered slices may be subtracted.

If your imports are ChatGPT, Claude web, or Gemini Takeout, expect token and cost rows to stay Unavailable. That is correct. See unavailable is not zero.

Open /app/dashboard. Pick the range first. Add provider, project, or model filters only after the range is right — otherwise you will compare two accidents.

Read Metric coverage before you press Compare. If a headline tile is already partly covered, comparison will not magically complete it.

Press Compare. Side A should match the dashboard you just left. Side B should still be on its defaults (typically this week, all providers, no project or model filter).

Do not "make B match A to check the feature." A comparison of a view with itself prints zeroes and looks broken. The product leaves B independent so the first screen you see is a real contrast.

All twelve parameters are in the URL. Copy it if you want to return to this pair later, or save each side as its own view after you like the filters.

Typical honest pairs:

1. Same providers, previous window. Set B's range to the equivalent period before A. This is the closest relative of the on-dashboard "What changed" narrative, with more room to inspect refused rows.
2. Codex versus everyone else. If you actually have Codex sessions, put Codex alone on B. Token and cost comparisons become possible on that side; they stay refused on Claude or Gemini web.
3. One project versus the account. Put a confirmed project on B and leave A unfiltered. Composition will show which providers and models exist only in that project.

If a filter would empty a side, leave the row. The page will say the side contains no sessions rather than inventing a baseline.

Scroll the metrics table slowly. A numeric delta is the exception. The useful half on a mixed account is usually:

• "The Claude export format does not contain it."
• "View A reports this for 1 of 4 sessions … the missing sessions are missing by export format, not at random."
• "The two sides recorded this metric differently."

Those sentences are the capability matrix and /methodology applied to a pair of slices. They are not error states. If you only wanted the rows that survived, you would not know what you had thrown away.

Composition groups underneath the metrics. A provider or model present on one side only reads Not in this view on the other. That mismatch is often why a total moved.

Return to /app/dashboard (or stay on the side whose filters you want). Name the view in the saved-views section. Use a name you will recognise in a month — "Codex all-time" beats "View 3".

Saving under an existing name updates it. You can keep at most 20. Only the six filter params are stored; session titles never are. Details and the non-nested form rule are in Compare views and save the ones you reuse.

It will not email you when a metric crosses a threshold. Watchlists and alerts are not built. It will not add a planned provider. It will not fill Claude, Gemini, or ChatGPT web tokens. If you came from the Novus hub (opens in a new tab) looking for study tools rather than measurement, Novus Learn (opens in a new tab) is the sibling that turns source material into cited notes.

When you are done comparing, go back to reading the dashboard and believe coverage first. Comparison is a scalpel for two slices you already trust separately.