# Support Secrets in Cloud Agent Environment Setup Script

**URL:** <https://forum.cursor.com/t/support-secrets-in-cloud-agent-environment-setup-script/142517>\
**Category:** Feature Requests\
**Created:** [November 13, 2025, 10:48pm UTC](https://forum.cursor.com/t/support-secrets-in-cloud-agent-environment-setup-script/142517 "2025-11-13T22:48:16Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CaptainTeemo](https://avatars.discourse-cdn.com/v4/letter/c/3d9bf3/32.png) [@CaptainTeemo](https://forum.cursor.com/u/CaptainTeemo)\
**Post date:** [November 13, 2025, 10:48pm UTC](https://forum.cursor.com/t/support-secrets-in-cloud-agent-environment-setup-script/142517/1 "2025-11-13T22:48:17Z")

</div>

### Feature request for product/service

Background Agent (GitHub, Slack, Linear,…)

### Describe the request

I’ve setup an environment setup command in the Cursor Cloud Agent Settings. For node-based projects, this worked well UNTIL we attempted to install private npm packages. Just a basic `npm install`.

From my testing, the secret for the auth token was NOT available at the “setup” time. But, when I asked the agent (with no setup command enabled) to npm install the private packages, that worked great.

Also, I couldn’t access the setup logs, making this a very difficult debug. This would be great as well.

### Operating System (if it applies)

MacOS