fix(compound): remove overly defensive context budget precheck#279
Merged
kieranklaassen merged 2 commits intomainfrom Mar 16, 2026
Merged
fix(compound): remove overly defensive context budget precheck#279kieranklaassen merged 2 commits intomainfrom
kieranklaassen merged 2 commits intomainfrom
Conversation
The Phase 0 vibes-based heuristic warned users and forced a mode choice even with 80%+ context remaining. Full mode now runs by default; compact-safe mode stays available on explicit request. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #278 — reported by @NoamTenne on X
Root cause
The heuristic told Claude to "check how long the current conversation has been running" and guess whether context was constrained. There's no actual token count API, so Claude erred on the side of caution and recommended compact-safe mode for any non-trivial conversation. Especially aggressive on Codex.
What changed
Replaced the 35-line Phase 0 block (warning + choice prompt) with a 3-line default: always run full mode, compact-safe on explicit request only.
Test plan
/ce:compoundin a fresh session — should go straight to full mode with no warning/ce:compoundin a long session — should still go straight to full mode/ce:compound --compact— should use compact-safe modePost-Deploy Monitoring & Validation
No additional operational monitoring required: this is a prompt-only change with no runtime impact.