Context bloating.

[schizoidcock]

This project is really good, but it needs more tests, i did used it with the hooks and the instructions, but feel that it bloated the context pretty quick in less than 3 hours of coding with claude, never happened that before, hit the limit in 2 hours mostly when i spend almost half a day without noticing.

[JordanCoin]

@schizoidcock Thanks for the comment, have been taking some time looking at this and version 4.0.5 has the latest changes here:

• Bounded watch daemon memory/event retention (MaxDaemonEvents, capped state recent events).
• Trimmed oversized .codemap/events.log and changed hook reads to tail-only.
• Added gitignore-aware watch/event filtering (including ignored nested directories).
• Removed expensive fallback scans from interactive hooks to avoid sudden context blowups.
• Added hook timeout fail-open behavior so hooks don’t block the coding session indefinitely.
• Added stale-daemon restart safety checks and ownership validation before stop/restart.
• Capped diff hook output so very large diffs don’t flood context.
• Expanded tests around hooks/watch limits and added CI coverage enforcement.

If your still seeing bloat from hooks let me know with: repo shape (Especially large ignored dirs / nested .git), which hook was running, how many files, and if you've set CODEMAP_HOOK_TIMEOUT

will try to keep iterating on this until its good

[schizoidcock]

I will do a check and let u know about it