.Dotfile protection setting gone?

Good morning all,

I cannot seem to find the .Dotfile protection setting anymore? it used to be under Agents → Auto run settings i believe, and i cannot find documentation or release notes that it changed. Is this intentional or should it be configured through .ignore files only?

We’re on the Team license and using version:

Version: 2.5.22
VSCode Version: 1.105.1
Commit: 0eda506a36f70f8dc866c1ea642fcaf620090080
Date: 2026-02-23T00:15:21.265Z
Build Type: Stable
Release Track: Early Access
Electron: 39.4.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Sincerely,

  • WS

There isn’t a separate dotfile-specific toggle anymore, they’ve consolidated file protection into the general file-scoping rules the agent follows (your project’s.gitignore, any.cursorignore, or workspace/file permission rules)

Thank you for your reply:) that’s good to know. Has this been communicated anywhere in release notes that i’m perhaps not aware of?

hi @woutersteven while the setting has been removed we still have dotfile protection but it can not be disabled.

As Chris also mentioned you can still use .gitignore, .cursorignore (agent) and .cursorindexingignore (index) for fine tuning what each part should be allow to access or not.

Thank you for your reply, does that mean that .Dotfile protection is intended to be always ON and will always be ON? or will it change in the (near) future?

From what I see there is no further change planned. Note that Agents may find other ways to access or change dotfiles (scripting, terminal,…) therefore ensure no critical info is accessible from your development environment.

Best practices include read only DB account if production data must be accessed.

What was the purpose for which you used the dotfile protection setting? Enabling or disabling it?

It was for enabling it and ensuring it was enabled in the team. But there are other ways to do that :slight_smile: We didn’t use it for disabling purposes.

1 Like