# Env vars not available in cloud agent's terminal? **URL:** \ **Category:** Help\ **Tags:** terminal, cloud-agents\ **Created:** [February 11, 2026, 3:24pm UTC](https://forum.cursor.com/t/env-vars-not-available-in-cloud-agents-terminal/151593 "2026-02-11T15:24:13Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Brian\_Morin](https://avatars.discourse-cdn.com/v4/letter/b/da6949/32.png) [@Brian\_Morin](https://forum.cursor.com/u/Brian_Morin)\ **Post date:** [February 11, 2026, 3:24pm UTC](https://forum.cursor.com/t/env-vars-not-available-in-cloud-agents-terminal/151593/1 "2026-02-11T15:24:13Z")
Hi folks, I’ve configured a handful of variables in the cloud agents settings and can see them both in the web UI and within Cursor’s IDE settings window. Now I’ve started the cloud agent setup wizard and am trying to make use of those variables. If I call `printenv` from the terminal in the cloud agent, I don’t see the variables. It’s hard to tell because there is limited output when trying to run the install command, but I suspect they are also not available during that. I’m trying to, among other things, specify a github token to authenticate to a private npm registry for use during `npm i`. Should I be seeing these variables when calling printenv in the agent terminal during setup? ---
**Author:** ![jakehandy](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/jakehandy/32/89524_2.png) [@jakehandy](https://forum.cursor.com/u/jakehandy)\ **Post date:** [February 11, 2026, 4:27pm UTC](https://forum.cursor.com/t/env-vars-not-available-in-cloud-agents-terminal/151593/3 "2026-02-11T16:27:00Z")
yeah, this is normal env vars/secrets configured in Cloud Agent settings often don’t appear inside the terminal, so `printenv` isn’t going to show them. the install should work fine once the environment is finished and the agent runs commands afterwards ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [February 13, 2026, 4:29pm UTC](https://forum.cursor.com/t/env-vars-not-available-in-cloud-agents-terminal/151593/4 "2026-02-13T16:29:55Z")
There’s actually no terminal redaction going on for secrets on cloud agents – I suspect your secrets might not actually be making it to the environment! When configuring Team Secrets, have you left the default **Apply to: All Repositories**? ![Screenshot 2026-02-13 at 17.29.34](https://us1.discourse-cdn.com/cursor1/original/3X/a/8/a826ad19721045a63ad2f949222d4c1126f6bb4c.png) ---
**Author:** ![Brian\_Morin](https://avatars.discourse-cdn.com/v4/letter/b/da6949/32.png) [@Brian\_Morin](https://forum.cursor.com/u/Brian_Morin)\ **Post date:** [February 13, 2026, 5:01pm UTC](https://forum.cursor.com/t/env-vars-not-available-in-cloud-agents-terminal/151593/5 "2026-02-13T17:01:07Z")
Hi Colin yes, I’ve left the default and confirmed that in the web UI. I just made sure to update to the latest client and again when starting the cloud agent wizard, none of my secrets (team or personal) appear in `printenv` ---
**Author:** ![natemwilson](https://avatars.discourse-cdn.com/v4/letter/n/edb3f5/32.png) [@natemwilson](https://forum.cursor.com/u/natemwilson)\ **Post date:** [February 18, 2026, 3:44pm UTC](https://forum.cursor.com/t/env-vars-not-available-in-cloud-agents-terminal/151593/6 "2026-02-18T15:44:38Z")
I’m having the exact same issue. ---
**Author:** ![bsalita](https://avatars.discourse-cdn.com/v4/letter/b/f19dbf/32.png) [@bsalita](https://forum.cursor.com/u/bsalita)\ **Post date:** [July 3, 2026, 1:27pm UTC](https://forum.cursor.com/t/env-vars-not-available-in-cloud-agents-terminal/151593/7 "2026-07-03T13:27:04Z")
I had the same issue of env vars not showing up when running the app or in the terminal. I asked using a prompt but the answer was non-actionable, something about either restarting the VM or creating a new VM. It was an impressively low quality response. After hours of experimentation, I finally stumbled upon the secretive URL. It’s in the form of [https://cursor.com/dashboard/cloud-agents/environments/r/github.com/bsalita/elo\_ratings](https://cursor.com/dashboard/cloud-agents/environments/r/github.com/bsalita/elo_ratings) where bsalita is my github repo and elo\_ratings is the project name. Substitute with your repo and project. On the top-right corner, there’s a drop down menu “Start Setup Agent”. It offers two choices; “Update Existing Env” and “Start Fresh”. Clicking on either will recreate the VM with the environment’s Secrets (the secrets which were entered in the right sidebar of the environment’s page. So there’s two issues. First, when environment variables are changed, a message should appear explaining that the VM must be updated and how to do it. Better yet, a single button should appear which offers to update/start fresh.