> For the complete documentation index, see [llms.txt](https://docs.nimbalyst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nimbalyst.com/session-management/ai-usage-report.md). # AI Usage Report The AI Usage Report shows how you use models and tools across Nimbalyst. Use it to understand activity over time, compare projects, and discover tools that are available but not yet part of your workflow. Open it from **Window > AI Usage Report**. If you are deciding between API keys and a Claude or Codex subscription, see [Claude Code and Codex subscriptions](https://nimbalyst.com/claude-code-codex-subscriptions/). ## Overview The **Overview** tab combines: * Session and token totals * An activity heatmap * Historical usage over time * Per-project activity Use the project filter when you want to separate one workspace from your all-project totals. ## Tool Usage Open the **Tools** tab to see calls made to: * Built-in agent tools, such as reading files, searching, editing, and running commands * MCP tools * Tools contributed by Nimbalyst extensions The report includes: * Your most-used tools * Successful and failed call counts * Built-in versus MCP and extension usage * Calls over time * Usage by provider * Usage by project Tool counts describe calls, not time spent or tokens consumed by a tool. ## Backfill Earlier Sessions New tool calls are recorded automatically. Click **Backfill history** to populate the report from compatible Claude Agent and Codex sessions created before tool tracking was enabled. Backfill reads your stored Nimbalyst session history. It does not rerun the sessions or call the tools again. ## Where the Data Lives The report is generated from usage data stored locally by Nimbalyst. Tool tracking records the tool identity, project, provider, count, and error count; it does not turn tool inputs or outputs into a public activity feed. The AI Usage Report is separate from provider billing dashboards. For authoritative subscription limits, API charges, or provider-specific usage windows, use the dashboard provided by the model provider. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.nimbalyst.com/session-management/ai-usage-report.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.