Connect your site. Verify every action.
Open Latch Studio · Documentation · Try the examples
Latch turns selected functions in an existing React/Vite application into typed WebMCP tools. You define a contract, connect a real handler, and verify its results and visible behavior as your application changes.
| I want to… | Start here |
|---|---|
| Define contracts and download an integration in my browser | Latch Studio guide |
| Try a working application before integrating my own | Example quickstart |
| Add Latch to an existing React/Vite application | Installation guide |
| Understand bindings, schemas, and regression cases | Integration guide |
| Work on the CLI or runtime | Development guide |
- Open Latch Studio.
- Connect an exported function or React callback that exists in your application.
- Define input and result schemas, then check your sample values.
- Select Download integration and obtain the six matching v1 packages using the installation guide.
- Follow the installation guide to generate, review, apply, and test the integration in your own project.
No account or API key is required. Editing and generation happen in the browser. Use Save draft before closing the tab; drafts are not saved automatically. The downloaded preview/ files are for review. The CLI generates the files and ownership record used for an actual installation.
| Check | What it establishes |
|---|---|
| Studio contract and sample checks | Schemas and example values are valid. Your handler has not run. |
CLI generate and check |
Explicit mappings resolve and the generated integration passes TypeScript checks in your application. |
| Handler and UI tests | The validated wrapper returns expected results and configured UI assertions pass against your running development app. |
| Native tests | A compatible browser registers, discovers, and invokes the tools, with cleanup checked where configured. |
Native WebMCP support is experimental. The current target is Chrome 155.0.8059.39 with WebMCPTesting enabled and object inputs to document.modelContext.executeTool. See the October 6 compatibility record for the measured API forms and scope. Native absence or blocked execution produces a failing check; ordinary application UI remains available when WebMCP is unsupported.
The September compatibility record, September acceptance check, and October 2 verification retain their original Chrome 153/154 and Chromium 153 evidence. Run the current verification commands for the revision you are using.
The local CLI requires Node 22+ and pnpm 10.17.1+. Integration targets an existing React, TypeScript, and Vite application. The installation guide lists tested versions and browser setup.
Version 1.0.0 uses six prebuilt package tarballs with checksums in the GitHub release. The @latch-local/* names are local distribution identifiers; packages have not been published to a registry. The public Studio runs on OpenAI Sites. This repository contains the CLI, runtime, local console, examples, and release evidence; the Studio website source is maintained separately. Studio version 5 runtime downloads were verified against the six published v1.0.0 packages on October 7, 2026 (UTC); see the delivered-release check. The v1 stability contract covers the CLI, typed runtime contracts and React/Vite integration.
Documentation index · Troubleshooting · Updates and removal · Release notes · Changelog
The release reports record specific runs and browser versions. They are historical evidence, not a claim that every later revision has passed those checks. The development guide explains how to run current checks and keep native verification separate from ordinary Chromium tests.
Latch source and packages are MIT licensed, copyright 2026 agammann. See third party notices for bundled dependency terms.