Changelog

Tracker releases are immutable: once a version is published at /v/<version>/t.js its content never changes, so a pinned script with Subresource Integrity keeps working.

November 11, 2026 — AI assistant and “what changed”

• Remote MCP server. Connect Claude, Cursor or VS Code with a read-only key and ask about your site. Eight tools; totals only; every answer carries its trust grade. Set it up.
• What changed. A rule-based comparison with the previous period, on the Overview page and in your assistant: what moved, what moved it, and how sure we are.

November 11, 2026 — Heatmaps (tracker 0.2.0 and 0.2.1)

• Click density, rage clicks, dead clicks and scroll reach, drawn on your own page. Off by default; one switch per site. Read more.
• 0.2.1: the overlay token travels in a header and is tied to the person who opened it; text selection is no longer a dead click; truncated URLs never end in half a character.

November 10, 2026 — Tracker 0.1.1

• Retries no longer stall after a long backoff; the last soft navigation is sent when the page closes.
• Excluded paths, late consent and server-rendered queues are handled exactly as documented.
• Measured loss no longer counts suspicious traffic as lost.

November 9, 2026 — Dashboard, API and revenue

• The dashboard: overview, sources with an AI channel, pages, countries, devices, events, realtime, the trust report, AI & crawlers, workspaces and members.
• REST API with an OpenAPI schema and scoped keys.
• Stripe revenue: restricted keys only, credited to the visit that reached checkout.
• npx @plaintrace/cli init for Next.js, Remix, SvelteKit, Astro, Vite and HTML.

November 7, 2026 — First release (tracker 0.1.0)

• Cookieless browser tracker with a daily, salted visitor hash.
• Collector that answers only after an event is durably queued, and never lets a raw IP address out.
• Server SDK: first-party proxy, crawler reads, measured loss and server-side events.