Feature Request

Summary

Add support for project-level configuration via .claude-mem.json file to disable memory capture for specific projects.

Use Case

As a developer working on multiple projects, I need the ability to:

1. Disable memory entirely for certain projects (e.g., projects with sensitive data, temporary experiments)
2. Configure memory settings per-project without affecting global settings

Proposed Solution

Support a .claude-mem.json file in the project root with options like:

{
  "enabled": false,
  "reason": "Project contains sensitive client data"
}

Or with more granular control:

{
  "enabled": true,
  "captureObservations": false,
  "captureSessions": true,
  "capturePrompts": false
}

Expected Behavior

• When enabled: false, claude-mem hooks should skip all memory capture for that project
• The project should still appear in the database (for organizational purposes) but no observations/sessions/prompts should be stored
• Alternatively, support a global ignore pattern in ~/.claude-mem/settings.json:

  {
    "ignoredProjects": ["SensitiveProject", "TemporaryExperiment"]
  }

Current Workaround

Currently, users must manually delete project data from SQLite:

sqlite3 ~/.claude-mem/claude-mem.db "DELETE FROM observations WHERE project = 'ProjectName';"

This is not ideal as it requires post-hoc cleanup rather than prevention.

Additional Context

• This would align with how other tools (e.g., .gitignore, .npmrc) support project-level configuration
• Enterprise users may have compliance requirements to exclude certain projects from memory capture

Thank you for this excellent plugin! 🙏