# Environment-scoped secrets not injected into web-launched Cloud Agents, but setup agent sees them

**URL:** <https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916>\
**Category:** Bug Reports\
**Tags:** cloud-agents\
**Created:** [July 16, 2026, 12:55pm UTC](https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916 "2026-07-16T12:55:41Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike1111](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@Mike1111](https://forum.cursor.com/u/Mike1111)\
**Post date:** [July 16, 2026, 12:55pm UTC](https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916/1 "2026-07-16T12:55:41Z")

</div>

### Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

### Describe the Bug

I have secrets configured on a personal Cloud Agent environment under Environment secrets (mix of Runtime Secrets and Environment Variables, all “All Repositories”).

The setup agent can see/use them.  
Later web-launched Cloud Agents on the same environment get none of them, including Environment Variable, not just Runtime Secrets.  
This is not Runtime Secret redaction. Injection never happens:  
CLOUD\_AGENT\_ALL\_SECRET\_NAMES → unset  
CLOUD\_AGENT\_INJECTED\_SECRET\_NAMES → unset

### Steps to Reproduce

I created an environment. Started setup agent. Then I set the secrets. New agent using this environment didn’t get the secrets. I started another setup agent with “Update Existing Env” and it did see the secrets. I saved the environment multiple times and started multiple new agents, but none of them had the secrets.

### Expected Behavior

Cloud Agents using that environment should receive the environment’s secrets/env vars

### Operating System

Windows 10/11

### Version Information

Web / Cloud Agents ([cursor.com/agents](http://cursor.com/agents))  
Reproduced on 2026-07-16  
Agent ID: bc-d63690f4-973b-44d4-81f5-6a6810f68416  
No IDE/CLI involved in the failing runs

### Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

---

<div class="post-metadata">

**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:** [July 16, 2026, 3:23pm UTC](https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916/7 "2026-07-16T15:23:50Z")

</div>

Hey @Mike1111!

Thanks for the report. This is a known issue with Environment-scoped Runtime Secrets, and we’re tracking this bug (I’ve just added your report as more signal!).

Until this is fixed, continuing to define these secrets as personal/team scoped instead of environment scoped will serve as a reliable workaround. This should prevent the issue you’re experiencing while we work on a permanent fix.

I can follow up here once the bug has been resolved!

---

<div class="post-metadata">

**Author:** ![Mike1111](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@Mike1111](https://forum.cursor.com/u/Mike1111)\
**Post date:** [July 16, 2026, 3:33pm UTC](https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916/9 "2026-07-16T15:33:13Z")

</div>

I have both Personal scoped and Environment scoped Runtime Secrets, and none of them work.

---

<div class="post-metadata">

**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:** [July 22, 2026, 11:55am UTC](https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916/11 "2026-07-22T11:55:44Z")

</div>

Hi @Mike1111!

We deployed a fix last night to fix up secret injection. Can you give it another try?

---

<div class="post-metadata">

**Author:** ![Mike1111](https://avatars.discourse-cdn.com/v4/letter/m/ad7895/32.png) [@Mike1111](https://forum.cursor.com/u/Mike1111)\
**Post date:** [July 22, 2026, 2:52pm UTC](https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916/12 "2026-07-22T14:52:43Z")

</div>

It’s working for me now. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [July 24, 2026, 2:52pm UTC](https://forum.cursor.com/t/environment-scoped-secrets-not-injected-into-web-launched-cloud-agents-but-setup-agent-sees-them/165916/13 "2026-07-24T14:52:47Z")

</div>

Closed on July 24, 2026, 2:52pm UTC

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
