[Regression] Unknown tokenizer: undefined

Open
#321,945 1 comment 1 reaction 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

ai-analyzed ai-generated bug error-telemetry

Error Message

unhandlederror-Unknown tokenizer: undefined

Stack Trace

    at gG.acquireTokenizer (../src/platform/tokenizer/node/tokenizer.ts:82:10)
    at new on (../src/extension/prompts/node/base/promptRenderer.ts:90:38)
    at (anonymous) (../src/extension/prompts/node/base/promptRenderer.ts:69:18)
    at fn (./src/vs/platform/instantiation/common/instantiationService.ts:111:10)
    at on.create (../src/extension/prompts/node/base/promptRenderer.ts:67:30)
    at FG._provideLanguageModelResponse (../src/extension/conversation/vscode-node/languageModelAccess.ts:657:56)
    at async FG.provideLanguageModelResponse (../src/extension/conversation/vscode-node/languageModelAccess.ts:853:16)

Raw Stack Trace (minified)
Error: Unknown tokenizer: undefined 	at gG.acquireTokenizer (\extensions\copilot\dist\extension.js:1682:34399) 	at new on (\extensions\copilot\dist\extension.js:1686:16373) 	at \extensions\copilot\dist\extension.js:1686:16724 	at n.invokeFunction (\extensions\copilot\dist\extension.js:29:944) 	at on.create (\extensions\copilot\dist\extension.js:1686:16687) 	at FG._provideLanguageModelResponse (\extensions\copilot\dist\extension.js:1710:11653) 	at async FG.provideLanguageModelResponse (\extensions\copilot\dist\extension.js:1710:15097)

Details

Property Value
Bucket ID f969dd59-a13a-f94e-2982-6394d7b51e19
Version 1.125.0
Commit 93cfdd48
Last Seen Wed Jun 17 2026 23:58:56 GMT+0000 (Coordinated Universal Time)
Platforms Mac, Windows, Linux
Product VSCode

This issue was automatically created from the VS Code Errors Dashboard

Dominant language
TypeScript
Stars
193k
Forks
42.9k
PR merge metrics
PR metrics pending

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.

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.