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

Delegated subagent sessions cannot load any skill: built-in worker/explore/verifier roles omit the skill tool

Abierto Apto para principiantes
  • ¿Algo no está bien?
#556 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
76/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript
Área
ai-infra-agents, developer-experience

Línea de trabajo

Lee packages/local-runtime-v2/assets/agents/{worker,explore,verifier}/agent.md y compara la configuración de herramientas y skills con la sesión raíz. Comprueba cómo se exponen la herramienta nativa skill y el catálogo de skills a las sesiones delegadas. Se considera terminado cuando un worker delegado puede cargar un skill instalado mediante la herramienta y la configuración de explore/verifier permite el acceso compartido previsto a los skills.

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

Descripción

Product or interface

Subagent delegation — the task tool and the built-in worker / explore / verifier roles — and the native skill tool.

Use case and problem

I use MiniMax Code as a long-running personal assistant and delegate almost all real work to subagents (task → worker / explore / verifier). Third-party skills are how I encode repeatable procedures (TDD, code review, debugging, planning), so that every delegated task follows the same process instead of reinventing it.

Delegated children currently cannot load any skill at all.

The built-in roles are defined in packages/local-runtime-v2/assets/agents/{worker,explore,verifier}/agent.md (verified at 50448abe), and their tools: lists do not contain the native skill tool:

  • worker/agent.md → read, write, edit, bash, task_query, task_output, task_stop, grep, glob, todowrite, web_fetch, website_deploy
  • explore/agent.md → bash, read, grep, glob, web_fetch, plus builtinTools: [] and skills: []
  • verifier/agent.md → read, grep, glob, bash, task_query, task_output, task_stop, web_fetch, plus builtinTools: [] and skills: []

Measured on my machine (desktop app, Windows): I ran four parallel delegated tasks with plain natural prompts — implement a function with tests, fix a failing test, review a diff, and plan a feature. Across 88 tool calls in 4 child sessions the skill tool was invoked 0 times. The tool schema actually offered to the child was:

bash, edit, glob, grep, mcp_invoke, read, tool_search, web_fetch, web_search, website_deploy, write

The only way a skill procedure reached a child was the child reading the SKILL.md file by hand, after tool_search for a skill loader returned {"hits":[],"total":0} — i.e. it went around the platform instead of through it. That works, but it is luck: it depends on the child happening to guess that the file exists, and the child never learns that the native loader exists.

Worth noting: packages/agent-tools/src/desktop/canonical-tool-policy.ts does not mention skill at all (the file is 80 lines and contains no occurrence of the string), so the policy layer is not what blocks it. The only gate is the per-role tools: list, so this looks like a one-line-per-role change rather than a policy decision.

The same gap applies to skills: [] on explore and verifier: even if the skill tool were listed, an explicit empty skills: array means there is no catalog to load from.

Desired behavior
  • A delegated child session can load a skill with the native skill tool, exactly like the root mavis session can.
  • skills: [] in explore/agent.md / verifier/agent.md either exposes the catalog, or is replaced by an explicit opt-out mechanism, so a delegated verifier can run a shared review procedure instead of improvising one.
  • Acceptance criteria: a delegated worker assigned a task that is covered by an installed skill invokes skill({ name }) for it without reading the file path by hand, and the returned SKILL.md content is visible in the child's context.
Platform

Desktop app 3.1.7.195 on Windows 11 x64. Source references are against upstream commit 50448abe (2026-10-29).

Reporter MMX UID: 500063342928973827

Alternatives and additional context

I worked around this today by creating three custom roles under agents/<name>/agent.md that add skill to tools: and drop skills: [], and delegating to those instead of the built-ins. It works, but every user has to re-create the built-in roles to get skill support, and the workaround is not discoverable from the product or from the built-in role descriptions.

Related, and worth checking in the same area: the official plugin packages that are published for MiniMax Code drop the upstream hooks/ directory, so a plugin that relies on a SessionStart hook can never fire in the desktop app. I filed that separately since it is a packaging problem rather than an agent-configuration one.

Lenguaje dominante
TypeScript
Estrellas
2.1k
Forks
271
Merge medio
14 h 23 min
PR fusionados (30 d)
35

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 MiniMax-AI/minimax-code

Todos los issues de MiniMax-AI/minimax-code

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.