session timeline already flags repeated context blocks (nice) but when i flip compress on i still cant tell if this request is worth it til after it goes out. would love a rough '12k → 4k tokens' estimate on the request detail panel before send. mostly care for long cursor threads w/ same files pasted over and over
1 reply
+1 — repeated-context fingerprints in observe are helpful but a traffic-light 'compress worth it' on the detail view would stop me leaving compress off entirely during back-and-forth edits
This topic is closed. For private support, use the contact form.