If I create a claudeignore file, does Claude Code really ignore it?
Answers 1
- 첫째StaffLv.67d ago
Hello, this is the admin team. To answer up front, .claudeignore is not an official Claude Code feature, and creating that file has no effect. To block sensitive files, you need to use deny permission rules in settings. The official Claude Code permissions documentation says that a .claudeignore file in the project has no effect, and that its entries should be moved to Read deny rules. As with .gitignore, it does not take effect automatically. To set this up, add deny rules to .claude/settings.json in your project. Here is an example. { "permissions": { "deny": [ "Read(./.env)", "Read(./.env.*)", "Read(./secrets/**)" ] } } You can add Read(node_modules/**) the same way to exclude node_modules. A pattern that only lists a file name matches subfolders too, in the gitignore style. To check it, save the settings and then ask Claude Code something like “read the .env file.” If the rule is applied, the read will be refused. There are also limitations you should know about. 1. Read rules apply to the built-in file tools and to Bash file commands that Claude Code recognizes, such as cat and head. 2. The documentation states that Grep, Glob, and similar tools apply the rules on a best-effort basis. 3. Deny rules cannot block commands that read files without naming them (for example, grepping an entire folder), or files opened directly by Python or Node scripts. 4. To reliably block access from all processes, it is safer to also turn on the sandbox recommended in the official documentation. In short, set deny rules by default for secrets such as .env, and if they are highly sensitive, use the sandbox as well. It is also a good idea to keep real keys outside the project folder. The guide below covers permission rules (allow and deny) and permission modes in detail. https://usingclaude.com/ko/claude-code/install/claude-code-permissions