[Bug] Chat fails with "No model configuration found" on Copilot Free; model picker is empty (works in VS Code with same account)

Geschlossen
  • Stimmt etwas nicht?
#513 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 2 Tagen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
48/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java
Bereich
backend-api-design

Rechercherichtung

The report points to the Copilot language server’s model configuration lookup: AutoModelService fetches a model, but chat cannot find its configuration. Start by tracing how the Eclipse plugin supplies available models to the language server and compare that flow with the reported VS Code behavior. Done means Copilot Free models appear in both Agent and Ask mode and a chat message receives a response; the issue names no source files or tests.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug

Environment

  • Plugin version: 0.21.0.202608060743 (com.microsoft.copilot.eclipse.feature.feature.group)
  • Eclipse IDE: 2026-09 (4.41.0), build id 20260903-0719 (Eclipse IDE for Java Developers)
  • OS: Windows, win32 x86_64
  • Java: 25.0.4.1 (Eclipse Adoptium)
  • Locale: it_IT
  • GitHub plan: Copilot Free

Describe the bug
Signed in with a GitHub Copilot Free account, the Copilot Chat view shows "No model configuration found" as soon as I send a message. The model picker is empty in both Agent and Ask modes. The same GitHub account works correctly in VS Code (models are listed and chat replies).

To Reproduce
Steps to reproduce the behavior:

  1. Install GitHub Copilot from the Eclipse Marketplace and sign in.
  2. Open the Chat view and send any message (e.g. "hello").
  3. The chat shows "No model configuration found".

Expected behavior
The model picker lists the models available to the Free plan and the chat responds.

Actual behavior

  • Chat shows "No model configuration found".
  • The model picker shows no models in Agent or Ask mode.
  • Window > Preferences > GitHub Copilot > Model Management lists only the custom-model providers (Azure, Ollama, OpenAI, Anthropic, OpenRouter, Gemini, Groq), with no models.

Logs

Earlier in the session, the Auto model is fetched successfully:

[LS:GitHub Copilot Language Server][Info] [AutoModelService] Fetched auto model for reserve in 433ms: mai-code-1.1-flash

Then, when sending a chat message:

[LS:GitHub Copilot Language Server][Error] [chat] Error processing turn 2206e965-974f-4809-ab81-b7eaec596632 Error: No model configuration found
    at qKe.getBestChatModelConfig (C:\snapshot\copilot-language-server-internal\dist\main.js:2436:12998)
    at async t.resolveModelConfiguration (C:\snapshot\copilot-language-server-internal\dist\main.js:2582:6346)
    at async ModelPickerUtils.getModelConfigurationById (C:\snapshot\copilot-language-server-internal\dist\main.js:2582:9562)
    at async fPe.processWithModelAndToolCall (C:\snapshot\copilot-language-server-internal\dist\main.js:3765:17405)
    at async fPe.process (C:\snapshot\copilot-language-server-internal\dist\main.js:3765:15760)
    at async handleConversationTurnChecked (C:\snapshot\copilot-language-server-internal\dist\main.js:4111:20552)
    at async tr.messageHandler (C:\snapshot\copilot-language-server-internal\dist\main.js:4237:89134)

Additional context

  • Authentication works: the signed-in user name is shown in the Chat view.
  • The same account works in VS Code with GitHub Copilot Chat.
  • Steps tried: switching from Agent to Ask mode, starting a New Chat, checking Model Management preferences, restarting Eclipse with -clean.
Vorherrschende Sprache
Java
Sterne
129
Forks
70
Ø Merge
3 T. 2 Std.
Gemergte PRs (30 T.)
15

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus microsoft/copilot-for-eclipse

Alle Issues in microsoft/copilot-for-eclipse

Ähnliche Issues

Weitere Issues zu Java

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.