Skip to content
| Marketplace
Sign in
Visual Studio Code>AI>Claude Eye — Screen Vision for Claude CodeNew to Visual Studio Code? Get it now.
Claude Eye — Screen Vision for Claude Code

Claude Eye — Screen Vision for Claude Code

Claude Eye

| (0) | Free
Let Claude Code see your screen. Type @eye in chat to attach a live screenshot to any message — no saving, cropping or dragging files. Screen capture over MCP, set up automatically on install.
Installation
Launch VS Code Quick Open (Ctrl+P), paste the following command, and press enter.
Copied to clipboard
More Info
Claude Eye

Claude Eye — Screen Vision for Claude Code

Let Claude Code see your screen. Type @eye and a live screenshot is attached to your message.

No saving, no cropping, no dragging image files into the chat.


What Claude Eye does

Claude Code is excellent at reading your code and terrible at seeing your screen. Anything that is not text in a file — a rendered UI, an error dialog, a chart, a video game, a design tool, an app in a language you do not read — has to be screenshotted, saved and dragged in by hand.

Claude Eye removes that. It adds an MCP server called eye that captures your screen on demand, so a screenshot becomes something you mention rather than something you manage.

Why does @eye:screen://now look broken on mobile?
Translate everything on @eye:screen://now

Claude can also decide to look on its own through the capture_screen tool, so "take a look at my screen and tell me what's wrong" works with no mention at all.

Screenshot in chat, without leaving the chat

Mention What gets attached
@eye:screen://now A screenshot of your screen as it looks right now
@eye:moonwalker://session A conversation from the Moonwalker floating panel

Type @ in the Claude Code chat and both appear in the autocomplete list alongside your files.

What you can ask

  • Debug what you can see — an error dialog, a stack trace in a terminal, a broken layout in a browser
  • Review a rendered UI — ask about spacing, contrast or hierarchy in the thing you are actually looking at, not in the CSS
  • Read an unfamiliar interface — a tool you have never used, or one in a language you do not speak
  • Translate what is on screen — subtitles, menus, game dialogue, documents
  • Understand a game — what an item does, which upgrade is worth taking
  • Summarise a chart or dense document without retyping any of it

Zero-configuration setup

Installing the extension is the entire setup. On first launch it:

  1. Finds a working Python interpreter — including the one your Python extension has selected
  2. Locates the bundled server and verifies it imports
  3. Registers eye with Claude Code through its own CLI

Nothing to paste into .mcp.json, no config file to edit, no terminal commands. An eye icon in the status bar confirms it is connected.

Restart Claude Code once after installing — it reads its MCP servers at startup.

Continue a conversation from anywhere on your desktop

Claude Eye ships alongside Moonwalker, a floating bubble that answers questions about your screen without leaving the app you are in — over a game, a film, or a full-screen document.

Questions asked there are written to a local session log, and @eye:moonwalker://session hands that conversation to Claude Code. Start a question over a game, finish it in your editor with the context intact.

Start and stop the floating panel from the command palette.

Commands

Open the command palette and type "Claude Eye":

Command What it does
Re-run setup Re-detect Python and re-register the server
Show status What was detected, and whether registration succeeded
Start / Stop the floating panel Run Moonwalker itself
Open the Moonwalker conversation View the session log

Requirements

  • Python 3.10+
  • Claude Code — the CLI or the VS Code extension
  • pip install pillow for screen capture (PySide6 is used as a fallback, and is required only for the floating panel)

Privacy

Screenshots are captured only when you mention @eye or Claude calls capture_screen. They go straight into that conversation — never written to disk, never sent anywhere else, no telemetry of any kind. The session log holds text only; screenshots are never stored in it.

The only thing the extension writes outside itself is one entry, mcpServers.eye, in your Claude Code config. Deleting that entry fully uninstalls the integration.

Settings

Setting Default Purpose
claudeEye.pythonPath auto Interpreter used to run the server
claudeEye.moonwalkerPath bundled Folder containing the moonwalker package
claudeEye.autoRegister true Register with Claude Code on startup
claudeEye.showStatusBar true Show the status bar item

Troubleshooting

@eye does not appear in the @ menu. Restart Claude Code — MCP servers are read at startup. Then run Claude Eye: Show status.

"No usable Python found." Install Python 3.10 or newer, or point claudeEye.pythonPath at your interpreter.

Registration failed. Run Claude Eye: Show status → Show log. If Claude Code was open while the config was written, it can overwrite the entry; the extension prefers the Claude CLI precisely to avoid this.

Licence

MIT — see LICENSE.

  • Contact us
  • Jobs
  • Privacy
  • Manage cookies
  • Terms of use
  • Trademarks
© 2026 Microsoft