Prooflane is an AI-native WebUI stress lab. Instead of leaving browser experiments scattered across scripts, CI logs, and hidden artifacts, it gives you one place to launch a target, read the result, and only then move into governed proof and deeper review.
No. Playwright is part of the stack, but the repo also includes:
Start here if you already feel the pain of:
Yes. Start with:
That path is public-safe and read-only.
Yes, for the key shell surfaces.
The current operator shell can switch navigation, onboarding, and help copy between English and Simplified Chinese. That bilingual shell now reaches the highest-traffic launch/result/review surfaces plus key operator chrome such as Flow Studio guidance, parameter panels, dialogs, and notifications. The deeper product and contract docs remain English-first so the public repo keeps one canonical documentation surface.
Yes, through MCP compatibility.
Prooflane exposes a read-mostly MCP surface that Codex, Claude Code, and other MCP-capable clients can call. That is a protocol compatibility statement, not an official partnership claim.
No.
The generated client is real, but it is currently harness-scoped and lives under the repo’s internal test surfaces. The safest builder entry today is the OpenAPI + direct HTTP contract described in docs/reference/integration-entrypoints.md.
CI is good at saying pass or fail. It is much worse at being the product surface where people understand what happened, why it failed, and what to do next. Prooflane tries to connect both.
Use this order:
Use this order:
Because the repo is not only shipping code. It is also opening up a productized way to think about WebUI stress testing, governed proof, AI-assisted review, and MCP-ready workflows. If that direction matters to you, following early is rational.