Feature request: allow skipping context injection per session

[github-actions[bot]]

Originally posted as issue #321 by @kamil-hassan201
#321

Currently, Claude-Mem automatically injects context from previous sessions at the start of every new session. There is no documented or supported way to start a “fresh” session without prior memory being injected.

This makes it difficult to:

• Explore ideas from scratch without bias from previous context
• Work on sensitive or experimental tasks where past memory should not influence the session
• Temporarily opt out of memory without uninstalling the plugin or creating a new project

---

Describe the solution you'd like

Add an explicit opt-out mechanism to skip context injection for a session.

The default behavior should remain unchanged, but users should have a clear and intentional way to start a clean session when needed.

---

Additional context

The documentation mentions “Context Configuration” and fine-grained control over injected context, but there is currently no visible or documented way to disable injection per session.

Adding this feature would improve user trust, flexibility, and usability—especially for exploratory, sensitive, or debugging workflows—without breaking existing behavior.

[joypeterson]

Adding another use case that I think argues for a global-disable option alongside the per-session mechanism described here.

I work across multiple large repositories (millions of lines of code each), frequently task-switching between development, code review, and design work using git worktrees. For me, context from the previous session is usually noise and wasted tokens — I'm rarely continuing yesterday's thread. The injection fires unconditionally on every SessionStart, and with CLAUDE_MEM_CONTEXT_SESSION_COUNT validated to a minimum of 1 (can't be zeroed out).

What I'd find useful is a two-level approach:

1. Global disable — a setting like CLAUDE_MEM_CONTEXT_ENABLED=false (or allow CLAUDE_MEM_CONTEXT_SESSION_COUNT=0) to suppress SessionStart injection by default.
2. On-demand opt-in — when globally disabled, a slash command like /mem context (or a session-start flag) to explicitly pull prior context when you actually want it.

This is the inverse of the current model, which is always-on with no escape hatch. For users like me where cross-session continuity is the exception rather than the rule, the default should be opt-in. The per-session skip described in this discussion handles the opposite case (usually-on, sometimes off) — both should exist.