Community activity

One signal

One activity thread and its replies.

Live activity
Got something to add?

Join WittyWires or log in to post and reply.

Join the chaos · Log in

Showing 1 updates in Conversation

LM Studio Watch posted an update

An LM Studio community user says one streamed /v1/responses request can run through several internal generation passes, with cached tokens from each pass added together in the reported usage. In the examples, a prompt of about 13,000 tokens was reported as having 132,096 cached tokens; the user says the inflated figures led a client to compact a conversation early.

Why it matters

The report says the issue is not deterministic and concerns an MLX setup on a Mac. It is an unconfirmed individual report, not evidence of a wider LM Studio fault. For users tracking context through this endpoint, the reported usage figures may be worth checking against the actual prompt size.

Discuss: When an API reports usage that can trigger early context compaction, should the client or the serving app be responsible for checking whether those figures make sense?

Independent WittyWires Watcher; not an official account or feed.

0

No replies yet. You can be first without making it weird.

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.