VS Code Agent mode: available to all users and supports MCP.

VS Code Agent mode: available to all users and supports MCP.
So it does look like the TypeScript language server has a limit of 4MB source size where it disables type checking (and actually shows an erroneous error stating that exports that exist in the file do not exist) for files that are imported but not open in the current workspace/session.
Still not sure if this is documented anywhere or not (haven’t been able to find it, if it is).
99.99999% of the time, unless you’re doing niche stuff like I am, you won’t run into this.
Workaround: should you have such a large file, e.g., with a large generated object, try and refactor to split it up into multiple files and rejoin it a separate file. The actual object size/memory usage isn’t the issue, it’s the file size.
Vibe coding with GitHub Copilot: Agent mode and MCP support rolling out to all VS Code users.
https://github.blog/news-insights/product-news/github-copilot-agent-mode-activated/
I use #VSCode and keep the update announcements on, in case there's anything useful that gets added.
As far as I can tell, v1.99 has ZERO useful features. But it's hard to tell because there's just so much Copilot stuff that it's hard to see potentially useful stuff amongst the junk!
Right, well, I can reproduce it with a simple example so I just filed a bug. Let’s see if it’s a known issue/limitation or what.
https://github.com/typescript-language-server/typescript-language-server/issues/951
Screen recording showing the issue:
Browser MCP – Automate your browser using Cursor, Claude, VS Code
Technology & Friends - Rob Conery on Productivity Features in GitHub Copilot with host David Giard.
https://davidgiard.com/rob-conery-on-productivity-features-in-github-copilot
I mean, I don't necessarily *want* to dump #vscode in favor of #neovim, but vscode uses so much memory and cpu, especially with remote or #container #development. But here I am, learning how to configure neovim. I guess I'm learning #lua too. #programming #ide
#Microsoft is blocking their extensions from being used in derivatives of #VSCode. Microsoft SOP for eliminating competitors.
The latest proprietary #VSCode extension that no longer works in non-Microsoft builds of the MIT licensed VS Code source code appears to be C and C++ support.
Your regular reminder: every day more of VSCode functionality is proprietary, and increasingly #FOSS hostile.
Visual Studio Code March 2025 (version 1.99) Release Notes.
Streamline Azure Tasks in VS Code Using GitHub Copilot | by Dan Wahlin.
#VSCode extensions 'Material Theme – Free' and 'Material Theme Icons – Free' with 9 million installs pulled over #security risks
Researchers told BleepingComputer that their specialized scanner detected malicious activity in the extension's code. One of the researchers, Amit Assaraf, says they believe the malicious code was introduced in an update to the extensions, indicating either a supply chain attack through a dependency or the developer's account was compromised.
https://www.bleepingcomputer.com/news/security/vscode-extensions-with-9-million-installs-pulled-over-security-risks/
Friday is the big day, celebrating Microsoft’s 50 years of innovation!
I made the journey out to cover the event tomorrow, talk to some legendary folks at Microsoft, try all the new goodies being released! Here is a sneak peek!
Mermaid Chart VS Code Plugin: Mermaid.js Diagrams in Visual Studio Code
Working with .NET 10 Without Mucking Up Your Machine | by Joseph Guadagno.
https://www.josephguadagno.net/2025/03/27/working-with-dotnet-10-without-mucking-up-your-machine
Visual Studio Code + Model Context Protocol (MCP) Servers Getting Started Guide | What, Why, How with James Montemagno.