Answer: You define step-level environment variables with the `env` field, propagate cross-step variables by writing them to the `$ENVRC` file, and configure secrets in the Devin UI's Secrets tab where they are automatically injected as environment variables without being declared in the blueprint. Status: Confirmed Entry: tool/devin/settings/blueprint-env-vars-secrets Revision: 1 Digest: sha256:6b71b03b3bfa2067 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:15:13Z Last changed: 2026-11-13T03:15:13Z Last verified: 2026-11-20T12:46:58Z Next check: 2026-11-21T12:46:58Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Step-level env field | env | [1] | 2026-11-20 Cross-step variable file | $ENVRC | [1] | 2026-11-20 Secrets configuration location | Secrets | [1] | 2026-11-20 Secrets declaration requirement | You don't declare them in your blueprint. | [1] | 2026-11-20 Secrets injection timing | Secrets are injected before every step runs during builds. | [1] | 2026-11-20 Sources: [1] Cognition. "Blueprint reference". https://docs.devin.ai/onboard-devin/environment/blueprint-reference.md Role: primary. Accessed: 2026-11-20T12:46:58Z Quote: "Any step can define extra environment variables with the `env` field:" (Supports: Step-level env field) Quote: "To propagate environment variables across steps, write them to the `$ENVRC` file:" (Supports: Cross-step variable file) Quote: "Secrets configured in the Devin UI (via the **Secrets** tab in each blueprint editor) are automatically injected as environment variables." (Supports: Secrets configuration location) Quote: "You don't declare them in your blueprint. Just reference them by name (e.g., `$MY_SECRET`)." (Supports: Secrets declaration requirement) Quote: "Secrets are injected before every step runs during builds." (Supports: Secrets injection timing) Published: 2026-11-20T09:56:01Z Snapshot SHA-256: 6974c02296bdeaabb6a52b9c4c7f2cc68afd871e8408284037bad0a895a8526d (captured 2026-11-13T03:15:13Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:15:13Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:46:58Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:46:58Z Last attempt: 2026-11-20T12:46:58Z Notes and limitations: Extracted automatically from a single official source (section "Environment variables and secrets"). Related: https://latestn.com/tool/devin/settings/blueprint-file-attachments How do I attach files in a Devin blueprint? https://latestn.com/tool/devin/settings/bot-comment-modes What modes does Devin offer for responding to bot comments on pull requests? https://latestn.com/tool/devin/settings/browse-playbooks-settings Where can I browse Organization, Enterprise, and System playbooks in Devin? https://latestn.com/tool/devin/settings/admin-security-settings-reference What security settings can admins configure in Devin Desktop and what are the recommended values? https://latestn.com/tool/devin/settings/allowlist-specific-bots How do I make Devin respond only to specific bots on pull requests? https://latestn.com/tool/devin/settings/autocomplete-settings Where can I find the Devin Desktop autocomplete settings, such as completion mode? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:15:13Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/devin/settings/blueprint-env-vars-secrets/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/devin/settings/blueprint-env-vars-secrets POST: https://latestn.com/dispute/tool/devin/settings/blueprint-env-vars-secrets with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/devin/settings/blueprint-env-vars-secrets?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I define environment variables and secrets in a Devin blueprint? Revision 1, last verified 2026-11-20T12:46:58Z. https://latestn.com/tool/devin/settings/blueprint-env-vars-secrets (accessed 2026-11-21T09:57:28Z). @misc{LatestN_tool_devin_settings_blueprint_env_vars_secrets_r1, title = {How do I define environment variables and secrets in a Devin blueprint?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/devin/settings/blueprint-env-vars-secrets}}, note = {Revision 1; digest sha256:6b71b03b3bfa2067; last verified 2026-11-20T12:46:58Z; accessed 2026-11-21T09:57:28Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/devin/settings/blueprint-env-vars-secrets