claude-code - 💡(How to fix) Fix More granular zoom/font size controls — code vs chat text sizes are inconsistent [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#48841Fetched 2026-04-16 06:49:26
View on GitHub
Comments
1
Participants
2
Timeline
3
Reactions
0
Timeline (top)
labeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

The font size zoom levels are too coarse. When Claude Code text is set to a comfortable size, the next step up is disproportionately large. There's no middle ground.

Additionally, the text size in code blocks/terminal output is noticeably smaller than regular chat text at the same zoom level, making it hard to calibrate a single setting that works well for both.

Request: Add more granular zoom increments (e.g. 10% steps instead of large jumps), and/or separate font size controls for code vs. prose content.

extent analysis

TL;DR

Implementing more granular zoom increments, such as 10% steps, could provide a better user experience by offering more precise control over font sizes.

Guidance

  • Consider introducing separate font size controls for code blocks/terminal output and regular chat text to address the discrepancy in text sizes at the same zoom level.
  • Evaluate the current zoom increment logic to determine the feasibility of implementing smaller step sizes, such as 10% increments, to provide more granular control.
  • Assess the impact of such changes on the overall user interface and experience, ensuring that the adjustments do not introduce unintended consequences.
  • Review existing user feedback and preferences to inform the decision on the optimal zoom increment and separate control implementation.

Example

No specific code example can be provided without more context on the current implementation, but a hypothetical approach might involve modifying a font-size variable in CSS or a similar styling mechanism to accept more precise increments.

Notes

The solution may require adjustments to both the frontend and backend, depending on how the zoom functionality is currently implemented. It's also important to consider accessibility guidelines when making changes to font sizes and zoom levels.

Recommendation

Apply a workaround by introducing separate font size controls for code and prose content, as this addresses the primary concern of text size discrepancy and provides a more tailored experience for users.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING