Title: Add screen capture and variable inspection capabilities for debugging to Claude Code

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Description:

When debugging UI applications, Claude Code is significantly limited by not being able to:

1. See the screen - I have to describe visual issues to Claude, which is imprecise and time-consuming. If Claude could capture screenshots or see the current application state, it could immediately identify visual bugs, rendering issues, or UI state problems.
2. Monitor variables during execution - Claude can only infer application state from console logs and file contents. A direct integration with browser DevTools or a debugger would allow Claude to:

• Set breakpoints
• Inspect variable values at each step
• Trace execution flow
• View the actual runtime state of objects

Use Case:

When debugging a data persistence issue in a spreadsheet component, I spent hours iterating with Claude because:

• Claude couldn't see that the spreadsheet appeared empty (had to describe it)
• Claude couldn't inspect the actual values flowing through callbacks
• Claude had to add console.logs, rebuild, and ask me to report outputs - a slow feedback loop

With screen access and variable inspection, Claude could have traced the exact data values at each step and found the bug directly.

Suggested Implementation:

• Integration with browser DevTools Protocol for web apps
• Screenshot capture capability via Puppeteer/Playwright
• Optional Electron/app window capture

What Should Happen?

Claude could debug much more efficiently and that would result in much higher user satisfaction vs. frustration since it wouldn't need ME to keep reporting how the app looked as changes are iterated!

Error Messages/Logs

Steps to Reproduce

Take just about any buggy application code base and try to fix the errors one by one without involving the users effort unnecessarily. The information on the screen should be readily available to Claude's debugging process as should the intermediate variables.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

Claude Code version 2.1.15

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_