AI-Assisted Onboarding and Diff UX Improvements

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

AI-Assisted Onboarding

Alt: onboarding panel with AI agent suggestions for CI/CD configuration

Setting up Recce involves connecting git, configuring your data warehouse, and adding Recce to CI/CD. The first two steps are straightforward with UI guidance. CI/CD setup is where it gets complex—every team has different pipelines, platforms, and configurations.

Recce onboarding now includes an AI assistant that handles the hardest part. When you reach CI/CD setup, the agent generates workflow configurations for your specific setup—GitHub Actions, GitLab CI, or other platforms. Describe your pipeline and the agent produces the YAML you need.

See Changes and Impact at a Glance

Finding what changed in large diffs required scanning through every line. Click the model to view all columns without highlighting changes. Value distributions lacked context for quick comparison.

Recce now makes changes and their impact immediately visible:

Schema change indicators — Visual badges mark columns as added, removed, or modified
Collapsible unchanged regions — Unchanged code collapses automatically so you focus on what matters
TopK inline labels — Distribution bars display numeric values inline for quick comparison

Customize Lineage Graph Node Shapes

Alt: Mermaid lineage graph with different node shapes for models, sources, and seeds

Lineage graphs used the same node shape for all resource types. Distinguishing between models, sources, and seeds required reading labels.

You can now configure custom node shapes in Mermaid lineage exports. Different shapes for different resource types make the graph easier to scan. Thanks to Daisuke Taniwaki for this community contribution (PR#1137).

See Instance Status on Your Project Page

Alt: project page with instance status indicators showing running, stopped, and error states

Opening a project meant waiting without knowing if the instance was already running or needed a cold start. There was no way to anticipate the wait time before clicking in.

The project page now shows instance status indicators. Know whether an instance is already running or requires a cold start before you click in.