This issue is about allowing extensions to use language model that are contributed by other extensions. The API proposal is and its scope is to allow to use the chat feature of language models. Remaining finalisation todos [x] consolidate different LanguageModelChatXYZMessage-type into one type and a role-enum [x] move System message/role into its own proposal [x] have a select-function that's the only way of getting to a chat model [x] [ ] consider to have more sturcture on , e.g have a fake reply message with role like others (ollama, open ai, anthropic) I renamed to and I will continue to explore a stream of structured objects. That would be additive to and plugged in as its foundation. add something like add a StopReason-enum that's also used in LanguageModelChat
Docs:
With there will be no more language model access object. Instead all requests are made directly via
Hi Is there any plans to add a , so I can implement my own calls to other models other than the Copilot provided models? Thanks!
Yeah, that exists. It is the which is still very rough and currently not yet scheduled for finalisation. Tho, feel free to give it a spin and report what's missing/wrong. For instance, locally I have a dummy extension that uses ollama to drive this API
I assume you are referring to the API? So if I use , I can then use the id I give it with ?
No, I mean the proposal that I have mentioned
FYI that I made the following changes to the proposal there is no more and generally no more referring of language model by string-identifier. there is that takes a selector and returns matching chat models or nothing () These changes allow for a better implementation of the providing-end (-proposal) and most importantly make it more obvious that models can (and will) change. The following pattern had become popular'ish , ....)`. This is brittle because extensions break as soon as the model id isn't known anymore. Instead models need to be selected, making it hopefully more clear that a desired model doesn't exist. The new selector-mechanism allows for new flexibility as well. A couple of samples To restate, the -function can return which means no model was found. That's because the selector is to strict (using ) or because no models are known (missing extensions). The shape of language model selectors is this Note that property order represents how specific it is properties are matched based on equality, when present it must match we will likely add some comparison selector for input and/or output tokens
Isn't this still possible? We can call any LLM API in our handler and use the stream.markdown() to display the response, right?
'y.provider.provideLanguageModelResponse is not a function'
I'm noticing a difference in behavior of the API when running in Codespaces from the browser. When running against a Codespace with desktop Insiders, everything works as expected. When running against the same Codespace with browser Insiders, always returns , implying there are no chat models available.
Make sure that you are on latest pre-release of the copilot-chat extension That's certainly possible when copilot-chat isn't installed in the codespace.
It is installed, and regular Copilot Chat works normally, but our extension can't get a language model.
And it is latest prerelease?
Yep! Version: 1.90.0-insider Commit: Date: 2024-05-13T12:40:35.552Z Browser: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 Edg/124.0.0.0 ! ! Here's regular chat working: ! And our extension emitting to its output log, via this line of code: ! The same codespace but using desktop frontend instead of browser (working as expected): !
Really confusing... In my sample remote-setup (which isn't codespaces) this is working just fine and I see so smoking guns for why this wouldn't work in codespaces. For now, I have some logging that should help us get to the bottom of this
I see mention of moving the System prompt to a separate Proposal, can that be linked to? I am not finding it and we use it in our extension. Also is this section of the guide still accurate? It's not showing those commands as imports anymore and from my reading of the types it looks like it should be closer to:
This is place of all API proposals: Likely outdated
Where should I look for the additional logs?
Enable trace logging, show the window-log and check for messages starting with . There should be some for registering and some for selection <img width="963" alt="Screenshot 2024-05-15 at 08 15 30" src=""
I did find something after running into a similar issues. Can you confirm that a later/second invocation yields models and/or that the -event fires and that after that chat models are selected?
I found some log lines for selection but nothing for registration: We end up doing language model selection several times and each time it returns . I even tried doing the following and still there were no log lines about registration: all 3 extensions (Copilot Chat, Copilot, and our extension) browser window trace window logging extensions a query with regular Copilot (success) a query with our extension (failure) However, when using VSCode Desktop as the frontend, I do see log lines about language model registration:
Thanks for the update. That would really mean the language model API doesn't register. Can you check the chat log (Output GH Copilot Chat) for messages starting with
I don't see any messages like that from either browser or desktop frontend on the Codespace. However, on the browser session there was this message which did not appear on the desktop session--might be spurious but I'm not sure:
We have finalized the Language Model and Chat Participant API Thus, you can now publish your extensions to the VS Marketplace. This API is finalized in VS Code Insiders, and will be finalized in VS Code Stable in July. Thus we suggest that you use an engines: ^1.90.0 property in your , and VS Code Stable will gracefully handle your extensions and ignore your usage of Language Model and Chat API until the API gets finalized in Stable in July. Full docs We have decided to only finalise the message. And message might be finalised in one of the future iterations. Main reason for this is general API consideration - as we are still learning how the prompt API would fit with some of the non-GPT models. Also we believe that the prompt API requires more responsible AI testing from our team. If your extension would like to use the prompt API - please let us know if you hit issues with using the prompt as a replacement. We are excited to see what you build
I am still wondering if there will be a API so I can use other models inside of the chat API. Is this something coming in the future? For now, it can be shimmed by wrapping and handling other entries (perhaps I want to point to my local Ollama instance).
Still a proposal and not yet planned for finalisation


Fyi
Verification: install the pre-release version of speech extension: make sure is configured to (it should be by default) switch VS Code display language to another language that is supported by the speech extension such as german or portuguese start voice dictation in a text editor via "Start Dictation in Editor" verify you get prompted to install the related language pack for the display language you picked


<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --As introduced in version 1.87.0 () drag&drop tabs now features a border indicator. It would be nice to have an option to disable this indicator. (Indicator also makes tabs width change and subsequent unwanted jump effect but that's perhaps a bug issue.) !
If you are not interested in seeing the indicator you can change it's colour to be transparent the following way: Regarding the jumping of the tabs, this is definitely a bug, however, I am not able to reproduce it so it seems like it might be related to some none default setting. Could you share the none default tab related settings you are using?
Of course, I believe jumping of the tabs is related to:
I've tried this but I do not see any jumping ! Possibly related to zooming, what are you using?
I've debugged my a bit and it seems combination of these settings is the culprit:
I have tried the combination of these two settings and it doesn't lead to any jumping in my case.
That's odd. I've tried my installation only with these two settings active (1.87.1 on latest macOS) and I can reproduce the bug. !
I tested it on windows, will try it out on a mac next week.
This issue has been closed automatically because it needs more information and has not had recent activity. See also our guidelines. Happy Coding!
I tried the drag and drop on a macos and was also not able to reproduce your bug. Will leave the issue closes for the moment.
Are you sure you've tried the settings above? I was able to reproduce the bug on different MacBook as well as on Windows machine.
I'm able to reproduce now. Looking into it.
In this specific scenario (actions left and shrink tab) we set an ::after element of width 5 for the shadow effect, however, we also use the ::before and ::after elements for drag and drop. Will try to fix next week. Could be a bit tricky


Steps to Reproduce: to a folder/workspace with multiple repositories the Source Control viewlet, and in the Source Control Repositories view select one repository to the Explorer viewer back to the Source Control viewlet and in the Source Control Repositories view pick another repository <img width="538" alt="image" src=""the Refresh button renders the input with the correct height


Refs: [x] anyOS [x] anyOS Complexity: 4 We have at long last finalized the test coverage API. Implementing an extension that produces data for the API from scratch is challenging, and requires domain-specific knowledge, so you might find playing with the selfhost test provider to be the most effective way to test it The new types in the API include: - - - Please: Do some testing that the API and UI functions as you would expect Read through the API and verify that its documentation makes sense to you See that UI interactions work nicely as you would expect (you can use any extension that produces coverage to test this part)


Testing The should be a plain property and not a method
I was thinking about this guideline when I switched it to a method as it's creating a new object every call: Can switch it back, is it worth a discussion in the API sync?
I don't think it does create a new object but that's also not the point here. Your data is never sync with an async iterable but the point is the consumer should just have which is still an async iterable (and likely implemented as lazy getter)
I might be doing something wrong as I don't think I've used an async iterable before, but doesn't this need to return a separate iterable per call in order to support multiple extensions? Currently the is a multiplexer for multiple iterators:
Oh, I missed the invocation inside .
Maybe a better name for a method would be or .


an extension with the following code: on the refactoring in the bulk edit pane opens the following multi diff editor: <img width="1093" alt="Screenshot 2024-03-27 at 17 23 56" src=""above is not correct because it looks like the file is . In fact it is deleted.


VS Code Version: Version: 1.87.2 OS Version: macOS 13.6.4 Steps to Reproduce: in the terminal happens in in , see that IWindowOptions is empty What should happen (works in iTerm2 and macOS Terminal): in the terminal should see a report printed to the screen The window size reporting functions are useful when connecting through tunnels that do not support TTY resize event forwarding. While many SSH and Telnet clients do support this, some tunnels do not (for example, a raw socket tunnel to a vt220-supporting application) and some programs may assume that the client supports this escape sequence. The information required to determine the terminal size in character is already available and is currently used to set the TTY's size. This function is fully implemented in , but not vscode. A small proof-of-concept where I use the debugger to enable this option appears to work as expected.


Does this issue occur when all extensions are disabled?: I dont know VS Code Version: 1.88.0-insider OS Version: Windows 10 - 10.0. Build Steps to Reproduce: Start debugging python script. It creates a new "debugging terminal". This should work stop debugging debugging. If you look at the debugging terminal, you will see a input (generated by VS Code) then command for debugging the selected file. path of the is somehow truncated, hence cannot find the file. debugging is however starting: you will be prompted with the message: Timed out waiting for launcher to connect. As seen on the gif below: Path 1st time: (Correct path) Path 2nd time: (truncated path) !
I'm getting similar behaviour when using Git Bash as default profile. First time debugging the Python Debug Console opens and the application runs without issue: the subsequent times I sometimes get: ... which does in fact executes the code, but then I also sometimes get: I don't know what the call to comes from (possible the end of the directory name, but in in the last instance is not called. This inevitable gives this error. ! Which then starts a new Python Debug Console. Similar to what is above. I don't see this behaviour when using PowerShell or Cmd. IMO There's some weird truncation happening. Version: 1.88.0 (user setup) Commit: Date: 2024-04-03T13:26:18.741Z Electron: 28.2.8 ElectronBuildId: Chromium: 120.0.6099.291 18.18.2 V8: 12.0.267.19-electron.0 OS: Windows_NT x64 10.0.
Thank you for adding details! This is the exact same problem that I experience: I didn't try with another terminal (Powershell or Cmd). I will see if that can fix my problem temporary using .
As mentionned by This issue is not here using . However, this is still adding extra command that could be the explanation behind it: ! The first run it is only using: On the second run, it : before the command. There is still the before this line though (2nd blank line)
I am seeing the problem when I set my default terminal profile to any of the following and run my debug launch script twice. Each shell will fail on the second launch with the same mangled command line. bash command prompt powershell Work around: revert back to vs code 1.87.
I am having a similar problem launching Python from VS.Code with or without debugging (both cmd and wt as terminal.external.windowsExec). If the path to the Python executable contains space as in default I end up with and an error message in the launched terminal window: Yet this works fine if I pick a Python interpreter from venv or somewhere else such that there is no space in path e.g. Curiously - the internal terminal and internal console work with either path
it seems sending the ctrl+c in a separate is not sufficient -- any suggestions?
If you want to execute something again we have a helper on the render process side , this conditionally sends a ^C and may wait for a shell integration prompt. That might work?
It looks like that does the same thing with a 100ms delay. I'll adopt the delay as well, see if that fixes it
please could you confirm when this will be released? It doesn't seem to have gone out in the latest April release. I've tried the insiders version and can't debug anything so it's even worse.
This is available on Insiders. Please open another issue with the details for not being able to debug anything; that's probably not related to this fix...
Can any of you verify that this is fixed in the newest version of VS Code Insiders? Thanks!
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
The external terminal launch is working with space in pythonInterpreter path () using both and as Windows Terminal in current: 1.89.1 and insiders 1.90.0 /verified
Running on version 1.90.0 I can not longer observe the truncation. The execution command looks intact even after multiple runs. ! There's an extraneous whenever you start a run but I guess that's intentional.
I am experiencing this issue using Python Debugger: Current File with Arguments. I am using ver VSCode ver 1.9


macOS, VS Code Insiders into explorer focus via keyboard hover does not show. There is no command to trigger the custom hover to show Like the activity bar, we have to make sure that the custom hover can be accessed in the tree/list only with the keyboard.
Would you suggest adding a keybinding to toggle the visibility of the custom hover of the html element which has focus?
Yeah, ideally it is . The same shortcut that we use in the editor for showing the hover. So it is consistent and easy for user to understand that there is one shortcut which does the right thing everywhere.
Isn't this a duplicate of ? Btw we seem to be having this support for extension provided trees at least:
I think it's good to have this one separate to .
Solving this for all trees/lists is pretty hard as the tree/list does not know anything about the underlying elements being rendered. For extension trees it is much easier as they all consist of a label which the creates and controls.
One option could be to utilize the to get the tooltip. Currently it already provides
After further discussions we came to the conclusion that we would use the DOM tree to figure out if there is any custom hovers available and trigger the hover by dispatching a mouse event on the HTMLElement. This might seem rather hacky but it ensures the consumers of the tree only have to support hover once and lets the tree handle keyboard triggers. Handling focus is still tricky and a open problem. Until this focus problem is properly fixed the treeview will keep it's own implementation which directly uses the hover service and moves the focus into the hover. The treeview implementation of this has it's own flaws but will b kept for the meantime to not cause regressions.


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.88.1 (Latest) + GitHub Codespaces OS Version: All? (Tested on Linux + MacOS) Steps to Reproduce: a folder or workspace (create if necessary): all the content from the above file and save it the command palette 'Tasks: Run Task' '+ Configure a Task' 'Open file' any provided task template notification error: "Unable to write to Folder Settings because no resource is provided." Expected behaviour: Empty is populated with the contents of the selected task template <img width="898" alt="Screenshot 2024-04-18 at 16 50 01" src=""


Under some circumstances, the Code Action button won't go away and will still run its assign command (incorrectly) Steps to Reproduce: an error with 'Quick Fix' available ! the cursor on the same line and press to bring up the quickfix ! to cancel ! the code action button ! the button again ! again ! ! at step 4. the button should disappear, but it does not I found this bug while adding Code Actions to my personal extension VS Code Version: 1.88.1 OS Version: Windows 11


Testing "Note: Using this setting will disable Window: Auto Detect Color Scheme" should finish with a period.


Testing open show outline and have sticky scroll enabled scroll the cell with "# Header " into view delete the cell :bug: the sticky scroll breaks, the error below is printed <img width="1482" alt="Screenshot 2024-04-23 at 08 51 18" src=""
I'm unable to repro this. Please can you share a screen recording of the steps. Perhaps recoding from opehning the notebook to selecting and deleting. Thanks.
Looking at the stacktrace tells me this is coming here which means the model had been already
following the steps above (empty profile) always reproduce the error (console) for me. The screen cheese shows in sticky scroll and/or other paces of the outline tree


<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --<!-- Describe the feature you'd like. --I'm creator of [SWC][] and I want vscode to use the officla JSON schema introduced by for by default. I'm going to create a PR. [SWC]


If I open a Dart project, right-click on a folder in the explorer and then "Run Tests", I see: ! However if I open the test explorer tree first and then try again, everything works. It appears that "Run Tests" from explorer does not trigger the to allow initial test discovery. ( I presume this is a bug and not intended?)
even after I've shown the explorer tree and triggered discovery, it seems like "Run Tests" now works on the "tests" folder, but not on an individual test file (even though I've confirmed the URI for that file is being set when creating the test tree item). Is there something else I need to do besides having the URI on the test file node?
Does this reproduce on Insiders for you? It should be fixed with
looks like that fix handles the second issue above (running the file now works), however the original issue above is still an issue - if I don't trigger discovery of the tests before using it, it reports no tests found.
Fix works for me, thanks! :) /verified


The command was augmented with the argument here in Because the does not include the , any attempts to mint a key will result in a 404 if the server-base-path is set. I think this is the reason why I am experiencing an issue that any sign-in attempt in the browser (e.g., Github Copilot, Settings Sync) do not persist between page refreshes. <!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.89.1 OS Version: x64 Steps to Reproduce: the browser, observe 404s to
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
assigned to you since you approved the original PR


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.89.0 OS Version: Linux x64 6.6.26-1-MANJARO Steps to Reproduce: VS Code. Developer Tools and watch Network requests. VS Code, open Settings. that Settings will not display any settings until the requests to are completed. reading the results of the queries, observe that this request is related to the absolutely despicable advertisement for GitHub Copilot_, to detect if it's already installed (or something) in order to show the ad in the Settings UI and that you are now even more incensed that something which should work immediately was taking 7 seconds or longer due to the fact that we are now living through a dystopia. Then quickly get over it and start considering a move to a different editor or a fork. Please choose one of the following suggestions: remove the GitHub Copilot advertisement from the Settings UI. waiting for network requests in order to show the Settings UI. this issue and ignore this unquestionably sane plea to help battle the enfecalization of this beloved product.
Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.89.1. Please try upgrading to the latest version and checking whether this issue remains. Happy Coding!
The AUR hasn't been updated with 1.89.1 yet but looking at the resolved issues I don't see any related to this.
I have a 1-second timeout per network request. In other words, the delays should now have an upper limit on their duration.


You should not be assuming that the editor for which the action is being run for is the active editor. Make sure to correctly extract the context from the arguments passed to the script. The run method should be defined the following way: You can get the correct context with and resolve it with Make sure to adopt this for the following MultiDiffActions: - You can test that it works correctly with and 2 editor groups


make an inline chat request that changes code select the re-generate action :bug: the previous changes aren't undone


My extension provides document links by calling on with a implementation. It provides tooltip, because it always sets the field to the return values of . I confirmed it works (tooltip is shown) by actually running the extension. I wrote an integration test for it. It activates the extension and calls where is the URI of an opened document that our extension supports. It returns the expected objects except those lack the field. Am I missing anything, or is it a bug of the command that it doesn't set the field? Version: 1.89.1 Commit: User Agent: Mozilla/5.0 (X11; CrOS x86_64 .0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36 Embedder: server-distro <!-- generated by web issue reporter --


I removed this to move over to using the agent, which required setting . Chatted with and I should add another agent to support the agent in both places, only making it the default for the terminal location. fyi
Verified that is available in panel chat.


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.90.1 OS Version: Rocky 8 Steps to Reproduce: with the option with a string containing the desired connection token. server starts up with the specified connection token. with the option with a path to a file with the desired connection token. server starts up with a randomly-generated UUID as the connection token. The exposes a which would reasonably be expected to work, especially since does work as expected and overrides generation of a random token. In particular, in calls to handle either generating a fresh token or using a provided one. This only handles and as far as I can tell there is no code in the option handling that would replace this value with the token read from the file . The option only appears to be used in different contexts like running the downloaded servers, and the value in the ServeWebArgs version appears to only ever be overwritten by the previously-mentioned token minting code. When executing the function, it would be much preferable to provide a specified connection token in a file, for reasons similar to those in to prevent the connection token from being accessible by other users. I do not believe this is a security vulnerability, since you have to explicitly opt in to providing a connection token in a potentially unsafe manner as-is, but being able to provide one in a file would be a substantial security improvement when using specified connection tokens. I believe that this code should read in the file at the path provided by the argument and use the contents as the token when provided. If this isn't intended to be used, I would think it should be removed from the options provided for the CLI command instead of being non-functional.
Hi Are you able to verify if this fix works? You can do so by getting the latest pre-release version of the remote-ssh extension and trying these same steps there. We want to make sure we get this bug verified, and the fix is correct, before we release this to stable. Thanks!
I checked the code-insiders build I downloaded today (1.92.0). It does not appear to have a fix for this issue and the current insiders build has the same behavior as before. I also took a look at the that closed this issue and although it is titled as relevant to this issue, it contains a that appears like it would perhaps be relevant to the remote-ssh extension but does not have any relation to this issue with connection tokens and the CLI that I can tell. I think perhaps that PR/commit got mixed up from different issue than this one.
Reopening with verification found based on authors report
huh, not sure what happened to the branch in that PR. I'll resubmit the change.


See
I think it's related to this line not clearing the quick pick: It's meant to hit backspace:


<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --Add support for --proxy-bypass-list in the file so that we can provide a default proxy bypass list to VS Code users. Setting NO_PROXY doesn't work as a solution because it would either have to be set as a user / system environment variable thus impacting all applications, or we would have to rely on our VS Code users to explicitly pass --proxy-bypass-list as an argument to code on the command line each time they launch. Having the option to set this in would provide us with a way to package this in our default enterprise installation of VS Code so users would get this setting by default, but just for VS Code.
Could we just in . I was not aware that only a subset of our command line arguments can be configured there actually. fyi
Yes we can expose it Yeah the list of chromium commandline flags in quit large and always changes with version updates it would be a nightmare if we are to support all of them in . At this time we only support those on a case by case basis.
Thanks, makes sense! Should I assign this one to you? If you are busy, I am happy to provide a PR in July if you give me a code pointer?
Here is an example of recent flag addition , feel free to send a PR. I can review it. Thanks!
Thanks for that great example. Here's the PR I verified that adding "proxy-bypass-list" does not produce errors in I did not verify if this list actually gets passed to Chrome. We can ask if we get this out to an insiders build.
FYI: There is a PR in progress for adding a setting for the feature:
Thanks. But unlike that PR, I think this flag just needs to be passed to Chromium and it should get handled. i.e. I did not add any code in VS Code that actually handles the flag.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
This flag doesn't seem to work for me unfortunately. Using mitmproxy I still see the bypassed domains: !
Can confirm, preparing a fix now.
thanks for the quick fix
verification steps: Setup mitmproxy Start the application with proxy server Check the logs to see requests from the application are intercepted, you should see some domains like or Open and set Restart the application with same proxy server Confirm that requests to these hosts are not seen in the intercepted logs anymore


Testing enable link underline open settings editor and scroll to "Text Editor" section in-text links are underlines but command links aren't unsure if this should be aligned or not? <img width="759" alt="Screenshot 2024-06-25 at 09 50 40" src=""


Testing Once again, I'm not sure what the norms are here, but would it be useful to have the actions in the status bar show in the accessibly view? <img width="607" alt="image" src=""
Hi yes that would make sense. Good point!


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.91.0 (Universal) OS Version: Darwin arm64 23.5.0 Steps to Reproduce: new profile test to new profile in Devcontainer sample container is loaded without extensions. Opening in DevContainer with the default profile works correctly. Works correctly with the previous version of vscode 1.90.2
Same For Me
+1 extensions from are not enabled in the container when using a custom profile. Although the container logs does report that the extension was successfully installed, and I can see it is installed in the container, in . It's just not enabled when using a custom vscode profile.


<!-- Do Not Delete This! featurerequesttemplate --<!-- Please read our Rules of Conduct: --<!-- Please search existing issues to avoid creating duplicates. --VSCode Version 1.91.0 introduces a new "New Window with Profile menu item". I see it's not currently available in the command palette, like the "New Window" command. <img width="603" alt="image" src=""It would be nice to have this available in the command palette.


Type: <bBug</bscreen ready accessiblity mode to be on. Look for screen reader optimized at the bottom bar of VS Code. settings, search for "accessibility volume". Set it to 0. an action in a VS Code editor that creates a sound (which you haven't configured to be "off"/"never"), eg trigger an inline copilot suggestion. a sound (make sure your computer audio is on) even though you set volume to 0. VS Code version: Code 1.91.1 (, 2024-07-09T22:07:46.768Z) OS version: Darwin arm64 23.5.0 Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (71)</summaryExtensionVersion ------ better-comments3.0.2 quitcontrol-vscode4.0.0 solarized-light-custom4.0.1 solidjs3.0.7 vscode-tailwindcss0.12.5 turbo-console-log2.10.4 ruff2024.30.0 regex0.4.0 doxdocgen1.4.0 vscode-eslint3.0.10 xml2.5.1 es7-react-js-snippets3.1.1 gitlens15.2.0 prettier-vscode10.4.0 figma-vscode-extension0.3.5 auto-rename-tag0.1.10 shell-format7.2.5 kotlin0.2.34 macros1.2.1 copilot1.213.0 copilot-chat0.17. vscode-pull-request-github0.92.0 go0.41.4 gti-vscode0.6.1 vscode-graphql-syntax1.3.6 better-cpp-syntax1.27.1 vscode-go-template0.2.1 cmake-language-support-vscode0.0.9 Kotlin1.7.1 git-graph1.30.0 vscode-docker1.29.1 vscode-dotnet-runtime2.0.9 black-formatter2024.3. debugpy2024.9. isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.375.1 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 vscode-remote-extensionpack0.25.0 cmake-tools1.18.43 cpptools1.20.5 cpptools-extension-pack1.3.0 remote-explorer0.4.3 remote-server1.5.2 test-adapter-converter0.1.9 vsliveshare1.0.5932 vsix-viewer1.0.5 vscode-hack2.20.0 quicktype23.0.170 webgl-glsl-editor1.3.8 code-spell-checker3.0.1 tauri-vscode0.2.6 blueprint3.0.0 best-dark-themes-pack1.0.2 best-light-themes-pack1.0.2 cmake0.0.17 vscode-lldb1.10.0 vscode-swiftformat1.6.10 change-case1.0.0 luahelper0.2.28 pretty-ts-errors0.5.4 markdown-all-in-one3.6.2 material-theme3.17.2 (28 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
thanks for taking a look ! i believe this will resolve as well
Specifically the setting doesn't get saved to Even if you write it manually in , VSCode removes it on next start. Both and have this problem.


Postgres supports dollar quoted strings as an alternative to regular strings. This is useful when you need to include the character itself but don't want to escape it. The official documentation can be found . Unfortunately, the default SQL highlighter in VSCode does not seem to support this syntax. Steps to Reproduce to a new file the "SQL" language mode the following content: Expected should not start a new string. The content between and should be identified as a string and highlighted as such. Actual ! Additional context Version: 1.91.1 Commit: User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/126.0.0.0 Safari/537.36 Embedder: Also tested in the desktop version with identical results.
Note that there may be good reason the editor tries to highlight code in the dollar quoted block. Dollar quoted strings are often used to declare function bodies in postgres and there are therefore (perhaps most commonly) instances where the content inside the dollar signs would be better off using "regular" sql highlighting. However, the reported issue is very annoying as it breaks highlighting for the rest of the file. If implementing a full parser with support for these types of "sometimes strings" requires too much effort, a passable alternative would be to at least stop the highlighter from leaking outside the dollar quoted scope.
Th grammar we have is for MS SQL and doesn't support features outside that. Duplicate of
In that case, I think you should rename the user-visible language mode to "MSSQL" rather than "SQL". I find just calling it "SQL" to be a deceptive marketing practice if you are not going to support other SQL dialects in it.
It is fair to say that MS SQL won't work for all SQL flavors. I will discuss renaming it with the team.
Based on some quick digging, MS SQL uses Transact-SQL (T-SQL). The most appropriate thing to rename the built in SQL grammar to would be T-SQL. However, I'm not sure that T-SQL will mean something to most users.
I'm going to wait and try renaming at the very beginning of our next milestone so that I can see if any insiders users are thrown off first.
I think T-SQL is not well known enough and will be confusing. I'll try renaming to MS SQL.
<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history. If this was closed in a separate repo you can add the label directly, or comment .
<!-- UNABLETOLOCATECOMMITMESSAGE --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased
To verify: Open a file in VS Code Open the language picker from the status bar Verify that you don't see SQL, but instead see MS SQL


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes/No, this is an extension-related issue that arises across extensions with walkthroughs <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.91.1 OS Version: Windows 11 Extension walkthroughs are not launching upon install. Expected behavior: walkthrough launches automatically upon install. Tested on C# Dev Kit extension and Python extension. Seemed to work in 1.90.0 but does not work in 1.91.1. Steps to Reproduce [Windows Sandbox]: a Windows Sandbox Edge and download VS Code (stable) from the VS Code website the C# Dev Kit extension. Note: Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps. command palette. command 'Welcome: Open Walkthrough' 'Get Started with C# Dev Kit' ! steps 3-7 with the Python extension. Same behavior. Steps to Reproduce [VS Code stable and VS Code insider]: VS Code C# Dev Kit (if you have it installed) VS Code C# Dev Kit extension. Note: Upon install the walkthrough is supposed to launch automatically. This is not happening, but I can manually open the walkthrough using these steps. command palette. command 'Welcome: Open Walkthrough' 'Get Started with C# Dev Kit' steps 2-7 with the Python extension. Same behavior.
closedWith
using the steps above, I am not seeing the walkthrough open when I reinstall the extension
Was just talking with about this- if you've had it installed in the past, it won't work, but for me it works in a window with a clean user-data-dir


Connect to my mac with Remote-SSH See these errors from the server in the log (Remote-SSH output channel) doesn't seem to cause a problem but it's noisy and looks like an issue
could you point me at which line this is? Our stack beautifier doesn't work on server code afaik
I don't know which line it is, I only have that stack
It's this line: Somehow node-pty can return undefined for Doesn't seem like it should be possible considering or are the fallbacks for :
I'm seeing this on my own machine so could do some debugging if you want to add logs or something


Type: <bBug</bWelcome - Learn the Fyndamentals Safely browse and edit code Workspace Trust Link 404 - page not found VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: Windows_NT x64 10.0. Modes: Restricted <!-- generated by issue reporter --
could you please provide a screenshot of where this broken link is? Thanks!
Got it - issue is in the walkthrough. Fix incoming. Thanks for signaling this
Is this a candidate? The change has been merged to the main branch but not the release branch, and so the fix is not in the latest Insiders.
IMO, it can go with the next one.
<!-- UNABLETOLOCATECOMMITMESSAGE repo --Issue marked as unreleased but unable to locate closing commit in repo history. If this was closed in a separate repo you can add the label directly, or comment .
<!-- UNABLETOLOCATECOMMITMESSAGE --Issue marked as unreleased but unable to locate closing commit in issue timeline. You can manually reference a commit by commenting , or directly add the label if you know this has already been releaased


Type: <bBug</bIssue Reporter, e.g. from off Command Palette. the first dropdown to VS Code version: Code - Insiders 1.92.0-insider (, 2024-07-24T07:50:18.385Z) OS version: Windows_NT x64 10.0. Modes: <!-- generated by issue reporter --
good catch, thanks! looks like an issue with the refactor


Type: <bBug</bIf you rename a folder to "Cut Sheet" for example, that folder and anything below it becomes a "greyed" out folder. If you have a file that is named "Cut " for example, this is also greyed out. Renaming any of these makes them a normal folder/item icon. I have confirmed that this is not a .gitignore issue, nor does it appear to be a theme issue. Please see the image below. ! VS Code version: Code 1.91.1 (, 2024-07-09T22:06:49.809Z) OS version: WindowsNT x64 10.0. Modes: <details<summarySystem Info</summary </details<details<summaryExtensions (81)</summaryExtensionVersion ------ amazon-q-vscode1.17.0 vscode-intelephense-client1.10.4 phpserver3.0.2 vscode-yarn-script0.0.1 path-intellisense2.9.0 codeium1.10.1 doxdocgen1.4.0 vscode-markdownlint0.55.0 composer-php-vscode1.49. intelli-php-vscode0.12. phptools-vscode1.49. profiler-php-vscode1.49. xml2.5.1 gitlens15.2.1 vscode-html-css2.0.10 EditorConfig0.16.4 prettier-vscode10.4.0 vscode-yarn2.1.0 copilot1.218.0 copilot-chat0.17.1 remotehub0.62.0 vscode-pull-request-github0.92.0 gc-excelviewer4.2.59 todo-tree0.0.226 vscode-test-explorer2.21.1 better-cpp-syntax1.27.1 vscode-nuget-package-manager1.1.6 cmake-language-support-vscode0.0.9 vscode-autohotkey-plus-plus5.0.5 rainbow-csv3.12.0 compare-folders0.24.3 vscode-docker1.29.1 csdevkit1.8.14 csharp2.39.29 vscode-dotnet-runtime2.1.1 vscodeintellicode-csharp2.1.11 debugpy2024.8.0 gather2022.3.2 isort2023.10.1 python2024.10.0 vscode-pylance2024.7.1 jupyter2024.6.0 jupyter-keymap1.1.2 jupyter-renderers1.0.18 vscode-jupyter-cell-tags0.1.9 vscode-jupyter-slideshow0.1.6 remote-containers0.379.0 remote-ssh0.112.0 remote-ssh-edit0.86.0 remote-wsl0.88.2 cmake-tools1.18.43 cpptools1.21.3 cpptools-extension-pack1.3.0 live-server0.4.14 powershell2024.2.2 remote-explorer0.4.3 remote-repositories0.40.0 remote-server1.5.2 test-adapter-converter0.1.9 vscode-speech0.10.0 vsliveshare1.0.5936 indent-rainbow8.3.1 word-count0.1.0 material-icon-theme5.8.0 LiveServer5.7.9 vscode-vba0.11.0 logos-vscode1.0.1 pdf1.2.2 cmake0.0.17 highlight-matching-tag0.11.0 intellicode-api-usage-examples0.2.8 vscodeintellicode1.3.1 vscode-gradle3.15.0 vscode-java-debug0.58.0 vscode-java-dependency0.24.0 vscode-java-pack0.27.0 vscode-maven0.44.0 vscode-todo-highlight1.0.5 php-debug1.35.0 php-pack1.0.3 php-intellisense1.3.3 (1 theme extensions excluded) </details<details<summaryA/B Experiments</summary</details<!-- generated by issue reporter --
/needsMoreInfo Is it reproducible with all extensions disabled? You can try this with <kbdF1</kbdand Do you have mentioned in setting for user or workspace or do you have it in ignore file?
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our . Please take the time to review these and update the issue. Happy Coding!
It still occurs when I reload window with extensions disabled. And I do not have mentioned in my files.exclude in my user or workspace settings JSON. My workspace does not have a a files.exclude. My user settings has the following: "files.exclude": { "/.classpath": true, "/.project": true, "/.settings": true, "/.factorypath": true }, See attached image showing extensions disabled and both files. ! And here's a picture of my .gitignore file: !
Same problem here !
PR fixing it
Fix reverted by


a workspace: and drop into Expected Inserts Actual Inserts
Closing as fixed in main and release branch


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --Does this issue occur when all extensions are disabled?: Yes <!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: 1.92.0, commit OS Version: Windows 10 Enterprise, 22H2 build .4651 Error message: Steps to Reproduce: a new VS code window ! a new file and drag out to make another window ! "Create New Terminal in Editor Area" on that new window ! error will show up ! "Try Again" will reload the terminal, but it doesn't accept inputs, cannot type anything there ! Creating terminal in main window and drag it to side windows does work, but I have to do that with every window reload. Yesterday I could still use terminals in side windows like normal, this only occured after updating to 1.92 July update Thanks for reading :)
! Facing same issue
coming from xterm here I think !
I have the same problem on Fedora 40 Sway. After I click , it will create a non-interoperable terminal.
I'm also having this issue, I thought it might be a problem with WSL but it started for me after updating to VSCode 1.92.0 !
QUICK FIX!!! Just create a new In-window terminal and drag it to the new terminal window.
Will this be hotfixed or should we downgrade?
sorry this won't get a patch release as there's a few workarounds. To downgrade in the meantime you can grab 1.91.1 here , you'll also want to set
Hi. Didn't do the trick for me. Other hack: Ctrl+J (new term in main window) Ctrl + Shift + P Terminal: Move Into New Window Drag & Drop into wanted window. Cumbersom many many times a day.


Note that quick pick instances and their events are disposables. Noticed a few cases of missing:


Type: <bBug</bThis issue was supposed to be fixed in , but we have recently received complaints from some users regarding this. I counted the first 50 issues with Vue extension installed in , and 25 users are using 1.8.27 ~ 2.0.10 (2.0.10 was released 4 months ago ), only 19 users are using the latest version (2.0.22 ~ 2.0.28). Numbers: 2.0.10: 13 (Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue , Issue ) 2.0.8: 6 (Issue , Issue , Issue , Issue , Issue , Issue ) 2.0.7: 2 (Issue , Issue ) 2.0.6: 2 (Issue , Issue ) 1.8.27: 2 (Issue , Issue ) 2.0.22~2.0.28: 19 Since some versions in 2.0.0~2.0.10 may have serious problems, this is probably the reason why the Vue extension has continued to receive negative reviews on the Marketplace and VSCode has continued to receive bug reports about the Vue extension for several months. I found a Windows computer with 2.0.7 installed and was able to reproduce the issue of not being able to update the version. The following is the content of . (Formatted for easier reading) And I can reproduce the problem of not being able to update by overwriting the above metadata to the file of another macbook. is installed, uninstall it and then close VSCode and reopen it. 2.0.7 from https://open- and install it to VSCode, VSCode can normally prompt that Vue extension needs to be updated. and modify the metadata of the last extension to: VSCode will find that the Vue extension cannot detect newer versions. VS Code version: Code 1.92.1 (, 2024-08-07T20:16:39.455Z) OS version: Darwin arm64 23.1.0 Modes: <!-- generated by issue reporter --
cc
I just checked our telemetry for the most popular combinations of VS Code version and Vue extension version and here's what I see. This proves that vue version and are indeed not getting properly updated. The root cause of this is the fact the vue extension, unpublished from the Marketplace and published again the same name (thus exposing a bug in the Marketplace) as explained here We still want to help transition your users, and I will go ahead and move this issue to the VS Code repo and Sandeep will investigate next week once he is back from vacation. Thank you !
Update is not detected automatically. It is detected only when user is searching for the extension.
Sorry about this inconvenience caused. Fixed it - We will now detect the update automatically.
<!-- AUTHORVERIFICATIONREQUEST --This bug has been fixed in the latest release of ! you can help us out by commenting if things are now working as expected. If things still don't seem right, please ensure you're on version of Insiders (today's or later - you can use in the command palette to check), and leave a comment letting us know what isn't working as expected. Happy Coding!
I just tested it and confirmed it's fixed in the latest insiders version, thanks a lot!
Adding label based on above comment


For: Passing in an empty markdown file fixes this issue currently. [x] Add the ability to go back to the last focused view instead of the welcome page.
Removing the button on walkthroughs if opened from the cmd. This should prevent the walkthrough from going to the welcome page. The button is now only shown when a walkthrough is invoked from the page or another walkthrough.


Run the following cell Stage the notebook Make changes to the HTML Run again and view the diff Problems Clicking the will display a quick pick, however selecting anything is a noop !
/cc


Testing I had this code: But I still got results from a workspace folder: ! Full Extension:
I happen to want to report the same problem When there is only one item in the exclude string, the exclusion is correctly applied. When the exclude string contains more than one item, the exclusion is not applied. !
I think that your issue is a duplicate of
Seems that this only happens when is not defined. Strange.


We'd like to have a safety net if we ever break Insiders users once more to the point of them not being able to update.
Implementation is done. Requires


move editor into its own window trigger find the input box is cropped, the border isn't fully visible !
I can reproduce and I am puzzled as to why this is. Opening for help wanted for a CSS wizard to step in if possible. Steps: open a text editor in the main window open the find widget and focus it, notice how the blue outline color goes all the way around the input box right click into the editor tab and "Copy into New Window" do the same and notice that the outline is cropped I already see that the wrapper around the is in the main window and in the auxiliary window ! ! CSS is defined from here: and
I can fix this, please assign me this issue if it's still open
we cannot assign issues to non-members of the team, but feel free to open a PR. Thanks!
sure, thanks for letting me know.


Enable the setting which enabled the native edit context adoption (make sure to reload the editor) Toggle word wrap on Resize the editor, so one of the lines is wrapped Type on that line Part of the line is deleted/incorrectly edited
Looks like this could be an issue with the coordinate system chosen too.


If the diff element is disposed while the diff element is being resolved/built, then we might end up leaking the text models. Here its possible that the element was disposed just after the first line, i.e. once the promise resolves the element has been disposed. Thus leaking the text models. We have similar code in other parts and handle this correctly.


<!-- Do Not Delete This! bugreporttemplate --<!-- Please read our Rules of Conduct: --<!-- Read our guide about submitting issues: --<!-- Search existing issues to avoid creating duplicates. --<!-- Test using the latest Insiders build to see if your issue has already been fixed: --<!-- Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --<!-- Launch with to check. --<!-- If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --<!-- Issues caused by an extension need to be reported directly to the extension publisher. The 'Help Report Issue' dialog can assist with this. --- VS Code Version: Version: 1.93.0-insider (user setup) Commit: Date: 2024-09-04T13:13:15.344Z Electron: 30.4.0 ElectronBuildId: Chromium: 124.0.6367.243 20.15.1 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0. OS Version: Windows 11 Insiders Steps to Reproduce: in the first paragraph doesn't appear to be a link, which I was surprised about: ! I hover over it, I see it's supposed to be a link, but clicking on it does nothing: ! The other docs links at the bottom of the playground appear correctly as links and do open when I click on them: !
This seems related to the bookmark issue we had in the release notes. The other bookmark links in the interactive playground don't work either.
Fixed the toc links. Need another fix for the documentation link too (which use command uris)
The Editor Playground is not showing at all anymore in the latest insiders. When selecting the Editor Playground menu item, a black editor comes up.
hm working from oss builds. Insiders, it seems like the error is:
Actually unrelated. Seems like a duplicate of and fixed by


When using vscode through a , if I switch profiles and then open an existing project (ctrl+r, left click), the url then updates with some url parameters (). The window loaded with that payload doesn't work correctly. For example, code search only works on the already opened files, and not the entire folder. A workaround is to remove the payload from the url. Version: 1.93.1 Commit: User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X ) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36 Embedder: <!-- generated by web issue reporter --


terminal I -notice double microphone icons I do not have the voice extension installed. ! fyi
Caused by:
looks the most relevant
Why does the terminal have its own execute menu?
Is it possible to clean up the parallel execute menu and submit actions? I'm unclear whether I can just move the voice actions to or you need a new parallel menu for terminal customizations.
I did the first one, seems to work, but please clean up the terminal-specific stuff if possible
Can you be more specific?
so I do have a lot of special code for terminal in using stuff like , which maybe now is obsolete? Did something change to consolidate inline chat in terminal?
This isn't actionable without more info. Terminal chat still has a separate widget implementation, it extends inline chat and shares a lot of code, but must be separate as it's not a monaco content widget for example.
Yeah I did a quick attempt to remove my terminal specific code but restored it, as it still seemed to be needed.
That was directed at the terminal widget stuff- it has its own execute menu and execute action, and I only looked briefly but it seemed like it was doing the same thing as the base chat submit action. TerminalChatWidget uses InlineChatWidget which uses the normal ChatWidget, I'd expect that the execute toolbar can be the same regardless of whether it shows up in an editor or a terminal.
did all that stuff so she might be able to comment better than me.
When I last investigated this, , the chat widget's submit action was dependent on an editor, which we don't have in terminal chat, and was defined in a place where the was not accessible. I can look into doing this now though as it seems the code has changed since then.


<!-- Please search existing issues to avoid creating duplicates. --- Version: 1.94.0-insider (user setup) Commit: OS: Windows_NT x64 10.0. Jupyter Extension version (available under the Extensions sidebar): v2024.9. (pre-release) Python Extension version (available under the Extensions sidebar): v2024.15. (pre-release) First part of the video: cursor in a markdown cell, somewhere in the visible area of the screen out of the cell to double click somewhere in the visible area of the screen to highlight text (either same line or not) Cell scrolls to the top so I can't see what I'm trying to highlight (the text is highlighted as intended though) Second part of the video: cursor in markdown cell, somewhere in the NOT visible area of the screen out of the cell to double click somewhere in the visible area of the screen to highlight text Cell scrolls to the previously placed cursor area (which is great if I'm single-clicking into the cell, but in this case, it feels glitchy to me)
I have the same issue!