Repository navigation
[BUG] /compact command does not compress - context increases instead #17557
Description
Description
The /compact command does not actually compress the context. Instead, the context token count increases after running /compact, indicating the command either fails silently or does nothing at all.
Evidence
Before /compact:
- Context: 50,241 tokens (25%)
After /compact:
- Context: 51,405 tokens (25%)
- Change: +1,164 tokens (context INCREASED)
No visual feedback was shown in the TUI during compaction (no "compacting" status), and no compression actually occurred.
Related Issues
This appears to be related to or a more severe version of:
- Compacting status never appears in TUI #16395 - "Compacting status never appears in TUI"
- [BUG] Compactation Fails Agent forgets everything #8394 - "Compactation Fails Agent forgets everything"
- Compaction loses entire conversation #14368 - "Compaction loses entire conversation"
Steps to Reproduce
- Start a session with moderate context (25%+ used)
- Note the current token count (e.g., via TUI status or
/compactprompt) - Run
/compact - Check token count again
- Observe that context has NOT decreased (may even increase)
Expected Behavior
- Context tokens should DECREASE after
/compact - TUI should show a "compacting" status during operation
- Compression should actually occur
Actual Behavior
- Context tokens INCREASED (+1,164 tokens)
- No TUI feedback during compaction
- No compression occurred
Environment
- OpenCode version: (latest - please specify in comments)
- OS: Linux
- Model: GLM-5 (zai-coding-plan/glm-5)
Additional Context
This was tested in a session with:
- ~80 messages exchanged
- 1 manually compressed block (via
compresstool) - Git operations, file reads/writes, and GitHub searches performed
The manual compress tool (agent-side compression) works correctly, but the user-facing /compact command does not.
Reacted by Anatolii Papenko, Jost Triller, Meirdrarel and Zagig Yragerne
Metadata
Metadata
Assignees
Labels
No labels
Activity
guyinwonder168 commentedon Mar 15, 2026
Update: DCP Plugin vs OpenCode Core Distinction
After further investigation, I want to clarify the distinction between two separate compression mechanisms:
compresstool@tarquinen/opencode-dcp)/compactcommandKey Findings:
The
compresstool I have access to comes from the Dynamic Context Pruning (DCP) plugin, evidenced by:<dcp-message-id>and<dcp-system-reminder>@tarquinen/opencode-dcpis installedThe DCP plugin's
compresstool works correctly - I successfully used it to compress earlier conversation ranges (confirmed by compressed block count increasing)OpenCode's built-in
/compactcommand is the broken one - it shows no TUI feedback and doesn't actually compress the contextThis means:
/compactcommand needs to be fixed in OpenCode coreRecommendation:
The OpenCode team should investigate why the native
/compactcommand doesn't trigger actual compression, while the DCP plugin'scompresstool works as expected.lumlase commentedon Mar 19, 2026
I'm encountering the same issue. I was also using the latest version of OpenCode v1.2.27 , use opencode-web the context
compactcommand isn't responding , I've tried using GLM-5 and GPT-5.4 Nothing is working.clousky2020 commentedon May 14, 2026
The issue still exists in version 1.14.50 and has not been fixed.
4riful commentedon May 18, 2026
i am using @tarquinen/opencode-dcp plugin its working fine for me thanks mate @guyinwonder168
privettoli commentedon Jun 25, 2026
Faced this with 1.17.10.
sanketblin-stone commentedon Jul 19, 2026
facing the same issue with opecode desktop app
github-actions commentedon Sep 19, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.