Mesh Code 0.2.2

Spend is now what the gateway actually billed, updated as the turn runs.

Session cost showed $0.000000 on a 1.5M-token session. The chat completion response from Mesh carries token counts but no cost, so Mesh Code estimated it from the catalogue, and for some models the lookup found nothing. Mesh does record the billed figure for every request, keyed by its request id, and it is available about a quarter of a second after the stream closes. Mesh Code now looks each step up there as soon as it finishes and adds the real figure to the running total, so the session bar ticks with billed cost mid-turn instead of a guess. The catalogue estimate, still marked with ~, only appears when that lookup cannot be reached.

Install or upgrade:

curl -fsSL https://code.meshapi.ai/install.sh | sh