AI Coding Assistants — 2026-05-06

Today's Lead Story

Microsoft Fixes VS Code After Copilot Auto-Credited Itself as Code Co-Author

• What happened: Microsoft released a fix for VS Code after its Git extension began automatically adding GitHub Copilot as a co-author on commits by default — without explicit developer consent. The Register reported the reversal, noting that developers were not pleased to discover the bot was being credited alongside them in their version history.
• Who it affects: Any developer using VS Code with the GitHub Copilot Git extension enabled — a massive slice of the professional developer population.
• Why it matters: The episode reveals a growing tension between AI tool vendors wanting to demonstrate value (and collect usage data) and developers who expect transparency and control over their own codebases. Automatic attribution without opt-in consent is a red line for many engineers, and Microsoft's quick reversal signals it heard the message loud and clear.

Release & Changelog Radar

• GitHub Copilot (supported models update, past 7 days): GitHub's Copilot documentation page for supported AI models was updated within the past week, reflecting ongoing model availability changes inside Copilot — practical impact is that developers should re-check which frontier models are accessible via their Copilot subscription tier before assuming the lineup is static.

• awesome-cli-coding-agents directory (updated ~5 days ago): A curated GitHub repository tracking terminal-native AI coding agents was updated, now covering open-source tools (Aider, Goose, Pi, OpenCode), platform agents (Claude Code, Codex CLI, Gemini CLI), and emerging alternatives. Notable entries include claw-code-agent (⭐450, a Python-only Claude Code rewrite born from the March 2026 source leak) and Coro Code (⭐358, an open-source Claude Code alternative). The directory signals just how crowded the CLI agent space has become.

• Cursor (past 7 days — Automations feature): Cursor's agentic "Automations" system — launched in early March 2026 — continues to be the most discussed recent product addition: it lets developers trigger coding agents automatically from Slack messages, new code additions, or timers, moving Cursor decisively into the autonomous workflow territory. Developers evaluating Cursor vs. alternatives are still actively benchmarking this feature.

Benchmark & Performance Watch

• SWE-bench / AI agent benchmark compendium: The community reference repository tracking 50+ benchmarks for AI agents — covering function calling, general reasoning, coding, and computer interaction — remains the go-to aggregator. No single new benchmark score dropped in the past 24 hours, but the compendium shows coding & software engineering benchmarks as the most actively contested category heading into May 2026. Developers looking for current leaderboard positions should check the live compendium directly.

• Cursor community self-reported benchmarks (r/cursor, ~3 days ago): A Reddit thread on r/cursor summarizing a 2026 review describes Cursor as "the fastest-growing SaaS product in history — reaching $2B annualized revenue by February 2026," which the community is treating as a proxy signal of real-world developer preference, even if not a formal SWE-bench score. Threads are actively debating whether revenue velocity is a meaningful proxy for coding quality.

Developer Sentiment Pulse

• The Register comments on the Copilot co-author story: Developers responding to Microsoft's VS Code reversal expressed frustration that the opt-out was necessary in the first place — "Devs not thrilled that Git extension added the bot as co-author by default" captures the mood. It reveals a broader concern: AI tools are increasingly making unilateral decisions about developer workflows, and trust is fragile.

• r/cursor (~3 days ago): Community members on the Cursor subreddit are sharing a detailed 2026 review calling Cursor "the AI code editor that replaced VS Code," with enthusiastic endorsements of its agentic Automations system — but also debates about token limits and cost-per-task at scale. The sentiment is broadly positive but cost-consciousness is a recurring friction point.

• GitHub (bradAGI/awesome-cli-coding-agents, ~5 days ago): The rapid star growth on open-source Claude Code alternatives like claw-code-agent and Coro Code — born from the March 2026 Claude Code source leak — signals that a meaningful segment of developers prefers hackable, dependency-free CLI agents over polished commercial products. The community appetite for forks and alternatives appears stronger than ever.

Deep Dive: The Copilot Attribution Controversy and What It Signals for AI Tool Trust

Microsoft's decision to automatically list GitHub Copilot as a co-author on Git commits — and its subsequent reversal — is more than a UX misstep. It exposes a structural tension at the heart of the AI coding assistant market.

Vendors have strong incentives to make AI contribution visible: it justifies subscription costs, generates usage data, and builds brand recognition in developer workflows. But developers maintain firm boundaries around authorship, intellectual property, and transparency. When a tool silently inserts itself into a commit record, it raises immediate questions: Who owns this code? Does my employer's IP policy cover AI-attributed commits? What does this mean for open-source licensing?

The speed of Microsoft's reversal — reported within roughly a day of the story breaking — suggests the company was caught off guard by the intensity of the reaction. For competing tools like Cursor, Windsurf, and Claude Code, the episode is instructive: any feature that touches code ownership or attribution requires explicit opt-in, not opt-out. The developer community's radar for autonomy violations is extremely sensitive.

Second-order effect to watch: enterprise legal and compliance teams are now more alert to what AI coding tools are silently writing into their Git histories. Expect this to become a formal procurement consideration for enterprise Copilot and competing tools going forward.

Business & Funding Moves

• Cursor / Anysphere: The company behind Cursor reportedly hit $2B in annualized revenue by February 2026 — a figure being widely cited in community discussions as evidence that AI-native code editors have found genuine product-market fit. While no new funding round has been announced in the past 24 hours, the ARR milestone keeps Cursor at the center of market conversations.

• Microsoft / GitHub Copilot: The co-author attribution reversal (see lead story) is itself a business signal — Microsoft is clearly willing to move fast on Copilot feature additions, even when they generate backlash, and equally willing to reverse quickly. This pattern suggests aggressive product velocity ahead, which will keep competitors on their toes. Watch for more opt-in/opt-out debates as Copilot pushes further into agentic territory.

What to Watch Next

• Microsoft's next Copilot move in VS Code: After the co-author attribution reversal, all eyes are on what GitHub ships next in the Git/Copilot integration space — and whether future features will default to opt-in rather than opt-out. Any new announcement will face heightened community scrutiny.
• Continued growth of open-source Claude Code alternatives: The claw-code-agent and Coro Code forks are gaining stars rapidly. If they achieve feature parity with the commercial Claude Code CLI, this could put meaningful pressure on Anthropic's monetization strategy for the tool.
• Enterprise procurement policy shifts on AI attribution: Following the Copilot controversy, watch for legal/compliance guidance from large enterprises on how AI-attributed commits interact with IP policies — this could reshape how Copilot and competitors market their enterprise offerings.

Reader Action Items

• Check your VS Code Git settings now: If you use GitHub Copilot, open your VS Code settings and search for "co-author" or "Copilot commit" to verify the attribution feature is configured to your preference — don't assume the reversal reset your existing settings automatically.
• Explore the awesome-cli-coding-agents directory: Browse for a fresh map of 30+ CLI-native coding agents — especially if you're evaluating open-source alternatives to Claude Code or Codex CLI.
• Test Cursor's Automations feature: If you're a Cursor user, try setting up an Automation triggered by a Slack message or a simple timer — this is the product's most differentiated agentic capability right now and worth benchmarking against your own workflow before competitors ship equivalent features.

1 sources

github.com

github.com