{"version":"2.1.251","anchor":"trust-re-prompt-explains-why-the-earlier-approval-no-longer-","canonical_anchor":"trust-re-prompt-explains-why-the-earlier-approval-no-longer-","heading":"Trust re-prompt explains why the earlier approval no longer counts","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251\/e\/trust-re-prompt-explains-why-the-earlier-approval-no-longer-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.251","markdown":"### Trust re-prompt explains why the earlier approval no longer counts\n\nRe-approval prompts now explain why your earlier approval could not be trusted.\n\n**What**\n\nWhen Claude Code asks again about a command you already approved, it now says the approval was stored somewhere it cannot rely on: a plugins directory inside the workspace, one on a network location, or one it could not resolve. The old text just said \"recorded inside this workspace\".\n\n**Details**\n\n- Always shown in that situation; there is no flag to skip it.\n\n**Evidence**\n\n`recorded where it cannot be relied on (a plugins root inside a workspace, on a network location, or one that could not be resolved)`\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}