{"version":"2.1.305","anchor":"new-profile-forget-hint-for-sandboxed-commands-reading-the","canonical_anchor":"new-profile-forget-hint-for-sandboxed-commands-reading-the","heading":"New message explains how to withdraw sandbox access to your user profile","tier":"use","area":"Sandbox","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/new-profile-forget-hint-for-sandboxed-commands-reading-the","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### New message explains how to withdraw sandbox access to your user profile\n\nA new message says to close every Claude Code session and run `profile forget` so sandboxed commands stop reading your user profile\n\n**What**\n\nSandboxed commands are commands Claude Code runs inside a protected space with limited access. Claude Code now has a message explaining how to take away their access to your user profile, the folder holding your personal files and settings. It tells you to close every Claude Code session and then run `profile forget` in a terminal. After that, sandboxed commands read nothing in your user profile.\n\n**Why**\n\nThis gives a way back if you have let sandboxed commands read your user profile and want to stop it.\n\n- Area: Sandbox\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}