.gitignore, auto approve, mcp

[archasek]

Hi, FAQ/wiki pages arent 100% comprehensive and is contradictory I guess.

1. Should I commit .drift/indexes and .drift/boundaries? what about .drift/views?
2. How to set up auto pattern approve?

"learning": {
    "autoApproveThreshold":

or

 "patterns": {
   "minConfidence": 0.7,
   "autoApprove": false
 },

3. Does MCP work fine? For me not, and I'm getting this when running it as in docs (trying from terminal below):

❯ npx -y driftdetect-mcp
npm error could not determine executable to run
npm error A complete log of this run can be found in: /home/xx/.npm/_logs/2026-01-27T15_40_55_304Z-debug-0.log

Thanks

[dadbodgeoff]

Hey! I've updated the wiki guide a bit an treid to make it more clear! As far as what .gitignore should follow id reccomend the following

What to commit:

config.json, patterns/approved/, boundaries/, indexes/, views/, constraints/approved/
Don't commit: lake/, cache/, history/, call-graph/
Auto-approve config:

Use learning.autoApproveThreshold: 0.95 (recommended)
The older patterns.autoApprove is deprecated but still works
You can reply to the issue pointing them to the updated FAQ and Configuration pages.

[archasek]

@dadbodgeoff thanks. what about MCP? I've just added #3 in the issue :)

[dadbodgeoff]

I just had to push a fix on for MCP there was a bug with npx command. Its working now for me can you please verify :)

The driftdetect-mcp@0.9.22 package:

Has the correct bin entry (driftdetect-mcp →
server.js
)
Starts successfully via npx -y driftdetect-mcp

npm cache clean --force
npx -y driftdetect-mcp@0.9.22

@archasek hope this helps!

[archasek]

@dadbodgeoff thx.

1. still docs is out of sync with reality, e.g. drift security-summary... very confusing
2. regarding gitignore... i am not sure on what you said. still I see .drift/patterns/approved/.backups stuff ready to be committed. so i guess more general pattern should be applied here. my current setup:

.drift/lake/
.drift/cache/
.drift/history/
.drift/call-graph/
!.drift/config.json
!.drift/patterns/approved/
!.drift/boundaries/
!.drift/indexes/
!.drift/views/
!.drift/constraints/approved/

there's a simpler way (and more long-term stable) i hope
3. shouldn't .driftignore use .gitignore by default?

[dadbodgeoff]

Hey Arc,

I appreciate your feedback today. Its exactly the type of feedback I need to help professionalize and smooth off some of the edges. Over the last week its been trying to get everyones languages, frameworks etc and still trying to document and leave breadcrumbs along the way I feel as those "roots" of drift is now there. Now its about helping smooth out the edges, act quickly on edge cases and tie off loose "notches" like these. although I am sure it can be frustrating to deal with I hope that the fixes so far have sufficed and based off your feedback in your previous messages heres what i've been able to push through.
Trying to be as thoughful as possible and hope this helps!

v0.9.24 Changes

1. Docs out of sync with CLI

Fixed drift security-summary in README → now drift boundaries sensitive
Removed drift decisions from CLI-Reference (it's MCP-only)
Added pnpm validate-docs script + CI check to catch future doc drift
2. .gitignore / .backups issue

Updated FAQ with simpler explicit ignore pattern (no confusing negations)
Added .drift/**/.backups/ to recommended ignores
drift init now prints the recommended .gitignore additions after setup
3. .driftignore + .gitignore

Documented that .gitignore is already respected by default (was undocumented)
New recommended .gitignore:

.drift/lake/
.drift/cache/
.drift/history/
.drift/call-graph/
.drift/patterns/discovered/
.drift/patterns/ignored/
.drift/patterns/variants/
.drift/constraints/discovered/
.drift/constraints/ignored/
.drift/contracts/discovered/
.drift/contracts/ignored/
.drift/contracts/mismatch/
.drift/**/.backups/

[dadbodgeoff]

Also goign to look at a way for beign more selective on the MCP tools you load into context windows preserver that aspect as well but still have it so its user friendly with no friction

[dadbodgeoff]

v0.9.27 shipped with intelligent tool filtering:

Zero config - automatically detects your project language from config files (tsconfig.json, go.mod, Cargo.toml, etc.)
41 core tools always available (patterns, security, impact analysis, etc.)
8 language tools filtered based on what you're actually using (drift_typescript, drift_python, drift_go, etc.)
Escape hatches if needed via
config.json
:
{ "mcp": { "tools": { "all": true } } } // expose everything
So a TypeScript project sees 42 tools instead of 49. A Go project sees 42. Multi-language monorepos get all relevant tools.

The goal: less noise for the AI, better tool selection, same full power when you need it.

[dadbodgeoff]

Wiki is now 100% decked out, it is all 100% up to date, fully optimzed and meant for a full udnerstanding of hwo eveyrthing works. Hope this is able to help out and thanks again for pushing me to be better! Would love your feedback