Answer: Yes, Cloud Agents can read secrets and credentials, which are configured through the Secrets tab and injected as environment variables at runtime. To limit exposure, sensitive values can be marked as Runtime Secrets to keep them out of the transcript, tool output, and commits. Status: Confirmed Entry: tool/cursor/permissions-and-security/cloud-agent-secret-access Revision: 1 Digest: sha256:a817bef0e3113d61 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:10:08Z Last changed: 2026-11-13T03:10:08Z Last verified: 2026-11-20T12:36:44Z Next check: 2026-11-21T12:36:44Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Secret configuration location | Secrets tab | [1] | 2026-11-20 Encryption at rest | encrypted at rest with KMS | [1] | 2026-11-20 Injection method | injected as environment variables at runtime | [1] | 2026-11-20 Runtime Secrets protection | Runtime Secrets | [1] | 2026-11-20 Ignore file for sensitive files | .cursorignore | [1] | 2026-11-20 Recommended cloud role credential | OIDC tokens | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/cloud-agent/security.md". https://cursor.com/docs/cloud-agent/security.md Role: primary. Accessed: 2026-11-20T12:36:44Z Quote: "Configure secrets through the Secrets tab in your dashboard." (Supports: Secret configuration location) Quote: "They're encrypted at rest with KMS, encrypted in transit, and injected as environment variables at runtime." (Supports: Encryption at rest) Quote: "encrypted in transit, and injected as environment variables at runtime" (Supports: Injection method) Quote: "Mark sensitive values as [Runtime Secrets](https://cursor.com/docs/cloud-agent/security-network.md#runtime-secrets) to keep them out of the transcript, tool output, and commits." (Supports: Runtime Secrets protection) Quote: "if sensitive files must live there, add them to [`.cursorignore`](https://cursor.com/docs/reference/ignore-file.md)" (Supports: Ignore file for sensitive files) Quote: "For cloud roles, mint [OIDC tokens](https://cursor.com/docs/cloud-agent/identity.md) from the VM instead of storing long-lived access keys." (Supports: Recommended cloud role credential) Snapshot SHA-256: 387a55a6c9b77e5e948ee7e6e0b5f7ab444a6cdf50ba10fcb5a501115951ca23 (captured 2026-11-13T03:10:07Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-13T03:10:08Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:36:44Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:36:44Z Last attempt: 2026-11-20T12:36:44Z Notes and limitations: Extracted automatically from a single official source (section "Can a Cloud Agent read secrets and credentials?"). Related: https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-secret-types What are the different secret types in Cursor Cloud Agents and when should I use each? https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-secrets-and-network-access How do I give a Cursor Cloud Agent access to secrets and network URLs it needs? https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-secrets-env-vars How do I add secrets and environment variables to a Cursor cloud agent? https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-egress-ip-ranges How do I get the egress IP ranges for Cursor Cloud Agents? https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-network-access How do I configure network access for Cursor Cloud Agents? https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-repo-access-scope Can Cursor Cloud Agents access repositories the developer can't? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:10:08Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-secret-access/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/permissions-and-security/cloud-agent-secret-access POST: https://latestn.com/dispute/tool/cursor/permissions-and-security/cloud-agent-secret-access with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/permissions-and-security/cloud-agent-secret-access?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Can Cursor Cloud Agents read secrets and credentials? Revision 1, last verified 2026-11-20T12:36:44Z. https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-secret-access (accessed 2026-11-21T10:02:03Z). @misc{LatestN_tool_cursor_permissions_and_security_cloud_agent_secret_access_r1, title = {Can Cursor Cloud Agents read secrets and credentials?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-secret-access}}, note = {Revision 1; digest sha256:a817bef0e3113d61; last verified 2026-11-20T12:36:44Z; accessed 2026-11-21T10:02:03Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/permissions-and-security/cloud-agent-secret-access