Changelog

Release notes for the whole Altimate suite: dbt Power User, Altimate Code, Datamates, Snowflake, and Databricks.

Filter by product
RSS
Showing 10 of 10 updates

July 2026

  1. ImprovedAltimate Code

    Altimate Code auto-installs on first chat open

    Opening the chat panel for the first time now installs Altimate Code automatically in the background instead of sending you to a manual install screen. You'll see a short "Preparing your Altimate Code experience" notification while it sets up, with the old manual install flow kept as a fallback if auto-install fails. Prefer to do it yourself? Turn off the new auto-install setting in your editor preferences.

  2. ImprovedSnowflake App (Enterprise)Databricks App (Enterprise)

    Better error messaging when no team is selected in Studio

    Asking Studio any question without a team selected now shows a clear message prompting you to pick a team, instead of a generic error with no obvious next step.

  3. ImprovedMCP Server

    Column level lineage Improvements

    We've made some performance and accuracy improvements to Column level lineage. You can experience faster, more accurate drill downs in your Lineage

  4. ImprovedPower user for dbtAltimate CodeMCP Server

    Datamate MCP server defaults to stdio transport

    The datamate MCP server now uses the stdio transport by default, so external MCP clients like Claude Code, Claude Desktop, and Cursor connect out of the box. Previously you had to manually switch the transport setting to get this; now it's the default, and you can still switch back if you prefer the old behavior.

  5. ImprovedAltimate Code

    Enterprise AI token usage is now metered and visible

    Enterprise and premium plans previously bypassed usage metering entirely, so there was no way to see how many AI tokens your team had used. Usage is now tracked against your provisioned grant, the same way every other plan already works, and shows up in the same token usage view — so you can see exactly what's been used and what's left.

  6. ImprovedDatabricks App (Enterprise)

    Filter AI/ML opportunities by endpoint name

    You can now filter Databricks AI/ML cost-saving opportunities by endpoint name. Type or paste part of a name to jump straight to the model-serving, vector-search, or AI Gateway endpoint you're looking for. The filter also works alongside the existing Type filter, and accepts letters, numbers, and symbols.

  7. ImprovedDatabricks App (Enterprise)

    Fixed Blank Runtime Engine and Photon fields

    The Runtime Engine and the Photon Enabled fields always showed a blank dash no matter how the cluster was actually configured. Both now populate correctly from the cluster's runtime version, so you can see at a glance whether Photon is turned on.

  8. ImprovedDatabricks App (Enterprise)

    Fixed Workspace-scoped visibility for model-serving endpoint opportunities

    Fixed: Access scoping for model-serving endpoint opportunities Model-serving endpoint opportunities are now properly scoped by workspace access, matching the behavior of cluster, job, and warehouse opportunities.

  9. BetaDatabricks App (Enterprise)

    New (Beta): Auto Tune comes to all-purpose clusters

    Auto Tune now supports Databricks all-purpose clusters, with a dedicated tab matching the existing Jobs experience. It includes: - Cost-savings chart to track the savings that Auto Tune is helping you realize - Audit history of all Auto Tune activity on the cluster - Toggles for Worker Sizing and Auto Termination recommendations You're in control of what Auto Tune can do by enabling just the recommendation types you want. Once enabled, Auto Tune operates autonomously, applying optimizations with SLA-safe rollbacks if anything regresses. Opening any recommendation shows a before/after diagram of the cluster's current and proposed configuration, so you always have full visibility into what's changing.

  10. ImprovedSnowflake App (Enterprise)

    New Site name column on Tableau connection sync history

    For Tableau connections spanning multiple sites, the Sync History table now includes a Site Name column showing which site each sync run belongs to. Previously, sync events weren't attributed to any site.