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