[BUG]: Context Command Consumes Entire Session Usage and Takes Over 3-4 Minutes to Complete
Status Open
Reported on v2.1.268
Maintainer reply None cached
Activity 0 comments · opened Sep 18, 2026
Bug Description
I used the context command, and it took an unusually long time to complete. I initially assumed this was a static function, so I was surprised that it appeared to take significant processing time. Does the context command also use AI processing?
I left the command running, but it took more than 3-4 minutes to complete, and my current session's usage was completely consumed (100%). This appears to be unexpected behavior and may be a serious issue. Please investigate and resolve this as soon as possible.
Additionally, what happens to the session usage that was consumed due to this issue? Will the usage from the affected session be restored or otherwise accounted for?
Environment Info
- Platform: linux
- Terminal: kitty
- Version: 2.1.268
- Feedback ID: a1a76521-11e7-4e7b-afad-06e1a99c2feb
Errors
[]