Alright, so I finally got around to testing Cline's `.clineignore` feature after it kept trying to refactor my `node_modules` directory. 😅 That's like offering to reorganize a hoarder's garage—admirable, but a terrible idea.
The setup is straightforward, similar to a `.gitignore` file. You create a `.clineignore` file in your project root. Each line is a pattern. Cline won't read files or directories matching these patterns when scanning your codebase for context.
Here's my example from a web project with a hefty `vendor` directory and some auto-generated gunk:
```txt
# Dependencies
node_modules/
vendor/
*.pyc
# Build outputs
dist/
.next/
out/
# Environment and secrets
.env*
*.pem
# Ignore massive log directories
**/logs/
```
The key is using it to keep Cline's context window focused and, let's be honest, to stop it from generating "helpful" suggestions about the 10,000-line package-lock.json file you're never going to touch.
One pro-tip: This isn't just for size. It's for security. Make sure patterns for `.env` files or secret keys are in there unless you fancy an AI assistant casually referencing your API keys in a code suggestion. Been there, done that, rotated the credentials.
Has anyone else found clever patterns or run into issues where Cline still peeked where it shouldn't? I'm still tweaking mine for some tricky Terraform `.tfstate` backups.
- tm
Oh wow, the security tip is something I wouldn't have thought about right away. I've been so focused on just keeping it from reading huge files that I didn't even consider secrets. That's a really good point.
Does the `.clineignore` file also work for single files, or is it mostly for directories? Like, if I have a giant `CHANGELOG.md` I never want it to read, can I just add `CHANGELOG.md` on its own line?
Yep, it works for single files too! You can absolutely just add `CHANGELOG.md`. I just tested it with a config file in my terraform project.
>if I have a giant `CHANGELOG.md` I never want it to read
I did exactly this for a huge `.terraform.lock.hcl` file. Just added that filename and it stopped picking it up. Seems like the pattern matching works the same as gitignore.
Side question - does anyone know if you need to restart Cline after editing `.clineignore`, or does it pick up changes automatically?
Good question about restarting. From my own testing and what I've seen in the community, Cline does typically need a fresh chat window to pick up changes to `.clineignore`. So you'd close the current conversation and start a new one; it reads the ignore file again when it initializes context.
That's a great example with `.terraform.lock.hcl`, by the way. It really highlights how this isn't just for performance, but also for keeping the AI's focus on the actual source code, not generated lockfiles or manifests.
Stay curious.