Oops, your response got filtered. Vote down if you think this shouldn't have happened.

[account-2-Eason]

• VS Code Version:
• OS Version:
• Logs:

Steps to Reproduce:

1. I don't know why GitHub copilot displayed this bug.

[M0-09]

I am having the same bug

[M0-09]

[Bikatr7]

Yep, has been rendering Copilot as useless all morning.

Seems to have happened in the past too: https://github.com/microsoft/vscode-copilot-release/issues/583

[deciusworld]

is there a solution for this? "Oops, your response got filtered. Vote down if you think this shouldn't have happened."

[neurotic]

I have the same problem.

I don't know if the problem is with certain words, that the system believes are forbidden or if the response is too large, but it is really anoying.

It's a paid product, i cannot have this kind of error.

[scriptify]

Same here, no matter what I send. Product is basically unusable.

[binury]

@account-2-Eason would you please edit your OP & fill out the issue template?

VS Code Version: ___ ??

https://github.blog/changelog/label/copilot/#🌐-upcoming-deprecation-of-copilot-chat-api-endpoints

Versions 0.8.0 and later of the Copilot Chat extension for VS Code and versions 0.1.1817.27579 and later of the Copilot Chat extension for Visual Studio […]

Probably, you all need to update your vscode in order to install the new extension version.

ls ~/.vscode/extensions |grep chat

(Not to imply it should or should not but…) there is no warning or notification to users in vscode when the editor version is too old to install the latest version of an extension, and instead it will just download the newest compatible version.

{
 ⋮
  "engines": {
    "vscode": "^1.86.0-20240131", // 
    "npm": ">=9.0.0",
    "node": ">=18.0.0" 
 ⋮
}

This means you need to have (probably) the 2024 Jan. or Feb. release versions of vscode to download the new extension…

[binury]

Here is the latest (also, pre-release) version of the extension that has the updated endpoint set correctly:

chat-extension.zip

(I also lowered the (strict) engine requirement for vscode to some arbitrary older release that should cover most users.)

MacOS, Linux: extract the contents to ~/.vscode/extensions.

Windows: wipe HD, reinstall *nix, and then extract to ~/.vscode/extensions

YMMV; I don't have time to downgrade and validate compatibility— maybe the extension really is incompatible with the older vscode API or something. So, don't blame me 🙏 if it doesn't work for your old version of vscode.

[binury]

alternatively, can try editing the old extension

pushd ~/.vscode/extensions/github.copilot-chat-0.7.*
sed -i 's/copilot-proxy\.githubusercontent\.com/https:\/\/api\.githubcopilot\.com/g' dist/extension.js
popd

I was unable to manually install the old extension to verify because it erased the old extension's directory when I closed the application to regenerate the extension host

[Bikatr7]

@account-2-Eason would you please edit your OP & fill out the issue template?

VS Code Version: ___ ??

https://github.blog/changelog/label/copilot/#🌐-upcoming-deprecation-of-copilot-chat-api-endpoints

Versions 0.8.0 and later of the Copilot Chat extension for VS Code and versions 0.1.1817.27579 and later of the Copilot Chat extension for Visual Studio […]

Probably, you all need to update your vscode in order to install the new extension version.

ls ~/.vscode/extensions |grep chat

(Not to imply it should or should not but…) there is no warning or notification to users in vscode when the editor version is too old to install the latest version of an extension, and instead it will just download the newest compatible version.

{
 ⋮
  "engines": {
    "vscode": "^1.86.0-20240131", // 
    "npm": ">=9.0.0",
    "node": ">=18.0.0" 
 ⋮
}

This means you need to have (probably) the 2024 Jan. or Feb. release versions of vscode to download the new extension…

Did all of this, my vscode is seemingly on the most recent version, i updated both copilot and copilot chat to their latest versions, and then even tried the pre-release version. Issue still persists

[binury]

@Bikatr7 it's hard to confidently extrapolate any meaning from "latest"; please post the specific versions of vcode and the copilot extensions you are using

[Bikatr7]

@Bikatr7 it's hard to confidently extrapolate any meaning from "latest"; please post the specific versions of vcode and the copilot extensions you are using

Sorry.

Is this sufficient?

I'm not really sure how to check such things.

[binury]

@Bikatr7 it's hard to confidently extrapolate any meaning from "latest"; please post the specific versions of vcode and the copilot extensions you are using

Sorry.

Is this sufficient?

I'm not really sure how to check such things.

Perfect. Thanks. Those seem to be the latest stable release versions. But, from your second screenshot, it seems like you are having a different issue from this thread? https://github.com/microsoft/vscode-copilot-release/issues/583#issuecomment-1894487558

[Bikatr7]

@Bikatr7 it's hard to confidently extrapolate any meaning from "latest"; please post the specific versions of vcode and the copilot extensions you are using

Sorry. Is this sufficient? I'm not really sure how to check such things.

Perfect. Thanks. Those seem to be the latest stable release versions. But, from your second screenshot, it seems like you are having a different issue from this thread? #583 (comment)

Yeah, it seems to have switched on me, It was filtering earlier, but now it's doing this instead. I'll take a look at the other thread as well.

[scriptify]

@binury I am also on the latest extension version, but the error seems to persist. Any suggestions? (tried stable and pre-release)

[binury]

@binury I am also on the latest extension version, but the error seems to persist. Any suggestions? (tried stable and pre-release)

Your code version is outdated which is preventing the extension from updating as it is incompatible. Check my earlier messages for solutions