Compaction happens at low context usage (e.g. 20%) and don't get reported as an actual checkpoint?
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 11.2k
- Forks
- 1.9k
- Avg merge
- 14h 16m
- Merged PRs (30d)
- 6
Description
Describe the bug
I keep seeing gpt-5.6 sol getting compacted at like 20% context usage. It shows a message like this and if I run /session checkpoints like it says in the message it says no checkpoints. Well, which is it, did you just add a checkpoint to the session or not?
Affected version
1.0.81
Steps to reproduce the behavior
- Use GPT-5.6 Sol for awhile and see it auto-decide to compact
- See the session compact message
- Type
/session checkpoints
Expected behavior
What's the point of having 80% available context when you force compaction at 20%.
I also expect that if you do a compaction it shows up in the list instead of this gaslighting message about there being a checkpoint and then doing the exact recommended command shows nothing.
Additional context
Windows Terminal on x64 win11
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior with GPT-5.6 Sol: observe the automatic compaction message, then run /session checkpoints as described. Trace the compaction and checkpoint-reporting entry points, and consider the issue complete when the compaction threshold and message are consistent and the resulting checkpoint appears in the listing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100