Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Test: BYOK models keep working when more than 128 tools are enabled

Closed Beginner friendly
#339,526 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@osortega is already working on this.

Since Oct 5, 2026.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
75/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
testing-qa

Research direction

Use the attached sample, which configures an MCP server with 150 tools, and follow the five manual test steps in the issue. Start by configuring a BYOK model and opening the sample folder; verify the response, warning visibility and Configure Tools destination, then stop the server and confirm a new session shows no warning.

Written by the indexing model from the issue text.

Description

testplan-item

Refs: #339184

  • anyOS

Complexity: 2

Authors: @vritant24

Create Issue


BYOK models in Copilot agent sessions used to fail when more than 128 tools were enabled. Now the extra tools are dropped and a warning is shown.

Setup

  1. Have a BYOK model configured (Chat: Manage Language Models).
  2. Unzip the attached sample and open its folder. It adds an MCP server with 150 tools and enables chat.agentHost.byokModels.enabled. Requires node.

Test

  1. In a new Copilot agent session, pick your BYOK model and send a message.
  2. Verify the response succeeds and shows the warning "The model only supports 128 tools, N tools were not provided to the model. Configure Tools".
  3. Verify the warning stays visible after the response completes (not inside Completed N steps).
  4. Click Configure Tools. Verify Customizations opens to Tools.
  5. Stop the many-tools server and start a new session. Verify no warning appears.
Dominant language
TypeScript
Stars
193k
Forks
44.1k
Avg merge
9h 26m
Merged PRs (30d)
654

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

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.

More from microsoft/vscode

All issues in microsoft/vscode

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.