Using the copilot language server sdk causes users to be blocked

[gpetrov]

We have implemented the GitHub copilot language server sdk in our low code editor Wappler and now some of the users report that their GitHub copilot access has been suspended.

Some even haven't tried any completions yet but get this after successful sign in and authorization:

"Contact Support you are currently logged in as XXXX"

And then they receive an email:

"Recent activity on your account has caught the attention of our abuse-detection systems. This activity may have included use of Copilot via scripted interactions, an otherwise deliberately unusual or strenuous nature, or use of multiple accounts to circumvent usage limits.

Due to this, we have suspended your access to Copilot."

What is going on? We aren't violating any terms of usage!

The point of the whole language server sdk was to integrate it in other editors than vscode as well right? As announced in:

https://github.blog/changelog/2025-02-10-copilot-language-server-sdk-is-now-available/

@tpope Any clearance about this?

[tpope]

Support is going to be your best bet here. But can you tell me what you are using as editorPluginInfo and editorInfo? And are you using any APIs that aren't expressly documented in the README?

[gpetrov]

We are following the sign-in procedure as described in https://github.com/github/copilot-language-server-release?tab=readme-ov-file#authentication and the authorization goes just fine.

Then we are passing current open documents of the user with textDocument/didOpen as per https://github.com/github/copilot-language-server-release?tab=readme-ov-file#text-document-synchronization

and the inline completions come in and work all fine with our monaco code editor integration.

As for the initialization with editorPluginInfo and editorInfo we use:

const response = await this.sendRequest('initialize', {
      processId: process.pid,
      workspaceFolders: null,
      capabilities: {
        workspace: { workspaceFolders: false },
        window: { showDocument: { support: true }},
      },
      initializationOptions: {
        editorInfo: {
          name: 'Wappler',
          version: '7.0.0',
        },
        editorPluginInfo: {
          name: 'Custom Copilot Integration',
          version: '0.0.0',
        },
      },
    });

Is this ok? Should we use something else?

Support is already contacted by few of our users.

I did notice that most of the users that got blocked were on the free github copilot plan. But even if they wanted to update to pro, it was denied because they were blocked ...

Are there maybe more restrictions to the free accounts? Shouldn't be all be solved by just rate limiting?

[tpope]

Is this ok? Should we use something else?

I would use something more specific for editorPluginInfo (repeating editorInfo would be fine), but I wouldn't expect that to be a factor here.

Wappler appears to be a technology partner of GitHub? I would reach out to your contact there if you have one. If not I would create your own support ticket. Either way specifically mention Copilot Language Server. I can't discuss the mechanics of abuse detection here.

[gpetrov]

Thanks @tpope, we are indeed GitHub technology partners and I will follow this up there.

Please do also make an internal issue as well, so this get resolved asap.

I will also adjust the editor settings but as those rules weren't mentioned in the guidelines so i doubt it will have great effect.

Anyway we should make sure this never happens again as it breaks the trusted reputation in both our product and GitHub and we did quite a large promotion about the GitHub copilot services and now people got burned...