Answer: Use authored auth to keep callers apart, since callers sharing the same bearer token are treated as one person. Status: Confirmed Entry: tool/cursor/permissions-and-security/separate-callers-cloud-agents Revision: 1 Digest: sha256:a8fc5923af879fbd (changes whenever the content changes) Timeline: Created: 2026-11-13T03:08:30Z Last changed: 2026-11-13T03:08:30Z Last verified: 2026-11-20T12:32:50Z Next check: 2026-11-21T12:32:50Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of solution | authored auth | [1] | 2026-11-20 shared token behavior | the extension treats them all as one person | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/agent-sdk/guides/cloud-agents.md". https://cursor.com/docs/agent-sdk/guides/cloud-agents.md Role: primary. Accessed: 2026-11-20T12:32:50Z Quote: "Use [authored auth](https://cursor.com/docs/agent-sdk/reference/channels.md#auth-policies) to keep callers apart." (Supports: solution) Quote: "If every caller uses the same bearer token, the extension treats them all as one person." (Supports: shared token behavior) Snapshot SHA-256: 724e615cbf8047667295c38df4d8a53d0a48444efa16790c027fe5f7d8617c79 (captured 2026-11-13T03:08:29Z) 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:08:30Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:32:50Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:32:50Z Last attempt: 2026-11-20T12:32:50Z Notes and limitations: Extracted automatically from a single official source (section "What the agent can do"). Related: https://latestn.com/tool/cursor/permissions-and-security/shared-responsibility-controls Which security controls does Cursor handle versus which do I configure myself? https://latestn.com/tool/cursor/permissions-and-security/shell-command-permissions How do I allow or deny shell commands in Cursor CLI using Shell permission tokens? https://latestn.com/tool/cursor/permissions-and-security/shell-mode-permissions-location Where are permissions configured for Cursor Shell Mode? https://latestn.com/tool/cursor/permissions-and-security/rotate-service-account-api-key How do I rotate an API key for a Cursor service account? https://latestn.com/tool/cursor/permissions-and-security/security-model-differences What are the security model differences between Cursor-hosted and self-hosted Cloud Agents? https://latestn.com/tool/cursor/permissions-and-security/self-host-securely How do I self-host a Cursor Agent SDK deployment securely? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-13T03:08:30Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/permissions-and-security/separate-callers-cloud-agents/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/separate-callers-cloud-agents POST: https://latestn.com/dispute/tool/cursor/permissions-and-security/separate-callers-cloud-agents with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/permissions-and-security/separate-callers-cloud-agents?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I keep callers' Cursor cloud agents separate when they share a bearer token? Revision 1, last verified 2026-11-20T12:32:50Z. https://latestn.com/tool/cursor/permissions-and-security/separate-callers-cloud-agents (accessed 2026-11-21T10:02:39Z). @misc{LatestN_tool_cursor_permissions_and_security_separate_callers_cloud_agents_r1, title = {How do I keep callers' Cursor cloud agents separate when they share a bearer token?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/permissions-and-security/separate-callers-cloud-agents}}, note = {Revision 1; digest sha256:a8fc5923af879fbd; last verified 2026-11-20T12:32:50Z; accessed 2026-11-21T10:02:39Z} } 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/separate-callers-cloud-agents