terminal
howtonotcode.com
VS Code logo

VS Code

Platform

A popular code editor with extensive features for developers.

article 14 storys calendar_today First seen: 2026-02-09 update Last seen: 2026-02-24 open_in_new Website menu_book Wikipedia

Resources

Links to check for updates: homepage, feed, or git repo.

home Homepage

Stories

Showing 1-14 of 14

Amazon Q vs GitHub Copilot in VS Code: Speed vs Rigor

In a head-to-head VS Code test of agentic AI for a complex editorial workflow, Amazon Q Developer completed the task faster with less rework, while GitHub Copilot Pro was slower but more rigorous on nuanced prose. In a real-world evaluation using a 4,000+ word instruction set, [Amazon Q Developer](https://visualstudiomagazine.com/Articles/2026/02/23/Comparing-Amazon-Q-and-GitHub-Copilot-Agentic-AI-in-VS-Code-Tests.aspx) finished the multi-step transformation in ~5 minutes versus ~15 for [GitHub Copilot Pro](https://visualstudiomagazine.com/Articles/2026/02/23/Comparing-Amazon-Q-and-GitHub-Copilot-Agentic-AI-in-VS-Code-Tests.aspx), and required less manual cleanup afterward. Copilot showed stronger editorial rigor (e.g., catching hyphenation/preposition issues) but exhibited “mid-task amnesia” during complex formatting, increasing operator intervention. For engineering teams trialing agentic AI beyond code completion, this comparison highlights a practical trade-off: minimize rework and interruptions for throughput, or accept slower runs for finer-grained QA. Treat your evaluation like the test here—long, specific instructions; multi-phase tasks; and measured time-to-done plus QA defects—across real workflows such as doc generation for services, pipeline change logs, or templated HTML/Markdown transforms in repos.

calendar_today 2026-02-24
amazon-q-developer github-copilot-pro amazon github microsoft

Claude Code Security preview lands alongside key CLI hardening

Anthropic shipped a limited Claude Code Security preview to scan repos and suggest patches, alongside CLI updates that improve remote build control, sandboxed hooks, and context efficiency. Anthropic’s code-scanning capability is now built into Claude Code as a limited research preview for Enterprise and Team customers, with human-in-the-loop patch suggestions and expedited access for OSS maintainers, per coverage from [CSO Online](https://www.csoonline.com/article/4136294/anthropics-claude-code-security-rollout-is-an-industry-wakeup-call.html). In parallel, the CLI added a new remote-control mode for external builds, hardened HTTP hooks behind a sandbox proxy and explicit allowedEnvVars, persisted large tool outputs to disk to save context, and fixed a workspace-trust gap—plus a Windows crash fix in the VS Code extension ([v2.1.51](https://github.com/anthropics/claude-code/releases/tag/v2.1.51), [v2.1.52](https://github.com/anthropics/claude-code/releases/tag/v2.1.52)). Teams are also adjusting to a simplified CLI output that hides some file I/O; practitioners suggest prompting for a pre-action file list to restore transparency and control, effectively a dry-run step ([community thread](https://www.reddit.com/r/ClaudeCode/comments/1rdj2hm/handling_the_simplified_output_changes_in_the/)). The wider ecosystem is keeping pace—LangChain’s Anthropic integration updated headers for 1M-context handling, model IDs, and tests, smoothing orchestration in agent workflows ([release notes](https://github.com/langchain-ai/langchain/releases/tag/langchain-anthropic%3D%3D1.3.4)).

calendar_today 2026-02-24
anthropic claude-code claude-code-security visual-studio-code langchain

Copilot CLI locks down MCP; Skills mature; watch VS Code and licensing gotchas

GitHub Copilot’s latest CLI releases tighten Model Context Protocol access and add workflow polish, while teams see editor and licensing edge cases worth planning for. Copilot CLI v0.0.416 adds enforcement to block third‑party MCP servers when policy disallows them and improves help, streaming counters, terminal status layout, and undo confirmations, while v0.0.415 brought agent model selection, a plan approval menu with curated actions, an env loader, a show_file tool, and quality fixes like UTF‑8 BOM handling and MCP UI polish ([0.0.416](https://github.com/github/copilot-cli/releases/tag/v0.0.416), [0.0.415](https://github.com/github/copilot-cli/releases/tag/v0.0.415), [all releases](https://github.com/github/copilot-cli/releases)). For security‑minded orgs, this pairs with growing scrutiny of what MCP unlocks inside enterprises, from querying internal systems to chaining multi‑step actions—governance and allowlists now matter in practice ([Scalekit’s analysis](https://www.scalekit.com/blog/github-copilot-mcp-enterprise-security-governance)). On the usability front, VS Code Insiders is iterating on a model picker with search, context‑window details, and contextual quick‑pick dialogs, while Copilot in VS Code is adding deeper C++/CMake awareness for richer assistance ([Insiders discussion](https://www.reddit.com/r/GithubCopilot/comments/1rct0g9/new_in_vs_code_insiders_model_picker_and/), [InfoWorld coverage](https://www.infoworld.com/article/4136164/microsoft-brings-c-plus-plus-smarts-to-github-copilot-in-visual-studio-code.html)). Teams should also track known rough edges like Copilot chat sessions not updating without reinstall and license entitlement desync between business and personal seats ([VS Code issue](https://github.com/microsoft/vscode/issues/297226), [GitHub community thread](https://github.com/orgs/community/discussions/187874)). For repeatable DevOps/SRE workflows, “Skills” provide on‑demand, reusable AI runbooks that load progressively and bundle scripts/templates, making it easier to standardize safe automation alongside MCP‑backed tools ([Skills walkthrough](https://dev.to/pwd9000/github-copilot-skills-reusable-ai-workflows-for-devops-and-sres-caf)).

calendar_today 2026-02-24
github-copilot copilot-cli github visual-studio-code microsoft

AI IDEs go agentic: Cursor "demos" and Windsurf Cascade

AI IDEs are shifting from code suggestions to autonomous agents that run, test, and showcase changes, led by Cursor’s new demo-first experience and Windsurf’s Cascade engine. Cursor now emphasizes "demos, not diffs," with agents that can run the software they build and send video evidence of their changes ([YouTube](https://www.youtube.com/watch?v=XbZvC4KTH68&pp=ygURQ3Vyc29yIElERSB1cGRhdGU%3D)). Meanwhile, Windsurf’s agentic Cascade engine promises project-aware, multi-file edits on a familiar VS Code foundation with simple onboarding and settings import ([TechCompanyNews guide](https://www.techcompanynews.com/how-to-use-windsurf-step-by-step-guide-for-beginners/)). The direction is clear: AI IDEs are moving from inline suggestions to autonomous, runnable workflows. Operational maturity remains a concern: users report surprise auto-updates ([automatic updater](https://forum.cursor.com/t/cursor-automatic-updater/152697)), Windows update failures ([Windows updates failing](https://forum.cursor.com/t/updates-on-windows-are-failing-still-antivirus/152819)), and visibility issues before approval in a recent build ([v2.5.20 diffs visibility](https://forum.cursor.com/t/modified-code-changes-not-visible-before-approval-cursor-v2-5-20/152760)), alongside UI changes like replacing "Keep All" with auto-approve ([discussion](https://forum.cursor.com/t/the-loss-of-keep-all-the-addition-of-auto-approve/152780)). Community threads also cite rate limits even on paid plans ([Reddit](https://www.reddit.com/r/cursor/comments/1rdfk9p/what_would_make_you_switch_from_cursor_to_another/)) and a practical auth fix for a Windsurf codex plugin by clearing a local token file ([Reddit fix](https://www.reddit.com/r/codex/comments/1rdddu3/windsurf_codex_plugin_issue/)). Teams are sketching an "AI builder stack" that pairs an agentic IDE with project tracking, instant deploy previews, and AI QA to close the loop from change to validation ([HackerNoon](https://hackernoon.com/the-ai-builder-stack-linear-cursor-vercel-and-qatech?source=rss)). New native entrants like macOS-focused G-Rump hint at a widening field and specialization opportunities ([Swift forums](https://forums.swift.org/t/g-rump-a-native-macos-ai-coding-agent-looking-for-early-feedback/84953)).

calendar_today 2026-02-24
cursor windsurf codeium visual-studio-code linear

Custom Copilot agents, IDE arenas, and terminal control planes

AI agent tooling for developers is maturing with customizable Copilot skills, IDE-based model comparisons, and terminal-first control planes, while new research warns multi-agent setups often hurt results. GitHub now documents how to tailor the Copilot CLI and coding agent with project-specific instructions, hooks, and skills, enabling targeted automation for repo chores, build/test flows, and shell tasks directly from your terminal or VS Code Insiders agent mode ([customize Copilot CLI](https://docs.github.com/en/copilot/how-tos/copilot-cli/customize-copilot), [create agent skills](https://docs.github.com/copilot/how-tos/use-copilot-agents/coding-agent/create-skills)). In parallel, IDE workflows are adding native model evaluation and task skills: Windsurf’s terminal and test-generation capabilities are backed by docs and guides, and its recent “Arena Mode” for side-by-side model comparisons surfaced in industry coverage ([terminal guide](https://docs.windsurf.ai/features/terminal), [AI command assistance](https://docs.windsurf.ai/cascade/terminal), [test generation](https://docs.windsurf.ai/features/test-generation), [InfoQ LLMs page](https://www.infoq.com/llms/news/)). Agent orchestration is shifting to the command line as well: Cline CLI 2.0 positions the terminal as an AI agent control plane for multi-file refactors and scripted operations ([DevOps.com](https://devops.com/cline-cli-2-0-turns-your-terminal-into-an-ai-agent-control-plane/)). But a new Google Research study summarized by InfoQ reports that scaling to multiple cooperating agents does not reliably improve outcomes and can reduce performance, so start with single-agent flows and measure before adding complexity ([InfoQ LLMs page](https://www.infoq.com/llms/news/)). Early experiments like xAI’s Grok Build with parallel agents and arena-style evaluation point to where this is heading, but details remain in flux ([TestingCatalog](https://www.testingcatalog.com/xai-tests-parralel-agents-and-arena-mode-for-grok-build/)).

calendar_today 2026-02-17
github-copilot github-copilot-cli visual-studio-code-insiders windsurf cascade

Copilot CLI stabilizes for long sessions as IDEs move to agentic, team‑scoped AI

GitHub Copilot CLI’s latest update focuses on memory reductions and long‑session stability while IDE workflows and AI agents mature around team‑level customization and modernization tasks. GitHub Copilot CLI v0.0.410 ships broad stability improvements—fixing high memory usage under rapid logging, reducing streaming overhead, improving long‑session compaction, and adding ergonomic shell features like Ctrl+Z suspend/resume, Page Up/Down scrolling, repo‑level validation toggles, and an IDE status indicator when connected ([release notes](https://github.com/github/copilot-cli/releases)). The momentum aligns with a wider agentic shift: The New Stack frames VS Code as a “multi‑agent command center” for developers ([coverage](https://thenewstack.io/vs-code-becomes-multi-agent-command-center-for-developers/)), and Microsoft’s Copilot App Modernization details AI agents that assess, upgrade, containerize, and deploy .NET/Java apps to Azure in days ([deep dive](https://itnext.io/how-microsoft-is-using-ai-agents-to-turn-8-month-app-modernizations-into-days-a-technical-deep-8340a33513e7)). For IDE standardization, JetBrains/Android Studio Copilot customizations support workspace‑scoped settings committed under .github so teams can share constraints and conventions across projects ([guide](https://www.telefonica.com/en/communication-room/blog/github-copilot-android-studio-customization/)); also watch cost dynamics—one report shows OpenCode using far more credits than Copilot CLI for the same prompt, warranting usage instrumentation and policy checks ([user report](https://www.reddit.com/r/GithubCopilot/comments/1r2fhs2/opencode_vs_github_copilot_cli_huge_credit_usage/)).

calendar_today 2026-02-12
github-copilot-cli github visual-studio-code android-studio jetbrains

OpenAI Codex-Spark debuts on Cerebras for near-instant agentic coding

OpenAI launched GPT-5.3-Codex-Spark, a fast, steerable coding model served on Cerebras hardware to deliver near-instant responses for real-time agentic development. OpenAI and Cerebras unveiled a research preview of Codex-Spark aimed at live, iterative coding with responsiveness over 1,000 tokens/s, enabled by the Cerebras Wafer-Scale Engine, and designed to keep developers “in the loop” during agentic work [Cerebras announcement](https://www.cerebras.ai/blog/openai-codexspark). Independent coverage frames this as OpenAI’s first major inference move beyond Nvidia, positioning Cerebras for ultra-low-latency workloads while acknowledging capability tradeoffs versus the full GPT‑5.3‑Codex on autonomous engineering benchmarks [VentureBeat](https://venturebeat.com/technology/openai-deploys-cerebras-chips-for-15x-faster-code-generation-in-first-major) and broader speed-focused reporting [The New Stack](https://thenewstack.io/openais-new-codex-spark-is-optimized-for-speed/). On the tooling front, the openai/codex v0.99.0 release adds app‑server APIs for steering active turns, enterprise controls via requirements.toml (e.g., web search modes, network constraints), improved TUI flows, and concurrent shell command execution—useful for orchestrating agent runs with higher control and safety [GitHub release notes](https://github.com/openai/codex/releases/tag/rust-v0.99.0). For adoption patterns, a practical guide outlines “agent‑first engineering” using Codex CLI/IDE, cloud sandboxes for parallel tasks, an SDK for programmatic control, and GitHub Actions to plug agents into CI/CD with clear definitions of “done” [agentic workflow guide](https://www.gend.co/fr/blog/codex-agent-first-engineering).

calendar_today 2026-02-12
openai cerebras-systems nvidia gpt-53-codex-spark gpt-53-codex

Copilot CLI adds GPT-5.3-codex and workspace MCP configs

GitHub Copilot’s CLI now supports GPT-5.3-codex with workspace-local MCP configs, and Microsoft published guidance on choosing the right Copilot model while users flagged UX and quota gaps. The CLI v0.0.407-0 adds support for gpt-5.3-codex and workspace-local MCP configuration via .vscode/mcp.json, plus numerous usability fixes and improvements [CLI v0.0.407-0 release notes](https://github.com/github/copilot-cli/releases/tag/v0.0.407-0)[^1]. Microsoft shared a practical model-selection guide for Copilot, while users requested premium request rollover and highlighted UX/Plan Mode issues; also note the VS Code 1.109.1 security recovery relevant to dev environments [model-selection guide](https://techcommunity.microsoft.com/blog/azuredevcommunityblog/choosing-the-right-model-in-github-copilot-a-practical-guide-for-developers/4491623)[^2], [premium request rollover](https://github.com/orgs/community/discussions/186654)[^3], [UX/Plan Mode concerns](https://github.com/orgs/community/discussions/186670)[^4], [VS Code 1.109.1](https://github.com/microsoft/vscode/releases/tag/1.109.1)[^5]. [^1]: Adds: Details the new model support, MCP config, and fixes in copilot-cli v0.0.407-0. [^2]: Adds: Guidance on which Copilot model to use by task type and enterprise considerations. [^3]: Adds: Community request signaling pain with monthly premium request caps. [^4]: Adds: Firsthand UX feedback on tool bloat, Plan Mode confusion, and reliability trade-offs. [^5]: Adds: Notes a security-related recovery update for VS Code that may affect Copilot users.

calendar_today 2026-02-10
github-copilot copilot-cli gpt-53-codex model-context-protocol-mcp visual-studio-code

Copilot model selection guidance with quota and UI gotchas

Microsoft outlines how to choose Copilot models by task while users report quota friction and a missing Edit mode after recent updates. A Microsoft guide maps everyday, lightweight, deep‑reasoning, and agentic tasks to specific Copilot model types and flags enterprise considerations like premium request multipliers [Choosing the Right Model in GitHub Copilot](https://techcommunity.microsoft.com/blog/azuredevcommunityblog/choosing-the-right-model-in-github-copilot-a-practical-guide-for-developers/4491623)[^1]. Meanwhile, community threads flag a disappearing Copilot Edit mode after the latest chat extension update and pain around non‑rolling premium request quotas (e.g., 300 Pro / 1,500 Pro+) [Github Copilot Edit mode gone after latest update?](https://github.com/microsoft/vscode/issues/293826)[^2] [Copilot premium requests to roll over to the next month](https://github.com/orgs/community/discussions/186654)[^3], with additional confusion from a recent Pro+ subscriber report [Bought Copilot Pro+ 2 hours ago, haven't use anything and ...](https://www.reddit.com/r/GithubCopilot/comments/1r07185/bought_copilot_pro_2_hours_ago_havent_use/)[^4]. [^1]: Adds: Developer-focused model selection guidance and enterprise usage considerations (multipliers) from Microsoft. [^2]: Adds: Report that Copilot Edit mode vanished after updating Copilot Chat Extension 0.37.1 on VS Code 1.109. [^3]: Adds: User feedback on lack of premium request rollover and stated quota numbers (300 Pro / 1,500 Pro+). [^4]: Adds: Anecdotal Pro+ subscription/usage confusion visible in VS Code.

calendar_today 2026-02-09
github-copilot microsoft github visual-studio-code openai

OpenAI’s GPT-5.3-Codex rolls out to Copilot with faster, agentic workflows

OpenAI's GPT-5.3-Codex is a 25% faster, more agentic coding model built for long-running, tool-driven workflows and is now rolling out across Codex surfaces and GitHub Copilot with stronger cybersecurity guardrails. OpenAI positions the model for multi-step coding and broader "computer use" with SOTA benchmark results and notes early versions helped build and operate itself [Pulse 2.0](https://pulse2.com/openai-reveals-gpt-5-3-codex-a-faster-agentic-coding-model-built-for-long-running-work/)[^1] and [AI-360](https://www.ai-360.online/openai-launches-gpt-5-3-codex-extending-agentic-coding-and-real-time-steering/)[^2]. GitHub confirms GPT-5.3-Codex is GA in Copilot (Pro/Business/Enterprise) across VS Code, web, mobile, CLI, and the Coding Agent with an admin-enabled policy toggle and gradual rollout [GitHub Changelog](https://github.blog/changelog/2026-02-09-gpt-5-3-codex-is-now-generally-available-for-github-copilot/)[^3], while OpenAI channels have it now with API access "soon" and a new Trusted Access for Cyber pilot [Pulse 2.0](https://pulse2.com/openai-reveals-gpt-5-3-codex-a-faster-agentic-coding-model-built-for-long-running-work/)[^1] and [ITP.net](https://www.itp.net/ai-automation/openai-launches-gpt-5-3-codex-the-new-era-of-ai-powered-coding-and-beyond)[^4]. [^1]: Adds: Core capabilities, benchmark highlights, safety posture, availability across Codex app/CLI/IDE/web, and NVIDIA GB200 NVL72 infra. [^2]: Adds: Real-time steering in extended runs and cybersecurity classification/pilot context for enterprise adoption. [^3]: Adds: Concrete Copilot GA details, supported surfaces, plans, rollout, and admin policy enablement. [^4]: Adds: Additional context on broader professional task coverage and API timing.

calendar_today 2026-02-09
openai gpt-53-codex openai-codex-app github github-copilot

AI dev tools adoption: 6 pitfalls and a team playbook

A practical playbook details six common pitfalls teams face when adopting AI coding tools and how to roll them out safely and effectively. It covers skill gaps, top‑down tool choice, blind trust and review load, context starvation, and people concerns, with concrete rollout steps for teams ([CodeRabbit adoption guide](https://www.coderabbit.ai/blog/ai-coding-tools-adoption-for-teams-guide))[^1]. [^1]: Adds: Summarizes 6 pitfalls and provides actionable team rollout guidance based on real-world adoptions.

calendar_today 2026-02-07
coderabbit google claude github gitlab