Skip to content
LLM Usage Metrics

KiloCode Source

Default location

Section titled “Default location”
  • VS Code and Cursor global storage for extension kilocode.kilo-code: <editor root>/User/globalStorage/kilocode.kilo-code/tasks/*/ui_messages.json, where the roots are ~/.config/Code and ~/.config/Cursor on Linux, ~/Library/Application Support/Code and ~/Library/Application Support/Cursor on macOS, and %APPDATA%\Code and %APPDATA%\Cursor on Windows
  • Remote VS Code server storage: ~/.vscode-server/data/User/globalStorage/kilocode.kilo-code/tasks/*/ui_messages.json

Override

Section titled “Override”
Terminal window
llm-usage daily --source kilocode --kilocode-dir /path/to/kilocode/tasks

kilocode is directory-backed, so generic source directory overrides also work:

Terminal window
llm-usage daily --source-dir kilocode=/path/to/kilocode/tasks

Parsing notes

Section titled “Parsing notes”

KiloCode shares the Cline task format. The adapter reads ui_messages.json usage payloads, keeps positive USD cost values as explicit cost, and reads the model from sibling api_conversation_history.json.

Like Roo Code, the Kilo Code VS Code extension writes tokensIn as the cache-inclusive prompt count (input plus cacheWrites plus cacheReads). The adapter subtracts the cache buckets whenever tokensIn is at least their sum, so input tokens exclude cache reads and writes as in every other source. Older rows carried the provider’s raw count; those whose count is below the cache buckets cannot be cache-inclusive and are left unchanged.