[FEATURE] App preview in CLI

Resolved 💬 2 comments Opened Mar 26, 2026 by silviorodrigues Closed Apr 26, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

Developers who prefer the terminal workflow cannot use the app preview feature. The embedded browser, auto-verify, and screenshot capabilities are only available in the Desktop app. This means CLI users must manually switch to a browser and verify changes themselves, which breaks the flow when Claude is making iterative UI changes.

Proposed Solution

Add preview support to the CLI - either by launching a browser tab that Claude can interact with via screenshot/DOM inspection, or by supporting a headless verification mode. The launch.json configuration is already CLI-compatible, so the gap is mainly in the browser interaction layer.

Ideal experience: Claude starts the dev server, opens a browser, takes a screenshot to verify the result, and continues iterating - all without leaving the terminal session.

Alternative Solutions

Currently working around this by running the dev server in a separate terminal and manually checking the browser after each change. Other tools (like Cursor) embed a browser preview directly in their interface.

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

  1. I ask Claude Code (CLI) to update the styling of a component
  2. Claude edits the file and starts the dev server via launch.json
  3. Claude opens a browser tab, takes a screenshot, and confirms the change looks correct
  4. If not, Claude iterates without any manual intervention from me

Today, step 3 and 4 require me to manually check the browser and describe what I see back to Claude.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗