LiteLLM Spend Tracker — Migration Build

This is a one-time migration build, not the extension you want to keep using.

LiteLLM Spend Tracker has moved to internal distribution. This release exists only to move existing installations across to the internal build, and then remove itself from the way.

What it does

On startup it asks the internal distribution index whether the new build is available:

https://frs-copilot.cicd.flexways-hosting.net/frs-artifacts/vscode/llm-spend-tracker/index.json

If it is, it offers to migrate. Accepting downloads the new package, verifies its declared size and SHA-256 digest, and installs it. After you reload, this build notices the hand-over has landed and asks you to uninstall it — and keeps asking, on every start, until it is gone.

What to do

1. Accept the Migrate prompt, or run LLM Spend: Update Extension from the command palette.
2. Click Reload Window when asked.
3. Re-enter your LiteLLM API key. VS Code stores secrets per extension id, so the key does not carry across the id change. Your other llmSpend.* settings do carry across.
4. Accept Uninstall Old Build when prompted, then Reload Window — VS Code deletes the build on reload, not on the click. Or remove gpuigros.litellm-spend-tracker from the Extensions view yourself and reload. Choosing Later only silences the reminder for now: it comes back on the next start (and again after a few hours if VS Code is left running), until the old build is uninstalled.

From then on, updates are handled by the internal build. Nothing here needs to run again.

If it does not work

The internal host must be reachable from your machine — it is inside the corporate network, so a workstation off the VPN will not be able to migrate until it is back on it. The build logs the reason to the LLM Spend Tracker output channel and will retry on the next check; it does not raise an error notification on a background check.

You can always install the new build by hand from the index URL above.

Notes

• Nothing installs without a click. This build never installs anything in the background.
• The old and new extensions can coexist. They are separate products with separate settings and separate stored keys; having both installed is harmless but pointless, so remove this one once the new build is running.
• This build has no other purpose. It carries the same feature set as the release it migrates to.