Issue #211  (Human Commits Co-Authored by Copilot?)05/06/26

Advertisement
 
Demystify AI for Your Business in Just 4 Steps

Overwhelmed by AI? HubSpot's free guide cuts through the noise. Get the ultimate crash course for non-technical entrepreneurs who want to harness AI's power – without getting lost in the jargon.

HubSpot CRM

"AI for Business Builders" delivers:

  • A 4-part roadmap to AI mastery
  • Jargon-free explanations of large language models
  • Practical prompt engineering tips you can use today
  • Real-world examples of AI boosting businesses like yours

Arm yourself with the knowledge to make informed AI investments and skyrocket your startup's growth.


As discussed in this huge thread on Hacker News, it was discovered that the VS Code team had approved a commit that causes VS Code to insert 'Co-Authored-by Copilot' into commits, even if those commits are authored by a human.

There was quite a bit of criticism for Microsoft in the thread and elsewhere as the news about this spread. To their credit, however, the team member responsible chimed in on the thread and took responsibility (it's currently the top comment):
 
"I am the person who approved this PR and would like to acknowledge and apologize for the mistake of turning this feature on by default without sufficient upfront validation.

There was no ill intent by evil corporation, but rather a desire to support functionality that some customers expect of VS Code w.r.t. AI-generated code. As folks mentioned here - many similar tools do this as well.

Obviously, it should not be on when disableAIFeatures is on and it should not be reporting changes that were not done by AI. I'll work on fixing those and meanwhile revert default to off in 1.119 update.

You can see the commit in the screenshot below:
 
Authored by Copilot Commit in VS Code

There's a part of me that thinks this isn't such a big deal. I mean, it wasn't a security issue, it was mainly just a 'credit' problem. But then I wonder how something like that could get past someone without recognizing the far-reaching effects it could have on the VS Code team's reputation.

As of this writing, version 1.119 has not been pushed out yet, but now that VS Code is on a weekly update schedule, you should see that fixed in the next few days.

Now on to this week's hand-picked links!
 

VS Code Tools

CodeVisualizer β€” A VS Code extension that provides two main visualization capabilities: function-level flowcharts for understanding code control flow, and codebase-level dependency graphs for analyzing project structure and module relationships.

OWASP Dependency Check β€” A VS Code extension that adds a software composition analysis utility that identifies project dependencies and checks if there are any publicly disclosed vulnerabilities, with support for Java and .NET and experimental support for Ruby, Node.js, Python, and C/C++ build systems.

Do You Know VS Code's Native Features? β€” A 346-page e-book in EPUB and PDF formats that includes 150+ native tips and 450+ screenshots, to help you customize and learn Visual Studio Code, the world's most popular code editor.   Sponsor 

Opilot β€” A VS Code extension that integrates the full Ollama ecosystem – local models, cloud models, and the Ollama model library – directly into VS Code's Copilot Chat interface. Your conversations never leave your machine when using local models, and you can switch between models without leaving the editor.


VS Code Theme of the Week

Slatewave β€” A theme that's part of a family of themes for 30+ applications (CLI tools, editors, etc.) that's "built around a slate foundation and a teal signature, with sky/rose/purple/amber accents."

Slatewave Theme for VS Code

Like others I've featured, this would be a neat way to have the same color scheme in all your apps, assuming of course that you enjoy the experience of it.

VS Code Articles & Videos

Microsoft Fixes VS Code After App Gives Copilot Credit for Human's Work β€” This is a good summary of what happened with the problem mentioned in the intro,  which made the rounds on tech news sites this past week, and how it was corrected by the VS Code team.

I Switched From VS Code's Marketplace to Open VSX, and Microsoft's is the One Falling Behind β€” The author makes the argument that all VS Code forks should have access to the official VS Code Marketplace, so he explains the benefits of using Open VSX instead.

Meco: Enjoy Newsletters in a Space Designed for Reading β€” Meco is a distraction-free space for reading and discovering newsletters, separate from the inbox. Add your newsletters in seconds and liberate your inbox today!    Sponsor 

Debugging Your VS Code Agent Interactions β€” A look at the Agent Debug Log panel, which was released in preview mode as of VS Code 1.110.

Best of the Rest

Icarus IDE β€” An incredibly light, performance focused C/C++ IDE with many features and customizations (see associated video for a breakdown).

Parallel Code β€” An AI coding tool that allows you to run Claude Code, Codex, and Gemini side-by-side, each in its own Git worktree.

Leadership Can’t Be Automated β€” AI can help you move faster, but real leadership still requires human judgment. The free resource 5 Traits AI Can’t Replace explains the traits leaders must protect in an AI-driven world and why BELAY Executive Assistants are built to support them.  Sponsor 

Is the IDE Dead? β€” "IDEs as we know them may stop being the primary tool for software work, or heavily evolve."

Suggestions?

If you have any link suggestions, including a tool, article, or other resource related to VS Code or another IDE, you can hit reply, send it via DM on X, or via chat on Bluesky.

That's it for this issue.

Happy VS Coding!
Louis
VSCode.Email
@LouisLazaris
Copyright © VSCode.Email. All rights reserved.

Not affiliated with Microsoft, Visual Studio Code, or any of its trademarks.