Faster Reviews: Pre-Warmed Instances, Schema Change Badges, and Value Diff Sorting

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

Recce Cloud Instances Launch in Seconds

Alt: Recce Cloud instance launching quickly from warm pool

Launching a Recce Cloud instance used to take 30 seconds or more. Every PR review started with a wait while a fresh container spun up.

Recce Cloud now draws instances from a pre-warmed container pool. Startup drops from 30 seconds to under 7 seconds. The pool stays warm so the next launch is just as fast. Available on the Enterprise plan.

MCP Server: Stable Setup with Clear Error Messages

The Recce MCP server crashed without a useful error when base artifacts were missing. Users had to dig through logs to find what went wrong. The --help text did not mention prerequisites.

The MCP server now classifies errors and tells you exactly what is missing. A new single-env onboarding mode works without a full two-environment setup. The --help output documents prerequisites so AI agents and users know what Recce MCP needs before starting.

Sort Value Diff Columns by Match Percentage

Alt: Value Diff sorted by Matched % with lowest matches at top

Value Diff showed columns in their original order. Finding the columns with the biggest differences meant scanning every row and comparing percentages manually.

Columns now sort by Matched % by default, with the lowest match at the top. Click any column header to change the sort order. The columns that need attention surface immediately.

See Which Columns Changed at the SQL Level in Schema View

Alt: Schema View showing ~/+/- badges and definition-changed indicator

Schema View showed added and removed columns, but columns with modified SQL definitions looked the same as unchanged ones. You had to open the code to check whether a column’s logic actually changed.

Schema View now marks columns with ~ (modified), + (added), and - (removed) badges. Columns where the underlying SQL changed show a definition-changed badge. You can spot logic changes without leaving the schema.

Column Lineage Resolves Recursive CTEs

Recursive CTEs — common in models that traverse hierarchies or generate sequences — showed “unknown” in column lineage. The self-referential nature of these CTEs broke lineage tracing.

Column lineage now follows recursive CTE references through each iteration. Models that use WITH RECURSIVE display correct lineage paths instead of dead ends.

Bug Fixes

Lineage view stays focused during row count. Running a row count from NodeView no longer resets the zoom and pan position.

Result pane appears in the correct position. The result pane no longer jumps to the top of the page.

Source nodes display their schema. Source nodes with columns in the catalog now show those columns instead of an empty panel.