/run

Starts and drives the project app so you can actually see a change take effect (not just tests).

Starts and drives the project app so you can actually see a change take effect (not just tests). [Skill] See 'Run and verify your app' in the skills docs. Requires v2.1.145+.

✅ WHEN TO USE IT?

See a change work in the real flow

After a UI change, use /run to actually start the app and see the change in the browser, instead of just trusting green tests.

Check a freshly set up project

On a newly cloned project, use /run to see whether the app even comes up from a clean environment.

⛔ WHEN NOT TO?

Only unit tests matter

/run actively starts and drives the app — for plain test runs with no running app needed, that's unnecessary overhead.

Better: Run the test suite directly (e.g. npm test) without starting the app.

SOURCES

Claude Code Doku (offiziell) ↗ code.claude.com