Visual Studio Code (@code)

Visual Studio Code(@code)에 실험적 기능인 'Agentic Browser Tools' 추가 소식입니다. 에이전트가 통합 브라우저에서 페이지를 열고 내용 읽기, 요소 클릭, 변경 확인 등을 직접 수행할 수 있으며, 사용하려면 workbench.browser.enableChatTools 설정을 활성화하라고 안내합니다.

https://x.com/code/status/2033700872794910880

#vscode #agents #browser #developertools #aiagents

Visual Studio Code (@code) on X

🌐 Agentic Browser Tools (Experimental) in @code! Agents can now open pages, read content, click elements, and verify changes directly in the integrated browser while building your web app. Enable ⚙️ workbench.browser.enableChatTools to try it out. Learn mode:

X (formerly Twitter)
And even more so thanks to this #vscode extension:

Workspace Storage Cleanup - Vi...
Workspace Storage Cleanup - Visual Studio Marketplace

Extension for Visual Studio Code - Remove workspace storage folders which are linked to non-existent folders

Managed to free up some much needed local disk space thanks to these suggestions for #vscode:

Fixing VS Code UI Unresponsive...
Fixing VS Code UI Unresponsiveness Caused by GitHub Copilot Extension

This article shows a simple solution to a problem that doesn't seem to be adequately documented: VS Code UI lags, freezes, and delays caused by the GitHub Copilot extension.

#Microslop sneaked a "C/C++ DevTools" extension into their C/C++ Extension Pack meta-extension for #vscode. It sounds innocuous, but apparently its entire purpose is to connect your projects to #GitHub #Copilot.

I've tried a few other IDEs over the years, but nothing is as good at understanding C/C++ codebases while also having first-class CMake support.

I could try #JetBrains CLion now that it's free for noncommercial use, but they boast about AI right on the main CLion webpage as well.

Et maintenant c'est le module git de #VSCode qui semble déconner? J'ai résolu un merge conflict, mais il m'empêche toujours de faire un push depuis l'interface. Depuis le git bash ça fonctionne parfaitement.

La déterioration semble s'accélérer. Je l'ai utilisé pendant plusieurs années sans jamais voir de bug, puis c'était un glitch de temps et temps, et maintenant c'est tous les jours des trucs bizarres.

Quand un.e étudiant.e me demande "pourquoi ça ne marche pas?" (toujours des questions précises), je me retrouve souvent à répondre: "ça marche, c'est juste que VSCode n'est pas au courant. relance VSCode si tu veux que l'erreur disparaisse, mais regarde ton terminal, ça compile."

Because of editor developer shenanigans, I all of a sudden gathered spoons to try the Helix editor. And boy, howdy, going back to an editor that only works in the command line has opened an interesting yak shaving expedition.

Ya see, I've been using GUI IDEs/editors since before neovim was a thing, when I lost the energy to mess with my vim config after it broke, I went to vscode with a vim keybinding addon and stayed there because it was good enough, and it had become the place where extensions appeared first. So there I stayed, until vscode became too aggressive with its AI stuff, and I decided to check out zed. Granted, zed also had AI functionality but it had a kill switch that made it all disappear. Zed was amazingly fast, and made switching from vscode super easy, and I was happier.

Then the last few weeks happened; Zed's updated their weird terms of service to be weirder, (which I never agreed to because I installed the arch package), and vim had the most embarrassing slop PR conversations one could think of.

So, I felt the sudden urge to change the main tool of my trade once again, and no dear reader, unlike some people, I don't consider the slop machine a tool of my trade.

So I looked at neovim, which sadly triggered the claude block warning, but didn't seem as brainwormed as vim yet. I heard about gram, which was an unfucked version of zed, but when I looked at it, wasn't properly packaged for my setup. Then I also looked at helix, which some people have said good things about, especially about its different take on modal editing, and it didn't have any obvious signs of slop at all.

As I had the spoons, I decided to try this helix thingamajig for a week, and see how it would mess up my muscle memory, which has been abused by vi(m)-style keybindings since the 90s.

This is all a long winded way to say that I am now back on a pure terminal-based development setup and... wow this stuff improved.

I discovered Zellij, which redefined what I thought of as a terminal multiplexer. I've used tmux for a long time, and screen before that, but Zellij makes its panes feel like discrete windows when it comes to selecting text and mouse controls.

Helix is very interesting, it sure is messing up my muscle memory, but it sure feels like it might be worth it, as some more complex stuff feels more logical than it ever did in vim. And because of the language server protocol, it does all the rust/go/etc operations just as good as zed or vscode did, better even, as I find the UI calmer and less surprising than I did in those GUI editors.

I've also been playing with lazygit and yazi, although not as much, as I've always used bash/zsh/fish for git and file management, so my need for those isn't too great. And then there's a whole lot of other small modern CLI tools that make life better, like fd, replacing find, sd replacing sed, and more.

The point of this long, barely coherent rant is to get off my chest just how much nicer terminal based development has become since last I gave it a proper go, and that if you haven't looked at this in a long time, or even ever, it might be worth a try.

#Terminal #CLI #HelixEditor #Helix #Zed #tmux #Zellij #VSCode #SoftwareDevelopment #vim #neovim

Dew Drop – March 16, 2026 (#4625) – Morning Dew by Alvin Ashcraft