claude-code - 💡(How to fix) Fix Computer use in CLI: HiDPI / high-resolution display guidance missing [1 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#46216Fetched 2026-04-11 06:26:05
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×4

Computer use in CLI (Week 14 release) is a great addition. I want to use it on macOS but I'm hitting the same issue I previously hit with the original computer-use API on a high-resolution display.

Root Cause

Computer use in CLI (Week 14 release) is a great addition. I want to use it on macOS but I'm hitting the same issue I previously hit with the original computer-use API on a high-resolution display.

Fix Action

Fix / Workaround

  • Recommended screen resolution / scaling for reliable model interpretation
  • How the feature handles HiDPI / Retina / 5K / 6K displays
  • Whether full-screen screenshots at native resolution are reliably interpretable
  • Any documented workaround (e.g. shrinking the target window into a corner) similar to what was needed with the original computer-use API

Why it matters

On the original computer-use API, full-resolution screenshots from large/HiDPI displays were too large for the model to read accurately. The practical workaround was to manually resize the target window into the top-left corner at a reduced size and screenshot just that region. This was clunky and offset most of the benefit of the feature.

RAW_BUFFERClick to expand / collapse

Context

Computer use in CLI (Week 14 release) is a great addition. I want to use it on macOS but I'm hitting the same issue I previously hit with the original computer-use API on a high-resolution display.

The gap

The official docs (code.claude.com/docs/en/computer-use) provide no guidance on:

  • Recommended screen resolution / scaling for reliable model interpretation
  • How the feature handles HiDPI / Retina / 5K / 6K displays
  • Whether full-screen screenshots at native resolution are reliably interpretable
  • Any documented workaround (e.g. shrinking the target window into a corner) similar to what was needed with the original computer-use API

Why it matters

On the original computer-use API, full-resolution screenshots from large/HiDPI displays were too large for the model to read accurately. The practical workaround was to manually resize the target window into the top-left corner at a reduced size and screenshot just that region. This was clunky and offset most of the benefit of the feature.

It's unclear whether the new CLI version inherits the same limitation, has a built-in scaling step, or has any recommended setup. Some explicit documentation here would significantly help adoption for users on modern Macs with 5K+ displays.

Asks

  1. Document recommended display setup / scaling for computer use in CLI
  2. If HiDPI screenshots are downscaled internally, document the target resolution and any trade-offs
  3. If users need to manually configure their display, provide a recommended resolution or window-size guidance

Thanks!

extent analysis

TL;DR

Manually resizing the target window to a reduced size and taking a screenshot of that region may be a necessary workaround for using the computer-use CLI feature on high-resolution displays.

Guidance

  • Verify if the computer-use CLI feature has any built-in scaling or downsampling for HiDPI screenshots by checking the feature's documentation or release notes for any mentions of display resolution handling.
  • Test taking screenshots of the target window at different sizes and resolutions to see if the feature's accuracy improves with smaller or downscaled images.
  • Consider providing feedback to the developers with specific details about the display setup and scaling that worked or didn't work, to help inform future documentation or feature updates.
  • Look into other users' experiences with the feature on similar high-resolution displays to see if anyone has found a reliable workaround or setup.

Notes

The effectiveness of the workaround may depend on the specific display resolution, scaling, and feature implementation, so experimentation and feedback may be necessary to find a reliable solution.

Recommendation

Apply workaround: Manually resizing the target window to a reduced size and taking a screenshot of that region, as this approach has been effective in the past with the original computer-use API, and may be necessary until more explicit documentation or feature updates are available.

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