import { Architecture } from "@/components/Architecture"; import { Faq } from "@/components/Faq"; import { Logo } from "@/components/Logo"; const RELEASES = "https://github.com/vincentvella/devloop/releases/latest"; const REPO = "https://github.com/vincentvella/devloop"; const MCPORTER = `${REPO}#when-mcp-is-blocked-enterprise-sandbox--drive-devloop-via-mcporter`; const agentRules = `For browser or Expo / React Native feature work, use **devloop**: - dev_start, then browser_navigate (or native_open for iOS/Android). - After a change, reproduce it with \`repro\` and read the result — never claim a fix works without exercising it in the running app. - browser_snapshot for clickable element refs; \`diagnose\` + get_logs_around to line up a console error with the matching server stack trace from the same moment. - Done = verified live in devloop: no console/page errors, the expected network calls succeeded, the UI reflects the change. - Setup stays yours: devloop names the missing toolchain + the fix command — it diagnoses, never installs. Run it, then rebuild.`; const cards = [ { h: "One timeline", p: "Server stdout/stderr and browser console/network/page-errors share one clock — correlate cause and effect across the stack.", }, { h: "Web and native", p: "Drive a browser, or an Expo/React Native app on the iOS simulator or an Android emulator — live device in the pane, native logs + RN network on the same timeline, snapshot/tap via idb/adb.", }, { h: "repro", p: "Run an action sequence (navigate / click / type / eval), wait for network idle, and get everything that happened on both sides.", }, { h: "Per-app scoping", p: "Run several projects at once; query logs by app name, not just the active pane. Each project gets isolated browser storage.", }, { h: "Shared daemon", p: "Run one devloop-mcp daemon and many agents/sessions share it over HTTP/SSE — one browser, one dev server, one timeline.", }, { h: "Agent-drivable", p: "Headless stdio for Claude Code, MCP-over-HTTP for the cockpit + daemon, or call the tools as plain shell commands via mcporter when MCP is sandboxed.", }, ]; export default function Home() { return ( <>

Devloop

Browser control + dev-server logs on one correlated timeline — so a browser console error and the backend stack trace from the same moment sit side by side. For AI agents and humans.

Download the app GitHub npm

Watch it work

{/* biome-ignore lint/a11y/useMediaCaption: silent product demo loop */}

Screenshots

{/* biome-ignore lint/performance/noImgElement: static marketing screenshot */} Devloop cockpit: a browser pane beside a unified, filterable timeline of correlated server and browser logs
{/* biome-ignore lint/performance/noImgElement: static marketing screenshot */} A Devloop repro result rendered inline on the timeline {/* biome-ignore lint/performance/noImgElement: static marketing screenshot */} Devloop running multiple browser panes, each with its own dev server

Use it with Claude (MCP)

          claude mcp add devloop --scope user -- npx -y devloop-mcp
        

Then, in any project: “dev_start and repro a navigate to /projects.” It starts your dev server, drives the browser, and returns a correlated slice of both sides. Need one instance shared across agents? devloop-mcp daemon. MCP blocked by an enterprise sandbox? Drive the tools as shell commands — see the{" "} mcporter guide.

Make your agent reach for it

Drop this in your CLAUDE.md (or any agent's rules file) so it drives features through Devloop and verifies them live — instead of guessing from the code:

          {agentRules}
        

The full copy-paste block is in the{" "} README.

Or run the cockpit

A desktop app: tabbed browser panes (and Expo iOS/Android targets) beside a unified, filterable timeline, a repro builder, an element picker, and pop-out browser windows. Grab your platform:

macOS .dmg Windows .exe Linux .AppImage Linux .deb

What it does

{cards.map((c) => (

{c.h}

{c.p}

))}
); }