Re-opening issue #61 Unexpected scheme: chat-editing-text-model

[mikej100]

This is a re-open of issue #61 which was closed because not reproducible.

I get this error message every time I touch a feature file or step file, but not other python code files. This happens any time after I have opened a chat session, even if I have closed it. I have to close the chat session and reload vs code to prevent the message appearing every time I touch the step/feature file. Reloading without closing the chat window does not clear the error message. It is quite distracting (i.e. driving me crazy).

Can we give the issue another go? I love the extension capability and want to train up a colleague: now this "feature" which I have just ignored for a while doesn't feel so tolerable.

Here is the observed behaviour.

I open a new session on vs code. When I edit the step file or feature file everything is OK

Then I open the Chat window for copilot, in this case Claude Sonnet 4, and have a chat. All fine

Then I edit a single character in the step file, and I see a pop-up message in lower right hand corner :
Unexpected scheme: chat-editing-text-model Source: Behave VSC.

I clear the pop up.

I edit a single character in the feature file, and same pop up

I close the chat window, and edit the step file
Same message pop up.

vs code Palette: Developer. Reload Window
Edit step file
No error

Open Chat session
Edit step file
Error message unexpected scheme ...

vs code Command Palette: Developer. Reload Window
Error message unexpected scheme ....

Set up

behave-vsc

Installation
Identifier
jimasp.behave-vsc
Version
0.6.4
Last Updated
2024-11-12, 19:00:26
Size
299.84KB

Behave

behave v 1.3.1

Copilot Chat

Installation
Identifier
github.copilot-chat
Version
0.30.3
Last Updated
2025-09-01, 22:22:50
Source
VSIX

VS code

Version: 1.103.2 (user setup)
Commit: 6f17636121051a53c88d3e605c491d22af2ba755
Date: 2025-08-20T16:45:34.255Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Windows_NT x64 10.0.26100

I'm using vscodevim extension.

Platform

WSL2 Ubuntu 24.04.2 LTS

Do let me know if you think I can provide any more info.

[jimasp]

I'm still not able to recreate using the exact steps that you have outlined, so to repeat my original questions:

1. Can you set "behave-vsc.xRay": true, in your settings.json and see if that gives a stack trace with the error in the Behave VSC output window?
2. If you are on a dev team, is anyone else on your team getting this issue? If not, what is different about your copilot/vscode setup and theirs? Can you get them to recreate the error?

Also:
3. Why did the error go away and come back for you? The extension hasn't changed, so your project or vscode setup must have changed.