Bug Description
I've now run into the same plan mode bug yet again, and frankly it's infuriating. Every time I activate plan mode it shows me an outdated plan from a previous session instead of the current state. This is the second time this has happened and it's wasting my time and my subscription fees. I'm running the latest build and have verified that there are no pending updates, yet plan mode continues to surface stale cached plans instead of the live data. This makes the feature effectively unusable.
It's honestly embarrassing that a company valued at around $300 B still hasn't been able to fix a core feature that's been broken for more than two weeks. Your own engineers touted Opus 4.5 as delivering a 2× productivity boost, but from my perspective I'm seeing a 2× decrease in productivity because I have to keep manually clearing the cached plans. I expect a more robust cache invalidation mechanism and better state management so that plan mode always reflects the current plan without reusing stale objects. Please fix this immediately.
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.0.65
- Feedback ID: 75d5008d-17a5-491f-abe6-923350cc59e9
Errors
Bug Description
I've now run into the same plan mode bug yet again, and frankly it's infuriating. Every time I activate plan mode it shows me an outdated plan from a previous session instead of the current state. This is the second time this has happened and it's wasting my time and my subscription fees. I'm running the latest build and have verified that there are no pending updates, yet plan mode continues to surface stale cached plans instead of the live data. This makes the feature effectively unusable.
It's honestly embarrassing that a company valued at around $300 B still hasn't been able to fix a core feature that's been broken for more than two weeks. Your own engineers touted Opus 4.5 as delivering a 2× productivity boost, but from my perspective I'm seeing a 2× decrease in productivity because I have to keep manually clearing the cached plans. I expect a more robust cache invalidation mechanism and better state management so that plan mode always reflects the current plan without reusing stale objects. Please fix this immediately.
Environment Info
Errors