This release brigs a unified agent experience, smarter incident management in beta, table usage across more warehouses, and more context and control for agents across the board.
Unified Agent Experience
The usage of Elementary agents grows every month, and we keep learning from how you work.
What we saw? Switching between agents mid-conversation slows you down and requires you to think about the tool, not the task. This changes today.
One unified agent now orchestrates everything automatically, choosing the right capabilities for each step as your work evolves. Just set your mode, "ask" or "edit", and let it run.
New Incident Grouping
Related failures can now merged into one incident, reducing alert fatigue and speeding up resolution. Once merged, you can see all failures in a single place, as well as the lineage between them.
Merge the incidents manually, or ask the agent to find and merge related ones for you.
Interested in early access? Reach out to the team.
Table Usage: More Warehouses (Opt-in)
Table usage stats are now available for Snowflake, Redshift, Databricks, and BigQuery. For every asset, you can see query volume and number of unique users, so you always know what data actually matters to your organization.
Usage data is visible in the catalog, and available as context for the agent.
👉 Learn more, and reach out to the team for access.
Cloud Test Improvements
Agent/MCP Cloud Volume and freshness tests management
Use the unified agent or the MCP to create, configure, enable/disable, and mute/unmute tests at scale.
Control training period
You can now set and edit the training period for cloud volume and freshness monitors, up to three months.
Data Contract Test
Elementary now supports a data contract cloud test. It validates that a table's schema conforms to a defined contract and detects column additions, removals, type changes, and nullability changes.
Fivetran Job Alerts
As another milestone in our Fivetran integration, sync failures now trigger alerts straight to Slack, Teams, or any configured destination.
To enable it, add "job failures" to your alert rules.
CI: More Control Over PR Settings
Project repo settings are now user-configurable: labels, commit message prefix, branch prefix, and ticket ID requirements.
When required ticket ID is enabled, every PR opened by Elementary must include a ticket ID, prepended to the branch name and title.
dbt Artifact Tools
dbt artifact tools are now exposed in the MCP and available to agents: query dbt invocations, run results, models, and sources directly.
