[CONTEXT MANAGEMENT] Suggestion on better context management.
Resolved 💬 6 comments Opened Aug 31, 2025 by junaid1460 Closed Jan 5, 2026
Problems:
- Tasks do work without good prior context.
- Often agent is solving some unrelated problem that's required to solve current problem
- Compact will just poorly squash everything.
Solution:
- Provide a branching ability within Chat. Then let us merge the branch back to original.
pros:
- it's in user's control
- regular user won't get affected
cons:
- Effect is big enough ( Although if we think about it modelling wise, I think all we need to do is keep track branch message and squash until and add message )
- Might not help regular user
- Automatic understanding and pruning non essential toolcalls and agent talks
pros:
- User's don't have to worry
- Users would just get the benefit from day 1
cons:
- Would affect existing users and their workflows
- Allow me to hack, or allow me to build POCs on top of claude code.
pros:
- you'd get free ideas
- I could subscription usage to model things
cons:
- You might be hesitant considering the business model of yours. :P
This issue has 6 comments on GitHub. Read the full discussion on GitHub ↗