# Reflow

> Reflow proves an AI's PR works in a real browser before merge. It is built for coding agents such as Claude Code, Cursor, and Codex, and for the developers driving them.

Reflow's agent surface is one streamable-HTTP MCP endpoint: https://mcp.reflow.io/mcp. It uses OAuth 2.1 with browser sign-in on first use, so there is no API token to paste.

The endpoint exposes 38 hand-written tools for identity and guidance, flows and DAGs, runs and results, live browser sessions, and harnesses and containers. Provider keys and API tokens stay in the dashboard, not MCP.

Flows are markdown files with YAML frontmatter, plain-language intent, and named ```ts step="..." fences. Step bodies contain deterministic RFL, Playwright TypeScript, or remain empty for agent-driven execution. Runs use a real cloud browser and the team's own model key: customers pay their model provider, never a token markup.

Evidence returns through the same MCP surface: tail_run streams step events and the terminal verdict, get_run_screenshot returns short-lived signed URLs, named snapshot checkpoints are perceptually diffed against approved baselines, and per-run virtual mailboxes support magic-link and OTP journeys.

Self-heal is enabled by default. If a scripted step fails, the agent takes control from the failed page state; a successful recovery attaches proposed RFL to the run and never rewrites the source flow. Set self_heal: false to disable it.

The GitHub Action runs selected flows against a pull-request preview and posts one merge-blocking check per flow with screenshots and visual diffs.

A cold-agent canary gave a fresh agent only the tool descriptions. It authored login-screen-loads, ran it, and reported PASS in 19 tool calls for $0.44; the harness verified runs.status='succeeded' in the database rather than trusting the transcript.

## Connect

- [MCP endpoint](https://mcp.reflow.io/mcp) — Connect any streamable-HTTP MCP client with OAuth 2.1 browser sign-in.
- [MCP reference](https://reflow.io/docs/mcp) — Connection commands, the agent loop, evidence, recovery, and all five tool groups.

Claude Code: `claude mcp add --transport http reflow https://mcp.reflow.io/mcp`

Cursor, Windsurf, Claude Desktop, and Codex take the endpoint URL. VS Code: `code --add-mcp "{\"name\":\"reflow\",\"type\":\"http\",\"url\":\"https://mcp.reflow.io/mcp\"}"`

## Start

- [Getting started](https://reflow.io/docs/getting-started) — Connect an agent, author a first flow, and run it in a browser.
- [Flow format](https://reflow.io/docs/flow-format) — Structure YAML frontmatter, intent, and named step fences.
- [Reflow language](https://reflow.io/docs/reflow-language) — Write readable deterministic RFL statements and targets.
- [Guiding the agent](https://reflow.io/docs/guiding-the-agent) — Give an agent the context it needs to author and interpret flows.
- [Test accounts](https://reflow.io/docs/test-accounts) — Cover sign-in, magic-link, and OTP journeys with per-run mailboxes.
- [GitHub Action](https://reflow.io/docs/github-action) — Run selected flows against PR previews and return merge-blocking evidence.
- [Playground](https://reflow.io/docs/playground) — Record flows against a live cloud browser with validated selectors.
- [Self-target](https://reflow.io/docs/self-target) — Execute flows directly on the browser image with inline CLI steps.
- [Autoheal](https://reflow.io/docs/autoheal) — How Reflow repairs a bounded class of selector failures and returns the change for review.
- [Visual testing](https://reflow.io/docs/visual-testing) — Snapshot checkpoints, baselines, and the perceptual compare loop.
- [API and tokens](https://reflow.io/docs/api) — The /v1 API, PAT scopes, and team binding.
- [Docs index](https://reflow.io/docs) — Full documentation map.

## Optional

- [Pricing](https://reflow.io/pricing) — Reflow plans.
- [Features](https://reflow.io/features) — Product capabilities.
- [For agents](https://reflow.io/agents) — The machine-facing overview, tool surface, and cold-agent proof.
- [Blog](https://reflow.io/blog) — Product and engineering notes.