What changed, and why it matters.

Add a website and Set-up hands you a snippet made for it. Its visits count only on that domain and its subdomains, and plans now hold to their site counts.

After 14 days the workspace turns read-only: dashboards and everything written stay, new AI pauses. A notice counts down the last three days.

The snippet now switches session recording off itself, so a setting elsewhere can never start recording your visitors.

Erasing a visitor now clears Lissoss's cached copies as well as its database — and only ever touches your own workspace's sites.

Four reviews — access and tenancy, injection, the public surface, the database and secrets. Every critical and high finding was re-checked in the code and fixed.

Dashboards opened after an idle pause used to wait on a full refetch. They now open from a shared snapshot in a few seconds.

A new sidebar with your workspace, search on / or ⌘K, the open-issues count and each site's status — set in Geist, under the new logo.

When something fails, Lissoss says what happened, why, and the one thing to do next. The technical detail stays a click away.

A run shows its steps and a clock, and keeps reporting from a corner of the screen after you move to another page.

Reviews, wireframes, mock-ups and summaries are saved on the server before they appear, so closing the tab never loses a result you've spent an action on.

Home's source badge now says what is behind the numbers: live, when the last sync ran, or sample data.

Loading states are visible again, and pages arrive softly instead of snapping in. Both hold still under reduced motion.

Home lost its hero panel and health gauge, so it reads as one dashboard. The depth lives in Analytics, Issues and Sessions.

Every page scored for attention, with its reasons. Pick one for a review grounded in its live structure, then a wireframe, a mock-up and a brief for your coding agent.

Claude Code, Cursor and other MCP clients can ask which page needs work and pull the brief. Eight tools: seven free, one uses an AI action.

A narration's one fix becomes an issue in a click and is verified like any other. Marking an issue fixed now asks what you changed.

Email on genuinely new high and medium issues. The inbox now also catches landing pages that lose most arrivals within ten seconds, and JavaScript errors.

Funnels of two to six steps with each channel's own completion, and a view that reports only material moves — or says why it can't yet.

Localhost, LAN and saved-page visits are dropped, and “Not me” hides any visitor. The hidden count is always shown.

The snippet records nothing until a visitor agrees. Old visitor events are purged every night, and an admin can erase a visitor on request.

The math clusters the friction and one AI call writes a title, a story and one fix for every cluster. Open, Fixed and Dismissed survive every new run.

Mark an issue fixed and every later triage compares the affected-session rate before and after, normalised for traffic.

Tell Lissoss what a conversion is — reaching a page or clicking an element — and every number and verdict uses it. Until then it says “Engaged”.

Install the snippet, watch events arrive live, set your goal.

The headline, what happened and one thing to do, written each night and sent to your inbox.

One page counts your AI actions and sessions against your plan — in actions, never dollars.

Without a live source, the workspace shows a sample month, marked “Sample data” wherever it appears.