github / github/copilot-cli

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

Open Beginner friendly
#4,729 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area:agents area:mcp
Dominant language
Shell
Stars
11.2k
Forks
1.9k
Avg merge
14h 16m
Merged PRs (30d)
6

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect ~/.copilot/pkg/linux-x64/1.0.83-3/definitions/research.agent.yaml and compare its github/get_me instruction with the listed GitHub MCP tools. Done means the packaged research-agent prompt no longer requires an unavailable identity tool, or names an available replacement; verify by running the research subagent with reasoning display enabled.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
cli, tooling
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.