Skip to main content
September 30, 2026
  • DinoAI: an agent run no longer ends as Completed on a reply that only promises work, such as “I’ll produce the list next”. When a turn ends on a promise without calling a tool, the agent is sent back once to do the work, or to say plainly that it’s finished, blocked, or waiting on you.
  • DinoAI: diagrams in DinoAI’s Slack replies render as images again, instead of arriving as raw Mermaid code.
  • Bolt: Turbo CI and other deferred runs start faster. They now fetch the deferred schedule’s sources.json only when a command selects on source_status or runs dbt retry.
  • Bolt: Retry from failure keeps the failed command’s --warn-error and path flags (--profiles-dir, --project-dir, --target-path, --log-path, and --defer-state) on the dbt retry it runs, so a retried dbt build --warn-error still treats warnings as errors. See Retrying a run.
  • Bolt: on dbt™ 2.0, runs that include dbt source freshness open in Run details again, and their post-run steps run again, including self-healing and alerts to incident.io, PagerDuty, Datadog, and New Relic. dbt™ 2.0 reports freshness statuses capitalized, which Paradime didn’t recognize. Sources that warn are also no longer shown as healthy in the Catalog and the Discovery API.
  • Catalog: the Catalog shows its build status again. A chip on the Catalog home, search results, and asset pages reads Ready, Building, Build failed, or Never built, and opens a breakdown by source with any error and whether it needs a fix from you. In the Code IDE, the catalog panel shows when your development catalog was last updated, and says why it has no docs for a file, such as a model that isn’t in the catalog yet. See Find & Explore.
  • Code IDE: a variable you put in front of a dbt™ command in the terminal now reaches dbt™, so PARADIME_STATE_DISABLED=1 dbt build turns Paradime State off for that one command. Values set in Settings > Environment Variables still take precedence. If a terminal was already open, open a new one to pick up the change.