> ## Documentation Index
> Fetch the complete documentation index at: https://docs.paradime.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Other improvements

> Fixes in v6.18: exact on-merge branch matching, Lineage Diff once per commit, agents get workspace env vars, Radar costs without a repo, and dbt-loom updates.

*October 8, 2026*

**Bolt**

* On-merge schedules run only for merges into exactly their branch (a schedule on `main` no longer runs for `main-v2`), and each merge run builds the pull request's merge commit.
* Turbo CI runs record the pull request's branch instead of `HEAD`, and Turbo CI schedules saved in the UI apply from the next pull request event.
* [Lineage Diff](/products/bolt/ci-cd/lineage-diff/index) is computed once per pull request commit, instead of after every Turbo CI run.
* A `schedule_trigger` with an empty `workspace_name` now points at the schedule's own workspace. Links written that way never fired before and start firing after your next deploy.
* **Run** stays available while Bolt reparses your schedules in the background.

**DinoAI**

* Agent sessions now get the workspace's **Default** environment variables, overlaid by their Agent environment's variables. See [Environment Variables](/products/settings/environment-variables/index).
* An agent that posts "Still working…" in Slack and then stops is sent back to finish, instead of the run showing **Completed**.
* Agent runs started through the API or the MCP server return the final answer, even when the agent first sends a short progress note.

**Code IDE**

* `paradime_schedules.yml` no longer flags a named Bolt environment, such as `environment: staging`, as invalid.
* The IDE reconnects by itself when the editor stops, instead of staying **Offline** until you reload.

**Radar**

* A workspace with only a cost connection can open the cost pages, **Alerts**, and **Looker** without a repository or Bolt connection. See [Get Started](/products/radar/getting-started).

**dbt™ Mesh**

* On dbt™ 1.11 and 1.12, dbt-loom accepts `schedule_slug`, works with account API keys when you set `workspace_uid`, and names any missing environment variable. See [Configure cross-project dependencies](/guides/data-mesh-setup/configure-project-dependencies).
* On dbt™ 1.11 and 1.12, projects without a `dbt_loom.config.yml` get dbt™'s own model access checks back, so a `ref` to a `private` model from outside its group now fails as dbt™ intends.


## Related topics

- [Other improvements](/changelog/2026-09-03/other-improvements.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.