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

[Feature] Treat unknown or wrong-case names in [tools] disabled/enabled as errors

Abierto
#4,037 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
68/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
cli, tooling

Línea de trabajo

Start by locating the validation for the [tools].disabled and [tools].enabled configuration, then compare it with the configuration docs' tools section. Preserve exact-name matching and empty enabled-list behavior; done means unmatched, malformed, or wrong-case names fail with the existing warning text while naming the relevant entry or exact built-in name.

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

Descripción

What feature would you like to see?

When [tools].disabled (or [tools].enabled) contains a name that matches no built-in tool and no MCP tool, fail loudly — exit with an error or refuse to start the session — instead of only printing a warning.

Matching is case-sensitive today, so disabled = ["agent"] does not disable Agent, and the tool silently stays available.

Concretely: keep the current warning text, but make it a hard failure for the three shapes the docs already say never match:

  • a wildcard that is not an mcp__ pattern,
  • an mcp__ name missing the tool segment,
  • any name that no registered tool has.
Additional information

The configuration docs (tools section) say those shapes "are reported with a warning" and that matching is case-sensitive. A denylist that is silently inert after a one-character case mistake is exactly how a session keeps a tool the operator tried to turn off — including Agent and AgentSwarm.

Behaviour that should keep working: exact names such as disabled = ["Agent", "AgentSwarm"], and an empty enabled list still meaning "no allowlist constraint", as documented.

Suggested acceptance check: with disabled = ["agent"] the process refuses to run and the message suggests the exact built-in name Agent; with disabled = ["NoSuchTool"] it refuses and names the unmatched entry.

Lenguaje dominante
TypeScript
Estrellas
7.5k
Forks
1.2k
Merge medio
12 h 45 min
PR fusionados (30 d)
329

Preparar el entorno

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 MoonshotAI/kimi-code

Todos los issues de MoonshotAI/kimi-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.