# Cursor usage spikes are becoming impossible to explain **URL:** \ **Category:** Feature Requests\ **Created:** [May 21, 2026, 3:07pm UTC](https://forum.cursor.com/t/cursor-usage-spikes-are-becoming-impossible-to-explain/161244 "2026-05-21T15:07:31Z")\ **Posts on this page:** 1\ **Showing post:** 5
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [May 22, 2026, 7:01am UTC](https://forum.cursor.com/t/cursor-usage-spikes-are-becoming-impossible-to-explain/161244/5 "2026-05-22T07:01:19Z")
This is fair feedback. Agent mode can consume significantly more tokens than you’d expect because each step may re-read files, expand context, and issue tool calls that all count toward usage. Long sessions compound this since conversation history grows with every turn. Right now, the usage page at [cursor.com/settings](https://cursor.com/settings) shows a daily breakdown by model and category (included vs. on-demand), but it doesn’t provide per-request granularity — that’s the gap you’re describing. A few practical things that may help in the meantime: - Start fresh chats for new tasks instead of continuing long sessions. Each turn carries forward the full conversation history, which inflates subsequent request costs. - Check your model selection. Max mode and premium models consume tokens faster. [Auto mode](https://cursor.com/help/models-and-usage/available-models) picks the most appropriate model for each task, which often reduces token spend. For the dashboard improvements you’re describing (model used, context size, token cost per request), this has been discussed in detail here: [Context Window Inspector & Agent Usage Profiler](https://forum.cursor.com/t/context-window-inspector-agent-usage-profiler/152223). Voting on that thread helps our product team prioritize it. --- _[View the full topic](https://forum.cursor.com/t/cursor-usage-spikes-are-becoming-impossible-to-explain/161244)._