Latten

What is @latten/installer?

@latten/installer is a Codex-ready MCP server that provisions an observe-only Latten brain, scans TypeScript apps for LLM/data/API crossings, guides the agent to instrument @latten/sdk, verifies real traffic, and returns a receipt plus claim URL.

See it on a live graph — no signup →

Agent-native setup

Add the MCP server with LATTEN_URL. If no token exists, the agent calls provision once and gets a claim URL for the human.

Static scan, human-reviewed diff

The scan proposes candidate crossings; the coding agent applies judgment and opens a reviewable PR a human approves.

Proof after traffic

The installer verifies real crossings and returns a receipt: reached domains, models, attribution, cost, fixes, and zero-PII-values posture.

How it works

  1. 1. Add MCP Configure npx -y @latten/installer in Codex, Claude, or Gemini.
  2. 2. Provision Mint an observe-only brain when no LATTEN_TOKEN exists.
  3. 3. Scan and instrument Find high-confidence TypeScript crossings and place @latten/sdk calls.
  4. 4. Verify and receipt Confirm real crossings and hand the human the receipt and claim URL.

Common questions

Does @latten/installer edit code by itself?

No. The coding agent proposes the diff and the human reviews it. The console never edits the repo.

What languages does scan support?

The current scan frontier is TypeScript.

Where can the token be sent?

Only to the configured Latten host or explicit allowed hosts, over HTTPS except localhost development.

See a live graph — no signup Instrument your app → All guides