github / github/copilot-cli

Built-in research agent tells subagents to call unavailable github/get_me tool

Abierto Apto para principiantes
#4,729 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

area:agents area:mcp
Lenguaje dominante
Shell
Estrellas
11.2k
Forks
1.9k
Merge medio
14 h 16 min
PR fusionados (30 d)
6

Descripción

Describe the bug

The built-in research subagent prompt tells the agent to call github/get_me first, but the GitHub MCP server exposed in the same CLI session does not provide that tool. With reasoning display enabled, the subagent visibly starts by trying to reconcile the mismatch and leaks scratchpad text like:

**Resolving function conflicts** I see that I need to call the GitHub function "get_me" first, according to the subagent instructions. However, it looks like there are only five listed GitHub functions...

This appears to be a packaged agent/tool mismatch: the built-in research-agent instructions reference an older or differently named GitHub MCP tool.

Affected version

1.0.83-3 on Linux x64.

Local evidence

Packaged agent definition:

~/.copilot/pkg/linux-x64/1.0.83-3/definitions/research.agent.yaml

Relevant prompt section:

## Critical: Work Autonomously

You work completely autonomously:
- Call `github/get_me` first to understand the user's org and identity context

The current GitHub MCP server visible to the agent exposes only these tools:

github-mcp-server-get_copilot_space
github-mcp-server-get_file_contents
github-mcp-server-list_copilot_spaces
github-mcp-server-search_code
github-mcp-server-search_users

There is no github/get_me or equivalent identity/profile tool in the available GitHub tool definitions.

Expected behavior

The built-in research-agent prompt should only instruct the subagent to call tools that are actually available in the packaged/default GitHub MCP server, or it should use the current tool namespace/name. If user identity context is unavailable, the prompt should not require a nonexistent first call.

Actual behavior

The research subagent receives an instruction to call github/get_me, cannot find the tool among the available GitHub MCP tools, and starts with visible conflict-resolution reasoning when reasoning display is enabled.

Related issues

Possibly related, but not exact:

  • #4076: built-in research agent MCP/tool configurability
  • #2630: subagent MCP tool availability in custom-agent / prompt contexts
  • #4604: get_me with user-configured GitHub MCP auth/token injection

This issue is specifically about the packaged built-in research.agent.yaml prompt referencing github/get_me when the available built-in GitHub MCP tool list does not include it.

Guía de contribución

Abrir la guía de contribución

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.

Línea de trabajo

Inspecciona ~/.copilot/pkg/linux-x64/1.0.83-3/definitions/research.agent.yaml y compara su instrucción github/get_me con las herramientas de GitHub MCP indicadas. Se considera completado cuando el prompt del research-agent empaquetado ya no requiere una herramienta de identidad no disponible o nombra un reemplazo disponible; verifícalo ejecutando el research subagent con reasoning display habilitado.

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

Evaluación

Stack tecnológico
github
Área
cli, tooling
Tipo de issue
Error
Dificultad
2/5
Tiempo estimado
1-3 horas
Estado de actividad
Activo
Claridad
Bastante claro
Aptitud para principiantes
72/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.