Session Base, Persistent Agent Checks, and Outdated Check Indicators

Service	Purpose
Bootstrap	UI framework for page layout and navigation
Cal.com	Meeting booking widget
Consent cookie	Stores your cookie preferences (recce_consent, 13 months)

Service	Cookies	Duration	Data Collected
Google Tag Manager	_ga, _ga_*, _gid	Up to 2 years	Page views, traffic sources, anonymized IP
PostHog	ph_*, distinct_id	1 year	Page views, feature usage, session recordings
Vector	vector_*	1 year	Visitor identification, page views

Service	Cookies	Duration	Data Collected
HubSpot Tracker	__hssc, __hssrc, __hstc, hubspotutk	Up to 13 months	Page views, session data, visitor identity
HubSpot Forms	__hs*, hubspotutk	Up to 13 months	Form submissions, contact information

Session Base with Dashboard Visibility

Comparing against production often introduces noise from environment-dependent patterns — SQL that resolves differently between prod and CI. Session base lets each PR build a dedicated comparison baseline using CI targets, so both base and current produce the same SQL and the diff reflects only the PR’s actual changes. Upload session base artifacts with GitHub or GitLab token authentication, and verify exactly which base each PR is comparing against in the Cloud Dashboard.

Approve or Unapprove Checks from GitHub and GitLab

Updating check status required opening Recce separately from your code review. The new /update-check slash command lets reviewers approve or unapprove checks directly from GitHub or GitLab PR comments, keeping the review workflow in one place.

Agent Creates Persistent Checks with Checklist Rendering

AI-generated checks previously disappeared after the session ended, making it hard to track what was validated. Agent-created checks are now persistent and render as checklists in the PR summary with clear attribution, so reviewers see exactly what the agent verified and can act on it.

Outdated Check Indicators

When the underlying data changes, existing checks can silently go stale. Visual outdated indicators now mark checks that may no longer reflect the current state, so reviewers know which checks need re-running before merging.

Impact Analysis Discovery and Preset Check Filtering

Finding which models are affected by a PR required manual lineage inspection. The Recce plugin now includes an impact analysis discovery tool that surfaces affected models automatically, available today for Claude Code and compatible MCP clients. Criteria-based preset check filtering and SessionImpact computation let you define rules that trigger the right checks for the right changes. Branch staleness warnings in PR summaries further help reviewers spot when a PR’s base has drifted.

Materialization Badge for Lineage Nodes

Model nodes in the lineage graph previously showed no materialization context. A new badge on each node now displays its materialization type (table, view, incremental, etc.), making it easier to understand performance implications at a glance.

Improvements

Fixed check links in PR comments that incorrectly used the /launch/ path
Updated recce mcp-server --help to list all 16 available tools
DataTypeIcon SVGs now scale with CSS font-size for consistent rendering
CLL performance improvement: skip Jinja compilation when compiled_code already exists
Pre-cached full CLL map via new full_map API parameter for faster lineage loads