From c368b73dd677358b56ba06847dc67b4a1117458a Mon Sep 17 00:00:00 2001 From: Dotta Date: Tue, 29 Sep 2026 09:46:12 -0500 Subject: [PATCH] Clarify Cursor admission and patched runtime isolation boundaries Co-Authored-By: Paperclip --- .../src/drivers/acpx/cursor-launch-policy.ts | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/packages/paperclip-runner/src/drivers/acpx/cursor-launch-policy.ts b/packages/paperclip-runner/src/drivers/acpx/cursor-launch-policy.ts index 19dfa2f6d98..c0523bc3431 100644 --- a/packages/paperclip-runner/src/drivers/acpx/cursor-launch-policy.ts +++ b/packages/paperclip-runner/src/drivers/acpx/cursor-launch-policy.ts @@ -17,10 +17,11 @@ export function cursorPrivateEnvironment(paths: { agentHomeDirectory: string; da } /** - * Cursor's disable-project-configs flag covers cli.json only. Its MCP/hook - * loaders still read these paths. Refuse ambient execution configuration rather - * than mutating the user's project. The host must protect these paths throughout - * the run and keep the same check on recovery; admission alone is not a sandbox. + * The vendor's disable-project-configs flag covers cli.json only. Keep this + * admission refusal as defense in depth without mutating the user's project. + * The separately verified paperclip-cursor-isolation-v1 distribution removes + * ambient MCP and hook discovery at its source for the entire session. This + * check alone is not continuous filesystem protection or an OS sandbox. */ export async function assertCursorWorkspacePolicy(workspacePath: string, platform: NodeJS.Platform = process.platform): Promise { const paths: Array<{ path: string; inspectClaude?: boolean }> = [];