{"version":"2.1.242","anchor":"computer-use-refuses-to-confirm-saves-into-protected-locatio","canonical_anchor":"computer-use-refuses-to-confirm-saves-into-protected-locatio","heading":"Computer use refuses to confirm saves into protected locations on macOS","tier":"notice","area":"Computer Use","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/computer-use-refuses-to-confirm-saves-into-protected-locatio","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Computer use refuses to confirm saves into protected locations on macOS\n\nWhile driving a Mac app, Claude refuses to confirm saves into sensitive startup or ssh files.\n\n**What**\n\nWhen Claude is driving a Mac app and a save sheet is open, several actions are now refused: putting a path or a shell-startup, ssh or launch-agent file name in the file-name box, pressing Return in the Go-to-Folder box, dragging or holding a press while the sheet is up, and typing into a window that is editing a protected document.\n\n**Details**\n\n- All refusals report `save_panel_restricted`, a reason code that does not exist in the previous build.\n- Return in Go-to-Folder is refused as unverifiable, since the destination cannot be checked before it commits.\n- Navigation shortcuts still work in a window editing a protected document; only text entry is blocked.\n- The checks run on macOS and depend on the host being able to inspect the open sheet and the document being edited.\n\n**Evidence**\n\n`save_panel_restricted`\n\n- Area: Computer Use\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}