{"version":"2.1.246","anchor":"trust-dialog-gets-a-stricter-variant-when-a-directory-is-onl","canonical_anchor":"trust-dialog-gets-a-stricter-variant-when-a-directory-is-onl","heading":"Trust dialog gets a stricter variant when a directory is only trusted through its parent","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/trust-dialog-gets-a-stricter-variant-when-a-directory-is-onl","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Trust dialog gets a stricter variant when a directory is only trusted through its parent\n\nThe trust prompt got rewritten and now ignores an Enter or Esc that arrives too fast.\n\n**What**\n\nThe trust-this-directory prompt was rewritten and now has a second form used when you `\/cd` into a directory whose own settings want to grant project permission rules or extra directories. Its title is \"Now in a new directory:\", and the buttons read \"Yes, trust it and apply them\" \/ \"No, keep them off\". Both forms now ignore a confirm or cancel that arrives within a short window of the dialog appearing, so an Enter or Esc already in flight cannot answer it for you.\n\n**Details**\n\n- The stricter form is chosen by the caller, not by a flag or setting; the `\/cd` flow requests it when project grants are gated.\n- Its body explains that the directory's settings declare project permission rules and\/or additional directories that apply only on explicit trust, even though the directory is currently trusted via a parent.\n- The keypress guard applies to both confirm and cancel.\n\n**Evidence**\n\n`Its settings declare project permission rules and\/or additional directories. They apply only if you trust this directory explicitly (it is trusted through a parent directory so far).`\n\n- Area: Permissions\n- Names: `\/cd`\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 2\/5"}