<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "type::bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=type::bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary From VSCode IDE, when I select code section and use GitLab Duo tools from the right click, I see error in the chat window. I am selecting GitLab Duo -\> Explain tool which send '/ecplain' command to the chat window and it shows error code G3001. Sceenshot below Note - This was working before 18.8 and I started seeing this issue after our 18.8 release on .com. Initial investigation pointed to the duo membership or duo licenses not assigned which has not changed and this error is seen even after I validated that membership and licenses are properly assigned. Also, Duo Agentic Chat works fine. {width=900 height=320} Error Message in Language Server 2026-01-14T08:35:44:156 \[debug\]: \[SecretRedactor\] redacting secret in file:///Users/manjeet/mywork/demo-delphi/customer-onboarding/scripts/backfill-coverage-history.js 2026-01-14T08:35:44:160 \[debug\]: \[OpenTabsService\] uri file:///Users/manjeet/mywork/demo-delphi/customer-onboarding/scripts/backfill-coverage-history.js was updated in the LRU cache with onDidSetActive 2026-01-14T08:35:52:983 \[debug\]: \[WebviewInstanceMessageBus:duo-chat-v2:a2200090-e82e-488e-b7e1-077e49b30dd4\] Sending notification: focusChat 2026-01-14T08:35:52:985 \[debug\]: \[SecretContextTransformer\] Transforming context item "editor_selection:scripts/backfill-coverage-history.js_e8f36548-70d4-47b2-a9a7-d6acb8f894fa" 2026-01-14T08:35:52:985 \[debug\]: \[SecretRedactor\] redacting secret in editor_selection:scripts/backfill-coverage-history.js_e8f36548-70d4-47b2-a9a7-d6acb8f894fa 2026-01-14T08:35:52:985 \[debug\]: \[WebviewInstanceMessageBus:duo-chat-v2:a2200090-e82e-488e-b7e1-077e49b30dd4\] Sending notification: focusChat 2026-01-14T08:35:52:985 \[info\]: ChatContextManager clearing all selected context items 2026-01-14T08:35:52:985 \[info\]: ChatContextManager returning 11 available context provider categories: "file, file, dependency, directory, snippet, issue, file, local_git, merge_request, repository, snippet" 2026-01-14T08:35:52:985 \[info\]: ContextItems: refreshing current context item selections 2026-01-14T08:35:52:985 \[debug\]: GitLabChatApi: subscribeToUpdates, additionalContextEnabled: true 2026-01-14T08:35:52:987 \[info\]: ChatContextManager returning 0 current context items 2026-01-14T08:35:52:987 \[debug\]: \[WebviewInstanceMessageBus:duo-chat-v2:a2200090-e82e-488e-b7e1-077e49b30dd4\] Sending notification: contextCurrentItemsResult 2026-01-14T08:35:53:235 \[info\]: Duo Chat: successfully subscribed to updates 2026-01-14T08:35:53:235 \[info\]: ChatContextManager returning 11 available context provider categories: "file, file, dependency, directory, snippet, issue, file, local_git, merge_request, repository, snippet" 2026-01-14T08:35:53:235 \[debug\]: \[SimpleApiClient\] Making GraphQL request: mutation: chat 2026-01-14T08:35:53:236 \[debug\]: fetch: request for https://gitlab.com/api/graphql made with https agent. 2026-01-14T08:35:53:648 \[debug\]: fetch: request to https://gitlab.com/api/graphql returned HTTP 200 after 411 ms 2026-01-14T08:35:53:651 \[debug\]: \[WebviewInstanceMessageBus:duo-chat-v2:a2200090-e82e-488e-b7e1-077e49b30dd4\] Sending notification: newRecord 2026-01-14T08:35:53:653 \[debug\]: \[WebviewInstanceMessageBus:duo-chat-v2:a2200090-e82e-488e-b7e1-077e49b30dd4\] Sending notification: newRecord 2026-01-14T08:35:54:251 \[debug\]: \[WebviewInstanceMessageBus:duo-chat-v2:a2200090-e82e-488e-b7e1-077e49b30dd4\] Sending notification: updateRecord ### {width=719 height=447} ### Steps to reproduce Select the code, right click to launch the menu, select GitLab Duo -\> explain ### Example Project <!--If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version.--> ### What is the current _bug_ behavior? <!--Describe what actually happens.--> ### What is the expected _correct_ behavior? <!--Describe what you should see instead.--> ### Relevant logs and/or screenshots <!--Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough to read otherwise.--> ### Output of checks <!--If you are reporting a bug on GitLab.com, uncomment below--> <!--This bug happens on GitLab.com--> <!--and uncomment below if you have /label privileges--> <!--/label ~"reproduced on GitLab.com"--> <!--or follow up with an issue comment of `@gitlab-bot label ~"reproduced on GitLab.com"` if you do not--> #### Results of GitLab environment info <!--Input any relevant GitLab environment information if needed.--> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:env:info\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\`) </pre> </details> #### Results of GitLab application Check <!--Input any relevant GitLab application check information if needed.--> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!--If you can, link to the line of code that might be responsible for the problem.--> ### Patch release information for backports If the bug fix needs to be backported in a [patch release](https://handbook.gitlab.com/handbook/engineering/releases/patch-releases) to a version under [the maintenance policy](https://docs.gitlab.com/policy/maintenance/), please follow the steps on the [patch release runbook for GitLab engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/patch/engineers.md). Refer to the [internal "Release Information" dashboard](https://dashboards.gitlab.net/d/delivery-release_info/delivery3a-release-information?orgId=1) for information about the next patch release, including the targeted versions, expected release date, and current status. #### High-severity bug remediation To remediate high-severity issues requiring an [internal release](https://handbook.gitlab.com/handbook/engineering/releases/internal-releases/) for single-tenant SaaS instances, refer to the [internal release process for engineers](https://gitlab.com/gitlab-org/release/docs/-/blob/master/general/internal-releases/engineers.md?ref_type=heads). <!--If you don't have /label privileges, follow up with an issue comment of `@gitlab-bot label ~"type::bug"`-->