Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Feat] Expose/allow configuration of github.copilot.chat.virtualTools.threshold in Eclipse Copilot

未关闭
#449 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
java

调研方向

从 Eclipse 首选项集成开始,跟踪 github.copilot.chat.virtualTools.threshold 在 Copilot 聊天体验中的处理方式。确定应公开现有设置,还是应提供面向用户的工具预算选项,然后验证已配置的值可被发现,并能防止所报告的工具限制失败。

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

描述

enhancement

The Copilot chat integration currently fails when the virtual tool budget exceeds the default threshold, throwing:

“You may not include more than 128 tools in your request.”

This seems to be controlled by the internal setting github.copilot.chat.virtualTools.threshold, which is available in VS Code but not exposed in the Eclipse Copilot experience.

Problem:
• In large agent/chat sessions, the number of virtual tools can exceed the default limit.
• There is no visible way in Eclipse to lower or tune the threshold.
• This makes Copilot unusable in larger workspaces or when many tools are available.

Expected behavior:
• Allow users to configure github.copilot.chat.virtualTools.threshold from Eclipse preferences or a supported config mechanism.
• Or expose a simpler user-facing setting such as “Maximum virtual tools / tool budget.”
• Ideally, this should be adjustable without requiring undocumented internal settings.

Use case:
• Large projects with many tools or context providers.
• Users working in Eclipse who need to keep Copilot requests under the hard limit without being blocked by a fixed internal threshold.

Additional notes:
• The setting appears to be hidden/internal and not discoverable in the Eclipse UI.
• Having a supported configuration path would make the behavior predictable and reduce failures in real-world large-workspace usage.

主要语言
Java
星标
125
派生
63
平均合并
1 天 4 小时
30 天内合并 PR
4

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

microsoft/copilot-for-eclipse 的其他 Issue

查看 microsoft/copilot-for-eclipse 的全部 Issue

相似的 Issue

更多 Java Issue

把新 issue 发到你的邮箱

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