Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

Cursor pro tip this is a game changer🔥 when context hits ~50%, type /summarize command this saves money + keeps AI responses sharp

83,404 Aufrufe • vor 1 Jahr •via X (Twitter)

41 Kommentare

Profilbild von Fili
Filivor 1 Jahr

Quick correction: /summarize is mainly for managing context window limits, not saving money Cursor supports prompt caching, which already kind of summarizes the context the main benefit is to make ai focused and stop it from being dumb

Profilbild von Tomas Francisco Firbeda
Tomas Francisco Firbedavor 1 Jahr

I’m interested, I currently spend approximately $875 per month on my ultra plan so this is good for me, but what would be the logic? Why would I “save” 50%? Thank you in advance for understanding my lack of knowledge at this point.

Profilbild von truth.phd
truth.phdvor 1 Jahr

That tip saves tokens and sanity in one move. Summarize at half context and you turn chaos into clarity. It’s like cleaning your room before it becomes a documentary about clutter. Efficiency never looked this tidy.

Profilbild von Evan
Evanvor 1 Jahr

ever notice how when you’re very close to using all the context the models decide to stop calling tools and updating files and instead just say “oh yeah i’ll do that” but do nothing

Profilbild von Fili
Filivor 1 Jahr

They get overwhelmed and become confused i think

Profilbild von Evan
Evanvor 1 Jahr

performance anxiety of a virgin having sex for the “second” time

Profilbild von Xsniper80
Xsniper80vor 1 Jahr

Composer 1 seems to do this fine on its own. It seems to summarize so well I forget it even has a context window.

Profilbild von Javier Rivero
Javier Riverovor 1 Jahr

Just open a new chat

Profilbild von WVY
WVYvor 1 Jahr

Do u have tips for a 100% ai native dev that’s making innovative frameworks

Profilbild von Fili
Filivor 1 Jahr

use the innovate custom mode

Profilbild von Sébastien Renault
Sébastien Renaultvor 1 Jahr

Isn't something Cursor should do by itself? Or maybe suggest to do when the context becomes big.

Profilbild von Justin
Justinvor 1 Jahr

Does that mean they count previous history even if it’s from the past?

Profilbild von Alex K
Alex Kvor 1 Jahr

it does it automatically if you go over 90-95%, but pretty cool anyway

Profilbild von Light
Lightvor 1 Jahr

50%???? I hit that at 94% 🥹

Profilbild von Connor
Connorvor 1 Jahr

so cool!

Profilbild von Agent Mish
Agent Mishvor 1 Jahr

Cursor pro tip - when context hits 50% you hit “CMD+T” and start a new chat

Profilbild von Arindam Majumder 𝕏
Arindam Majumder 𝕏vor 1 Jahr

Yes, I use them! Very helpful!

Profilbild von Simonas
Simonasvor 1 Jahr

lol, I barely ever use Cursor and I've had this same exact idea to offer to Gemini, Claude, etc., so they'd do it on their services

Profilbild von InsForge
InsForgevor 1 Jahr

Huge tip. I always forget to summarize and wonder why responses start turning into mush 😅 /summarize at ~50% is now going into my workflow — thanks!

Profilbild von Ammar Fahmy
Ammar Fahmyvor 1 Jahr

👌

Profilbild von alexander
alexandervor 1 Jahr

Super cool!

Profilbild von RobSkar
RobSkarvor 1 Jahr

And faster responses.

Profilbild von Fili
Filivor 1 Jahr

Yeah, you're right👍

Profilbild von Tall Tale Bro
Tall Tale Brovor 1 Jahr

Yeah I usually try to keep context under 100k

Profilbild von jonramvi.eth
jonramvi.ethvor 1 Jahr

Cool, but do you start un-max, go to max going over 50% context, then summarize when over 50; or Do you un-max, summarize and never go max; or Do you go max all the time

Profilbild von Fili
Filivor 1 Jahr

Before i knew about summarize command, i used to start un-max, then max when i hit 50% Thats a lot more expensive than using the summarize command especially for sonnet 4.5 with 1M context window I wouldnt use max mode unless the codebase is very large and task is too complex

Profilbild von Anuj
Anujvor 1 Jahr

cursor copying all the features from different IDE's This is kiro IDE feature

Profilbild von De Bear 🧸
De Bear 🧸vor 1 Jahr

Dude? 🤯 you are a lifesaver. Thanks!

Profilbild von Jonathan
Jonathanvor 1 Jahr

This is actually huge. Is this a Cursor 2 feature? So tired of doing this manually and copy/pasting to new chat.

Profilbild von Fili
Filivor 1 Jahr

its a helpful feature yea and been out on last version. But didn't get much attention for some reason.

Profilbild von Julian Ramirez
Julian Ramirezvor 1 Jahr

also strongly recommend to write atomic specifications (you can use openspec or github/speckit) so instead of summarizing you can completely reset the chat after each task this gives a better output and saves money

Profilbild von Emad Moghimi
Emad Moghimivor 1 Jahr

Great tip 👍 In Cursor 2.0 you can now also leverage multi-agent support to split large tasks into parallel agents and avoid hitting context limit too early.

Profilbild von Mykhailo Sorochuk
Mykhailo Sorochukvor 1 Jahr

Why not have the AI suggest summarizing itself? Feels like a missed opportunity to streamline things.

Profilbild von Manuel Mejia
Manuel Mejiavor 1 Jahr

👀

Profilbild von JC
JCvor 1 Jahr

Isn't it a very common function that every AI coding tools have?

Profilbild von Nhan Thai
Nhan Thaivor 1 Jahr

🤦‍♂️I've been telling it to summarize and write to markdown files and open new chat. What an idiot..

Profilbild von Fili
Filivor 1 Jahr

been doing same until I recently discovered this

Profilbild von Greg Toth
Greg Tothvor 9 Monaten

Interesting tip! I've found that capturing coding prompts via voice notes can really help eliminate context switching when working with AI tools. What's been your experience with the /summarize command so far?

Profilbild von moonliteTech
moonliteTechvor 1 Jahr

it does this automatically now. do you find it works better doing it manually ahead of time?

Profilbild von Anas
Anasvor 1 Jahr

Never use Sonnet 4.5 for any SWE work it sucks Totally only Big Talks and Benchmarks. Codex 5 is way Better

Profilbild von Second Oak
Second Oakvor 1 Jahr

Thanks, didn’t even know of this feature

Ähnliche Videos