Change:
const pendingCommentText = (this._pendingNewCommentCache[uniqueOwner] && this._pendingNewCommentCache[uniqueOwner][thread.threadId]) ?? continueOnCommentText; const pendingEdits = this._pendingEditsCache[uniqueOwner] && this._pendingEditsCache[uniqueOwner][thread.threadId]; <del> const shouldReveal = thread.canReply && thread.isTemplate && (!thread.comments || (thread.comments.length === 0)) && (!thread.editorId || (thread.editorId === editorId)); </del> <ins> const isThreadTemplateOrEmpty = (thread.isTemplate || (!thread.comments || (thread.comments.length === 0))); const shouldReveal = thread.canReply && isThreadTemplateOrEmpty && (!thread.editorId || (thread.editorId === editorId)); </ins> await this.displayCommentThread(uniqueOwner, thread, shouldReveal, pendingCommentText, pendingEdits); this._commentInfos.filter(info => info.uniqueOwner === uniqueOwner)[0].threads.push(thread); this.tryUpdateReservedSpace();

Discussion:
<!-- 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. --Version: 1.90.0 (Universal) Commit: Date: 2024-06-04T19:34:44.157Z Electron: 29.4.0 ElectronBuildId: Chromium: 122.0.6261.156 20.9.0 V8: 12.2.281.27-electron.0 OS: Darwin arm64 22.1.0 Description Our VSCode extension relies on the comment thread API ( via a ) to create an input box that can receive user input. On VS Code versions 1.89.1 and before, the comment threads created via this API would be auto-focused and in an expanded state: ! However, starting on version 1.90.0, the comment thread is created in a closed state: ! This is undesirable, since it takes an additional click to start entering text into the comment thread. Is this something that we can configure on our side? If it's a helpful reference, there seem to be a couple of changes on the VS Code side relating to the focus / reveal of comment threads:
Yes, I have this too, very annoying.
I can't reproduce this. Can you share a code snippet?
Hi I'm a Codeium user and I can reproduce it by adding the and pressing Cmd + I to open a refactor panel. Not sure about snippet because I'm not a Codeium developer. 
Thanks for the reply!

I believe the following is a minimal example, let me know if it works for you: a comment controller a comment thread with any doc and range Expected behavior: opens the comment thread where the input is auto-focused Actual behavior: open the comment thread but the input is closed
Hmm. I'm doing basically the same thing, but I can't repro. I've pushed my test command to the comment sample. You can see the change here: , and you can clone that repo and check out the alexr00/createEditableThread branch to try it out.
I tested out the change and it seems like it opens the comment box with an existing comment box in edit mode. While this does open the input to be focused, it also adds a "Reply" at the bottom of the comment box which is undesirable. <img width="2058" alt="image" src=""If I remove the comment and start with an empty thread, we're back at the original issue which is that the comment box is not open <img width="2075" alt="image" src="" Is there a way for us to: Open the comment box with the input focused No existing comments / reply at the bottom Thank you!
Thanks for finding the difference between our samples!
thqnk you for the swift fix!
Thank you!! Is there a rough estimate on when this might make it to the next VS Code release?
We aren't planning on having another recovery release, so you can see our next approximate release time in the .
<!-- 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!
Looks good now in insiders! !
My change for this is causing a bad experience for several extensions: It's a common pattern for extensions to call and pass in for the comments. Because of my change, this now results in the comment reply editor always being expanded for threads created like this. reverts this change, and also makes a new change that will ensure that the input editor is focused when you create a comment thread like this: From The above snippet should do the trick.
thank you for the heads up!

while testing this out in VSCode Insiders, I noticed that after opening the comment thread, the comment appeared in the comment tab below even while editing. Ideally, it would only appear after submission in which case we can control the behavior. Is there a way we can prevent the comment from showing up in that separate panel? <img width="900" alt="image" src=""
Thanks for trying it out and noticing this! I've improved the way the comments view handles these empty comments here: We're about to release 1.92, and doesn't meet the bar to go into this release or a recovery release. It will be part of the 1.93 release.