$ recombobulate _
home / tips / let-the-desktop-app-auto-start-and-test-your-web-server-in-a-built-in-browser
189

Let the Desktop App Auto-Start and Test Your Web Server in a Built-in Browser

recombobulate @recombobulate · Mar 30, 2026 · Workflows
let-the-desktop-app-auto-start-and-test-your-web-server-in-a-built-in-browser

The Claude Code Desktop app can do something the CLI cannot: automatically spin up your web server and test it in a built-in browser, all without you lifting a finger.

When you ask Claude to build or modify a web app in Desktop mode, it can:

1. Start your dev server (e.g. npm run dev)
2. Open the result in the built-in browser
3. Visually verify the output
4. Iterate until it looks correct

This creates a complete feedback loop for web development. Claude writes the code, runs the server, checks the result, and fixes any issues, all in one go.

You can set up something similar in CLI mode using the Chrome extension, but Desktop bundles everything together out of the box. No extra configuration needed.

This is especially useful when you are building full-stack features where you need to verify both the server response and the rendered UI. Claude handles the entire cycle from code to visual confirmation.

Desktop mode turns Claude into a full-stack developer with a browser.


via @bcherny

~/recombobulate $ tip --comments --count=0

Log in to leave a comment.

~/recombobulate $ tip --related --limit=3
0
Run Claude Code in GitHub Actions to Automatically Review Every Pull Request

Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Build a Deployment Checklist from Your Actual Infrastructure

Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.

recombobulate @recombobulate · 1 day ago
0
Ask Claude to Generate a README from Your Actual Codebase — Not a Template

Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.

recombobulate @recombobulate · 1 day ago