Bug
After an auto-compaction, /status (and the post-message status card) shows the pre-compaction context size on the "Context" line, not the current size.
Example
⚙️ Compacted (106k → 36) • Context 36/200k (0%)
then on the next status:
🧮 Tokens: 6 in / 124 out
📚 Context: 76k/200k (38%) · 🧹 Compactions: 1
The 76k / 106k figures shown immediately after compaction are stale — they reflect what was in context right before compaction fired, not what's actually there now (which is the summary, ~a few hundred to a few thousand tokens).
This is misleading: users read "Context: 106k/200k (53%)" and think compaction didn't work.
Expected
The "Context" field should reflect the current post-compaction context size.
The pre-compaction peak is useful but belongs on the Compactions line as a delta, e.g.:
📚 Context: 36/200k (0%)
🧹 Compactions: 1 (last: 106k → 36)
Repro
- Let a session grow to >100k tokens.
- Trigger
/compact or auto-compact.
- Run
/status — observe Context line still shows pre-compaction figure until the next user turn refreshes it.
Notes
- Reported in WhatsApp group surface, but the status card formatter is shared, so this affects all channels.
- Likely a stale read of the context window snapshot taken before the compaction summary replaces history.
Bug
After an auto-compaction,
/status(and the post-message status card) shows the pre-compaction context size on the "Context" line, not the current size.Example
then on the next status:
The 76k / 106k figures shown immediately after compaction are stale — they reflect what was in context right before compaction fired, not what's actually there now (which is the summary, ~a few hundred to a few thousand tokens).
This is misleading: users read "Context: 106k/200k (53%)" and think compaction didn't work.
Expected
The "Context" field should reflect the current post-compaction context size.
The pre-compaction peak is useful but belongs on the Compactions line as a delta, e.g.:
Repro
/compactor auto-compact./status— observe Context line still shows pre-compaction figure until the next user turn refreshes it.Notes