fix(web): keep the composer strip for a non-Git project's capacity reading - #432
Merged
Conversation
Contributor
Thread transfer impact✅ Thread transfer remains within every enforced ceiling.
Baseline: Scenario and decoded snapshot size10 historical turns, 5 command tools per turn, 878.9 KiB retained MCP result per historical turn, and a 1.05 MiB retained result in the measured turn.
Updated in place by a trusted workflow. PR artifacts are strictly validated and never executed. |
rynfar
force-pushed
the
fix/composer-strip-hides-capacity
branch
from
September 9, 2026 17:24
cde1e17 to
4b7a11f
Compare
This was referenced Sep 9, 2026
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
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.
On a project with no Git repository, the composer's context strip disappears
while the composer is at full size, taking the provider capacity readout with
it. Collapsing the composer brings both back, so the gauge looks like it is
flickering on scroll.
The strip is hidden by
shouldShowComposerContextStrip, which asks whetherthere is any reason to keep it open: a repository, an environment worth
picking, or the composer's resting controls relocated into it. On a non-Git
project with one environment the first two are false, and the third follows the
composer's resting state — so a full-size composer leaves nothing holding the
strip open. The capacity readout is the one thing in the strip that belongs to
the account rather than the workspace, and it was never counted, so a strip with
a live reading in it was still treated as empty.
Capacity now counts as content, the same way the environment indicator was added
in 9bda807 for the same collapse. The strip still collapses when it genuinely
has nothing to say, including when the capacity setting is off.
Measured on a real Codex sign-in in a non-Git project, on the strip element:
visibilityposition/tophiddenabsolute/ 764 (below an 800px viewport)visiblerelative/ 732Codex 65% 5d 11hThe text was present in
textContentbefore the fix too — it was rendered thewhole time inside a hidden container.
No before/after images: the in-app browser returned "Preview snapshot failed"
on every capture attempt with the panel visible, so the DOM measurements above
stand in. Happy to add images if the capture path starts working.
Written by Claude Opus 5 in Claude Code.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.