Keeping agent work available conflicts with preserving evidence of a possible tenant boundary failure.
A broad containment protects customer data quickly, while continued access preserves the workflow enterprises depend on.
Who you’d be doing this for
“My legal team asked why another company’s path showed up in our export, and I have nothing solid to tell them.”
Mai Santoso · Platform Security Engineer
She administers an enterprise development organization whose repositories are accessed through agent workspaces.
What is at stake
Repository paths from one organization appeared in another organization’s support export. You must weigh immediate containment against preserving evidence and active agent work.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer continuity vs. tenant isolation
- evidence preservation vs. rapid cleanup
- narrow containment vs. shared-service assurance
- export availability vs. verified recovery
Why Cursor
Cursor Editor agents read proprietary repositories and hold credentials inside enterprise workspaces.
Written with these in mind
Not your kind of problem? 42 more at Cursor, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.