# Available context for many models being truncated

**URL:** <https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480>\
**Category:** Bug Reports\
**Created:** [October 29, 2025, 5:25pm UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480 "2025-10-29T17:25:04Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![jrista](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jrista/32/68794_2.png) [@jrista](https://forum.cursor.com/u/jrista)\
**Post date:** [October 29, 2025, 5:25pm UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480/1 "2025-10-29T17:25:04Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

This has been a long-standing problem. Many models are getting truncated context, or in other words, the nominal context of say 200k, 250k or 275k tokens, is larger than the context that actually seems to be available for use.

 ![Screenshot 2025-10-29 at 11.19.01 AM](https://us1.discourse-cdn.com/cursor1/original/3X/a/9/a9cce386e9c34030f43df6e924522b83f78f1257.png)  
 ![Screenshot 2025-10-29 at 11.22.44 AM](https://us1.discourse-cdn.com/cursor1/original/3X/7/5/75d8ea07c48b00cb1836a8279c6837a63b370782.png)

This model, Sonnet 4.5, should have a 200k context window, but it has for quite some time now, shown only 175k. The issue is even worse with GPT-5 Codex, which is supposed to have a 275k context window, but only gets 200k:

 ![Screenshot 2025-10-29 at 11.21.22 AM](https://us1.discourse-cdn.com/cursor1/original/3X/7/f/7f7955d1c23c0205ae4beabdcc060d34e1b61204.png) ![Screenshot 2025-10-29 at 11.22.35 AM](https://us1.discourse-cdn.com/cursor1/original/3X/2/0/209fd5c657c9ed53a96be7905936c97d27500faa.png)

This does seem to affect when context summarization happens. I rarely get beyond about 87% context usage anyway, maybe 90%, before context summarization happens. That means we are first not able to use all the available context before summarization occurs, and for many chats summarization may never need to occur, but also it results in summarization occurring more frequently, resulting in longer wait times while the agent summarizes context.

### Steps to Reproduce

Select model.  
View context usage.

### Expected Behavior

Available context should match the nominal context available for each model.  
Summarization should not be triggered prematurely based on an incorrect context usage meter.

### Operating System

MacOS

### Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.0.34  
VSCode Version: 1.99.3  
Commit: 45fd70f3fe72037444ba35c9e51ce86a1977ac10  
Date: 2025-10-29T06:51:29.202Z  
Electron: 34.5.8  
Chromium: 132.0.6834.210  
Node.js: 20.19.1  
V8: 13.2.152.41-electron.0  
OS: Darwin arm64 24.5.0

### Does this stop you from using Cursor

No - Cursor works, but with this issue

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [October 30, 2025, 6:28am UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480/2 "2025-10-30T06:28:00Z")

</div>

Hey, thanks for the report. This is very helpful.

The reduced available context window may be due to reserved tokens for:

- space for response generation
- space for reasoning
- system prompts and instructions
- safety buffers

However, the difference you noted (25–75k tokens) seems significant, especially if it causes premature summarization.

I’ll pass this to the team to determine whether the reduced available context is intentional or a bug. The team will check whether the context window calculations work correctly, or if there’s an issue with how the available context is calculated or displayed.

---

<div class="post-metadata">

**Author:** ![jrista](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jrista/32/68794_2.png) [@jrista](https://forum.cursor.com/u/jrista)\
**Post date:** [October 30, 2025, 4:58pm UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480/4 "2025-10-30T16:58:06Z")

</div>

I think, if you guys are reserving some amount of context for those purposes, that reservation should be made evident in this control. A different color, perhaps, in the radial indicator to show how much of the usage is for reservations. Then in the popup, report out of the total context, how much is reserve vs. user usage. IF we have a 275k context window, and 10ktok are reserved, and we then have 265ktok for our usage, that needs to be made clearer.

I do think that if you have a 275ktok window, but are losing 75k for some reason (reservation or whatever), that is a lot of context to be losing. I also can’t imagine its all reserve, so hopefully its just a calculation glitch. It does seem, though, that context gets summarized around 90% usage on that indicator. Sometimes it edges higher before summarization, but, if there is a buffer that basically forces summarization early, AND there are also reserves…we are kind of losing a lot of the context window here…

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [November 21, 2025, 4:58pm UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480/5 "2025-11-21T16:58:43Z")

</div>

Closed on November 21, 2025, 4:58pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [January 22, 2026, 4:18am UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480/6 "2026-01-22T04:18:19Z")

</div>

Opened on January 22, 2026, 4:18am UTC



---

<div class="post-metadata">

**Author:** ![jrista](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jrista/32/68794_2.png) [@jrista](https://forum.cursor.com/u/jrista)\
**Post date:** [January 26, 2026, 6:45pm UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480/7 "2026-01-26T18:45:32Z")

</div>

This is still an issue, and seems to be a progressively degrading issue. Where previously I had 176k context out of the 200k I am supposed to have, Cursor is now reporting, and as far as I can tell, operating off of for the things like auto summarization, just 164k context. So we have lost 36k context here, out of the 200k that we are supposed to have.

I don’t doubt that cursor needs some of this context on its own. However, 36k? That seems like a TON for internal usage. We need better clarity and insight into what ALL the available context for any given model is used for, both internal Cursor usage as well as usage by our own prompts and context attachments, etc.

---

<div class="post-metadata">

**Author:** ![jrista](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jrista/32/68794_2.png) [@jrista](https://forum.cursor.com/u/jrista)\
**Post date:** [January 27, 2026, 10:51pm UTC](https://forum.cursor.com/t/available-context-for-many-models-being-truncated/139480/8 "2026-01-27T22:51:53Z")

</div>

Experiencing some very odd behavior today. Sometimes when I check the context usage, it is X / 164k. However, starting today, sometimes it will show X / 200k instead. But it is not consistent. Sometimes it will initially show X / 200k, and then just a moment later if I check again, it shows X / 164k…

I have not updated cursor, I am still on 2.3.34. Baffled…
