Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

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

Abierto
  • ¿Algo no está bien?
#2,778 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
55/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
C
Estrellas
45.8k
Forks
3.8k
Merge medio
3 d 6 h
PR fusionados (30 d)
201

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de DeusData/codebase-memory-mcp

Todos los issues de DeusData/codebase-memory-mcp

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.