Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

feat: config switch to suppress the Claude Code SessionStart/SubagentStart reminders (per user and per project)

Aperta
  • Qualcosa non va?
#2,778 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
55/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
c
Ambito
cli

Direzione di ricerca

Start in src/cli/cli.c at the reminder heredocs around L5748 and L5771, then trace how install registers those hooks and how hook-augment handles lifecycle events. Decide with maintainers which proposed opt-out and routing approach to implement; done means users can suppress the reminders per project and per user without breaking upgrades or other projects. No tests or specific test files are named in the issue.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

editor/integration enhancement ux/behavior

Problem

install registers two global Claude Code hooks in ~/.claude/settings.json (or $CLAUDE_CONFIG_DIR):

  • cbm-session-reminder: SessionStart on startup, resume, clear and compact
  • cbm-subagent-reminder: SubagentStart, every spawn

Both print fixed text (src/cli/cli.c, the reminder heredocs around L5748 and L5771). Claude Code merges hooks across settings scopes, so a project cannot turn off a user-level hook. Its own .claude/settings.json can only add hooks, never remove them. That leaves two options today:

  1. Edit the scripts. The installer then treats them as unowned (#1387) and stops updating them, so they quietly fall behind upstream.
  2. Deregister them globally, which removes them from every project, including ones that want them.

Why this matters

The reminders are a good default. They do conflict with projects that ship their own CMM routing guidance. In my case that's a hook stack that enforces graph-first navigation and has its own SessionStart and SubagentStart text. In those projects, every session and every subagent receives two sets of instructions that partly disagree. CMM's line is "Use Grep/Glob/Read for text, configs, and non-code files". The project's rules route text in indexed files (.md, config, .cgi) through search_code and keep grep for files CMM does not index. Agents follow whichever instruction they read last.

Proposal

Any one of these would solve it. They are listed smallest first.

  1. Project opt-out marker. The reminder scripts exit 0 silently when $CLAUDE_PROJECT_DIR/.codebase-memory/no-reminders exists, or a similarly named marker. That's one line per script, and nothing changes for anyone who doesn't create the file.
  2. Config key. Add codebase-memory-mcp config set agent_reminders false, read by the scripts or by hook-augment. A per-project override in the project's .codebase-memory/ config would be ideal.
  3. Route Claude Code through hook-augment. Copilot, Hermes and Kimi already get dynamic lifecycle context from hook-augment --event SessionStart. Pointing the Claude scripts there too, as exec "$BIN" hook-augment --event SessionStart|SubagentStart, would put the text in the binary. Upgrades would then update it without rewriting scripts, and the opt-out (1 or 2) would live in one place.

I'm happy to send a PR for whichever you prefer. My lean is (3) with (1) as the switch.

Lingua principale
C
Stelle
45.8k
Fork
3.8k
Merge medio
3g 16h
PR unite (30g)
203

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di DeusData/codebase-memory-mcp

Tutte le issue di DeusData/codebase-memory-mcp

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.