Repository Trust

Some language features can do more by running code from the repository you opened: build scripts, project plugins, a linter’s or formatter’s config file. A repository you just cloned could put anything there, so a feature that depends on trust works in a restricted form until you say you trust the repository.

Every repository starts untrusted, including projects you already had. Editing, Git and everything else keep working.

Trusting a repository

Loxel doesn’t ask when you open a project. When a feature is restricted for lack of trust, a notice appears once and the status bar shows Restricted. Hover it to see what is held back, and click it to choose. Manage Repository Trust in the command palette opens the same choice at any time.

Trust belongs to the repository, not to a worktree, so a new worktree of a trusted repository doesn’t ask again. Moving or replacing the repository’s folder means choosing again.

A trusted repository’s own solution files and project references are loaded as it names them, including ones in nested repositories.

In a repository you haven’t trusted, format on save doesn’t run Biome, Prettier or oxfmt, formatters from the project’s node_modules, or a formatter override that names a file by its path in the repository, and a Python installed through a version manager such as pyenv shows its global version in the status bar.

Trust a repository only if you would be willing to run its code yourself. Language servers that depend on trust restart as soon as you choose.

Stop trusting a repository

A trusted repository shows a shield in the status bar. Click it, or run Manage Repository Trust, to stop trusting it. Language servers that depend on trust restart restricted.

What trust does not do

Trust lets those features run code that is already in the repository. It doesn’t let Loxel download or install anything: dependencies and toolchains stay yours to install, in a repository you trust as in any other.

Nothing in a repository can mark itself as trusted. Your answer is stored in Loxel’s own state on your machine and is never sent anywhere.