github / github/copilot-cli

MCP server unavailable is reported as "waiting on ide" and hangs copilot-cli

未关闭
#4,552 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

triage
主要语言
Shell
星标
11.2k
派生
1.9k
平均合并
14 小时 16 分钟
30 天内合并 PR
6

描述

Describe the bug

If you have an entry like this in your ~/.copilot/mcp-config.json

    "dummy": {
      "tools": [
        "*"
      ],
      "type": "http",
      "url": "http://bextop17:4000/mcp",
      "headers": {
        "Authorization": "Bearer token"
      }
    }

And the host is unavailable (it is in DNS but the system as a whole is unreachable) then copilot will hang on startup eventually showing the message "waiting on ide." IDE is not in use.

Important: using a non-existent dns name will NOT recreate this error. The host must be defined in DNS and not available. Using an existing host with a down service (system up, but port not) will NOT recreate this. My tests were confirmed by unplugging a system next to me's ethernet cable.

Affected version

GitHub Copilot CLI 1.0.81-6

Steps to reproduce the behavior
  1. Define an mcp server for a system that has a valid dns name but is not on the network
  2. start copilot cli
  3. see error
Expected behavior

The cli should report the correct error message and not hang on a missing mcp server.

Additional context

This is on MacOS 15.7.7 (24G720) connecting to an mcp server on my local network which I had unplugged from the network for $reasons. This left the name in DNS but the system unavailable.

贡献指南

打开贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

调研方向

从连接到已配置 MCP 服务器的 CLI 启动路径开始,然后使用一个可通过 DNS 解析但在网络上无法访问的主机重现该问题。完成的标准是 CLI 准确报告 MCP 连接失败,并继续运行,不会挂起或错误地显示 "waiting on ide."。

由索引模型根据 Issue 内容生成。

评估

技术栈
macos
领域
cli, networking
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
活跃
描述清晰度
基本清楚
新手友好度
58/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。