The knowledge sources do not show a way to globally change how

--select

works so that

elementary

is automatically added every time you select something else (e.g. “`dbt build -s model_x` should implicitly behave like `dbt build -s model_x elementary`”). dbt itself doesn’t expose a “default extra selector” setting in

dbt_project.yml

in the materials we have. [Disable per env] What is documented are patterns that go the other way (disabling or excluding Elementary by default), using: •

+enabled

conditions per env/var in

dbt_project.yml

[Disable per env] • Explicit

--exclude elementary

/

--exclude package:elementary

on the CLI [Micro-batch example] So, based on the available sources: • There’s no documented way to force-include

elementary

in every

--select

via config. • The practical workaround would be to enforce this at the orchestration / script level (e.g. always calling `dbt build --select "`your selector

elementary"

), but that’s outside what the docs and Slack threads explicitly describe. 👍 0 button 👎 0 button ℹ️ Tip: Mention @elementary.ai in the thread for follow-ups or DM the app for 1-to-1 help.