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?
1 Like
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
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?
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
1 Like
I’m having the exact same issue.