{"found":true,"collection":"patterns","library_url":"https://www.grokbotdb.com/library/pat.separate-cursor-user-for-isolation","generated":"2026-09-06T05:32:11Z","citation":["Quote the record id and its source_url (or provenance if there is no URL).","Include last_verified or observed_at when present. Do not present an old date as current.","If tier is community and confidence is low, say so. Do not launder it into a fact.","If the database does not hold the answer, say that. Do not invent Grok Bot product claims.","Contradictions are data: when conflicts_with is present, report both records rather than picking a favourite.","Deprecated and removed records stay visible. They are history, not current guidance."],"record":{"id":"pat.separate-cursor-user-for-isolation","name":"A separate user, not a separate Bot","category":"safety","problem":"A workload genuinely needs its own credential set and the product offers no per-Bot isolation.","technique":"Give the workload its own Cursor user. Buy the seat.","why_it_works":"The only real isolation boundary on offer is the account, because the microVM is assigned per user.","when_to_use":"Client confidentiality, regulated data, anything a security review must be able to point at.","when_not_to":"When shared-session handoff between Bots is the point of the workflow; a second user loses it.","manual_ref":"1.2","evidence":"documented","source_url":"https://docs.x.ai/grok-bot/faq","related":["pat.bots-are-not-a-security-boundary","pat.scoped-service-accounts"],"confidence":"high","first_seen":"2026-09-03","last_verified":"2026-09-03"}}