AI spend now counts the conversations we could not save

When the assistant cannot reach the place it keeps conversations, it answers you anyway. That is deliberate: a brief database problem should cost you your history, not your assistant. Those turns are answered by the same AI provider as any other, and they cost the same.

Until now they were the one thing AI spend did not count. The figures were built from saved conversations, and a turn with no saved conversation left nothing to count — so the total sat slightly under what had really been used, and it did so precisely during the moments something was going wrong.

What changes on your screens

Nothing moves, and nothing you did before works differently. The numbers in AI spend — and in the console’s per-workspace view — now include those turns, so they are a fuller account of the month than they were.

If you compare a month against a figure you noted earlier, expect the new one to be the same or a little higher. That difference is coverage we were missing, not new usage and not a correction to what you are charged.

What we do not go back and fix

Turns answered this way before today were never recorded anywhere we can read, so there is nothing to recover. Past months keep the figures they were given; the fuller count starts from now.

As before, these are measurements rather than a bill — your invoice still comes from your agreement with us.