Your data starts flowing as soon as ATTRIBUT captures its first session — one recorded run from an AI coding tool you've connected, such as Claude Code, Cursor, Codex, or Antigravity. That first session usually shows up within moments of you finishing it, and the Overview page tells you exactly what it's waiting for the whole time. Until that first session lands, Overview shows a connect screen instead of your dashboard — this article walks through that screen, what has to happen before data appears, and how to tell it's working.

Two things need to be true before any numbers show up:

Nothing appears on Overview until both of those are true at least once.

If your account has never captured a session, Overview replaces the normal dashboard with a connect screen. It shows the connector command to run, a "Waiting for your first session" indicator, and the list of supported tools.

Once you've run the command and used the tool, click "I've run it — check for sessions" on that screen. This starts an active check: ATTRIBUT polls for a captured session every few seconds, for up to about a minute. If a session is found, the screen switches to "First session captured," showing that session's title and cost along with a button to view your full session list.

If nothing turns up after about a minute, the check stops on its own and returns you to the connect screen with a note asking you to confirm your terminal is open and try again. Nothing is lost — you can rerun the same check as many times as you need.

Once ATTRIBUT has captured a session — ever, on your account — Overview stops showing the connect screen for good and switches to your real dashboard: your spend statement, the spend-to-value breakdown by repo, checkpoints, heatmap, daily rhythm, model mix, and daily spend chart.

Note that an empty result for one specific date range is different from never having connected. If you've captured sessions before but the range you're currently viewing happens to have no activity, Overview still renders the full dashboard — it just shows zeroes for that range rather than falling back to the connect screen.

Once an AI tool is connected and reporting, one setup step is still worth finishing: connecting GitHub. Until you do, Overview shows a short banner near the top of the page: "Connect GitHub to see what your spend shipped," with a button to connect. GitHub is what lets ATTRIBUT attribute your AI spend to the pull requests it actually helped ship, including the cost-per-PR figures shown elsewhere on Overview (for example, the "Cost / merged PR" footnote).

This banner checks your connection status directly, so there's nothing to dismiss and no separate step to mark complete — it simply disappears on its own the moment GitHub is connected.

If you've installed the connector, run a session, and the check above still finds nothing after about a minute, see the CLI connector guide's troubleshooting section in the Connectors collection. It also covers backfilling sessions you ran before you connected, in case earlier work never made it in.