Skip to content
| Marketplace
Sign in
Visual Studio Code>Other>RTK InspectorNew to Visual Studio Code? Get it now.
RTK Inspector

RTK Inspector

PeterMEFrandsen

|
561 installs
| (0) | Free
Visualize RTK savings alongside AI CLI token usage in VS Code.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info

RTK Inspector

Build Status Visual Studio Marketplace Open VSX Coverage Status License: MIT

RTK Inspector is a VS Code extension that visualizes how much the rtk CLI is saving you, then compares those savings against your total AI CLI token usage across the tools you already use.

Install it from the Visual Studio Marketplace or Open VSX, and browse the source on GitHub.

RTK Inspector banner

Dashboard preview

RTK Inspector Dashboard

Why RTK Inspector?

  • Track daily RTK savings trends in a sidebar chart.
  • Compare RTK input, output, saved tokens, and CLI totals in one place.
  • See an honest True Savings % calculation: saved / (CLI total + RTK input).
  • Review per-CLI token usage alongside RTK results.
  • Refresh on demand and spot when a newer rtk CLI version is available.

Installation

  • Install from Visual Studio Marketplace
  • Install from Open VSX Registry

What the extension reads

RTK Inspector combines RTK output with local session data from supported AI CLIs.

Source Data used
rtk CLI rtk gain -d -f json
GitHub Copilot ~/.copilot/session-state/*/events.jsonl
Gemini CLI ~/.gemini/tmp/*/chats/session-*.json
Claude Code ~/.claude/projects/**/*.jsonl
Codex ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl

Only days where RTK has data are included in the CLI comparison, so the numbers stay aligned.

Requirements and setup

  1. Install the rtk CLI.
  2. Make sure rtk is available in your PATH, or set a custom path with rtk-inspector.executablePath.
  3. Open the RTK Inspector view from the Activity Bar.
  4. If you use RTK from WSL while VS Code runs on Windows, enable rtk-inspector.useWsl.

CLI metrics appear when at least one supported tool has local session data available.

Usage

  1. Open RTK Inspector in the Activity Bar.
  2. Review the summary cards and charts in the sidebar.
  3. Click Refresh RTK Stats to reload RTK data and local CLI usage.
  4. Expand the commands list in the sidebar to inspect RTK command counts.

Commands

Use the Command Palette to access:

  • RTK Inspector: Refresh RTK Stats
  • RTK Inspector: Show RTK Inspector Logs
  • RTK Inspector: Run RTK Inspector Diagnostics

Settings

  • rtk-inspector.executablePath: path to the RTK executable. Defaults to rtk.
  • rtk-inspector.useWsl: runs RTK through wsl.exe -e when VS Code is on Windows and RTK lives in WSL.

Troubleshooting

If the dashboard does not load as expected:

  1. Run RTK Inspector: Run RTK Inspector Diagnostics.
  2. Open RTK Inspector: Show RTK Inspector Logs.
  3. Verify that rtk runs in your shell, or set rtk-inspector.executablePath.
  4. On Windows + WSL setups, enable rtk-inspector.useWsl.

For Gemini CLI, the extension uses message output and thought tokens from each session entry to avoid inflating totals with cumulative input counts.

For Codex, the extension reads JSONL rollout files and takes the last cumulative token snapshot per session, counting shell_command function calls and local_shell_call items as tool calls.

Development

  • Repository: github.com/petermefrandsen/rtk-inspector
  • RTK CLI: github.com/rtk-ai/rtk

License

MIT

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft