Option to only trust a whitelist of project directories

[jklaiho]

In addition to the all-or-nothing trust_all_worktrees boolean, an option that I'd very much welcome is trust_worktrees_under (actual name TBD), an array of paths that Zed considers trusted (recursively; possibly with the exception of well-known embedded external paths like node_modules). Our company considers all of our internal codebases fully trusted, and with this option, we'd instruct people to have them under a whitelist of paths, separate from any external codebases. This combined with trust_all_worktrees: false would be a very compelling default in our environment.

[TrevorBurnham]

Same. The docs say:

To permit trust decisions for multiple directory worktrees at once, it's possible to trust all subdirectories of a given parent directory worktree opened in Zed by checking the appropriate checkbox.

So the capability is there, but only when you ope I'd like to be able to see and edit those directory-level trust settings directly. They aren't stored in ~/.config/zed, and they aren't shown in the settings pane.

The best available workaround seems to be to open a directory like /My/Dir/X, then click "Restricted mode" and accept the prompt to trust everything in the parent directory My/Dir.

Also, what if I want to revoke trust? Having an editable file would make that easy.