> ## 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.

# Turn on Paradime State

> Switch to dbt™ 2.0 and set one environment variable so your Bolt schedules and Code IDE skip unchanged models on every dbt run and dbt build.

Turn on [Paradime State](/guides/paradime-state/index) for your Bolt schedules, your own Code IDE, or both. It takes a dbt™ version change and one environment variable, with nothing to change in your project.

<Note>
  **Prerequisites**

  * An [Admin role](/products/settings/users/role-based-access-control) to change the dbt™ version and to set Default or Bolt variables. Any user can turn Paradime State on for their own Code IDE.
  * A project that parses on dbt™ 2.0. See [Prepare for dbt™ v2](/guides/migrations/dbt-version-upgrades/prepare-for-dbt-v2).
  * A [supported warehouse](/guides/paradime-state/index#supported-warehouses).

  Estimated time: 10 minutes.
</Note>

## Steps

<Steps>
  <Step title="Switch to dbt™ 2.0-latest">
    Paradime State runs only on dbt™ 2.0. Switch where you want to use it:

    * **The whole workspace:** go to **Settings** > **General**, select **Change version** next to the dbt™ version, choose `2.0-latest`, and save. Open Code IDE sessions restart, and Bolt re-parses your schedules.
    * **One Bolt environment:** go to **Settings** > **Environments**, open the Bolt environment's menu (**⋮**), select **Environment settings**, and set **dbt version** to `2.0-latest`.

    <Info>
      The Code IDE always uses the workspace's dbt™ version. To use Paradime State in the Code IDE, switch the whole workspace. See [Manage dbt™ version](/products/settings/configuration/manage-dbt-version).
    </Info>
  </Step>

  <Step title="Add the PARADIME_STATE_ENABLED variable">
    Go to **Settings** > **Environment Variables** and select **Add variable**. In the **New environment variable** panel, enter `PARADIME_STATE_ENABLED` as the **Key**, then enter `1` in the box for each environment where you want Paradime State on:

    | Box | Turns Paradime State on for |
    | - | - |
    | **Default** | Every Bolt environment and every user's Code IDE |
    | **Bolt · \<environment>**, for example **Bolt · Production** | Schedules in that Bolt environment |
    | **Code IDE** | Your own Code IDE sessions only |

    Leave a box empty to inherit the **Default** value, then save. Any of `1`, `true`, `yes`, or `on` turns it on.

    <Warning>
      A Default value also reaches your Turbo CI and continuous deployment schedules, and so does a Bolt value for the environment they run in. If those schedules select with `state:` methods such as `state:modified+`, keep Paradime State off for them. See [Turn it on or off for one schedule](#turn-it-on-or-off-for-one-schedule).
    </Warning>
  </Step>

  <Step title="Let Bolt and the Code IDE pick up the change">
    * **Bolt** reads the variable when it parses your schedules, not when a run starts. Saving a **Default** value re-parses them automatically. After saving a **Bolt · \<environment>** value, open Bolt and select **Parse schedules**, or wait for the next automatic parse (about 10 minutes).
    * **Code IDE:** after saving your **Code IDE** value, open a new terminal. Terminals that were already open keep their old environment.

    <Info>
      A Default value reaches your Code IDE the next time your IDE profile is written, for example when you save any of your Code IDE variables. To start right away, set the variable in your Code IDE box.
    </Info>
  </Step>

  <Step title="Run dbt build twice">
    Run `dbt build`, from a Bolt schedule or in the Code IDE terminal. The first run has nothing to compare against, so it builds every node and records a baseline. Run it again without changing anything: the unchanged nodes are skipped.

    Each state-aware run ends with a summary that starts with `=========== Paradime State ===========`, followed by counts such as `executed`, `skipped`, and `compute saved (est.)`. See [Read a Paradime State run](/guides/paradime-state/read-a-run).
  </Step>
</Steps>

<Check>
  The second run's summary lists your unchanged nodes under `skipped`. If a run has no Paradime State summary at all, it didn't go through Paradime State: see [No Paradime State summary at the end of the run](/guides/paradime-state/troubleshooting#no-paradime-state-summary-at-the-end-of-the-run).
</Check>

## Turn it on or off for one schedule

To change one schedule without touching the rest of its environment, override the variable on that schedule. `0` turns Paradime State off and `1` turns it on.

* **YAML schedules:** add the variable with [`env_overrides`](/products/bolt/creating-schedules/schedules-as-code/configuration-reference#environment-variable-overrides). It takes effect when Bolt next parses the schedule.

  ```yaml theme={"system"}
  env_overrides:
    - key: PARADIME_STATE_ENABLED
      value: "0"
  ```

* **Schedules created in the UI:** use a [Schedule override](/products/bolt/creating-schedules/schedules-environment-variables). An override can only change a variable that's already set for the schedule's environment, so add `PARADIME_STATE_ENABLED` to the Bolt environment first, then override it on the schedule.

## Turn it off

Set `PARADIME_STATE_DISABLED` to `1` in any box. It wins over `PARADIME_STATE_ENABLED`, so it's the quickest way to switch one environment back to plain dbt™ without changing anything else. Deleting `PARADIME_STATE_ENABLED` also turns it off. As with turning it on, Bolt applies the change at its next parse.

In a Code IDE terminal, `export PARADIME_STATE_DISABLED=1` turns it off for that terminal until you close it.

<Warning>
  In the Code IDE, putting the variable in front of a single command, as in `PARADIME_STATE_DISABLED=1 dbt build`, has no effect. Use `export`, or set the variable in your Code IDE box.
</Warning>

## Next steps

<CardGroup cols={2}>
  <Card title="Read a Paradime State run" href="/guides/paradime-state/read-a-run" icon="scroll-text">
    What each line of the summary means.
  </Card>

  <Card title="Configuration reference" href="/guides/paradime-state/configuration-reference" icon="sliders-horizontal">
    Tune when nodes rebuild with `lag_tolerance` and the other settings.
  </Card>

  <Card title="Environment variables" href="/products/settings/environment-variables/index" icon="variable">
    How variable scopes and precedence work.
  </Card>

  <Card title="Manage dbt™ version" href="/products/settings/configuration/manage-dbt-version" icon="box">
    Workspace and per-environment dbt™ versions.
  </Card>
</CardGroup>


## Related topics

- [Paradime State](/guides/paradime-state/index.md)
- [Paradime State configuration reference](/guides/paradime-state/configuration-reference.md)
- [Troubleshoot Paradime State](/guides/paradime-state/troubleshooting.md)
- [Paradime State: build only what changed](/changelog/2026-09-28/paradime-state.md)
- [Read a Paradime State run](/guides/paradime-state/read-a-run.md)