GitHub’s latest Copilot weekly release puts the biggest operational change in the command-line tool: its runtime has been rewritten in Rust for faster performance, while interrupted sessions can now be restored. The update also expands team-based agent work in Slack and Teams and adds tighter controls across the Copilot app, JetBrains, VS Code, and Visual Studio.

Source

Google is developing native Windows 11 and Windows Subsystem for Linux support for Antigravity, its agentic development platform. The move would let Antigravity run coding agents, shell commands, builds, and file operations in Linux environments on Windows, while a separate native Windows implementation could reduce the platform’s reliance on browser-based or Electron interfaces.

Source

The August 2026 Azure Developer CLI release train makes two notable changes for deployment teams: the extension framework is now generally available, and Azure Functions can deploy containers from Dockerfiles, existing images, or Azure Container Registry remote builds. The new `docker.imagePassthrough` option can send an already-published image to its destination without requiring Docker or Podman on the deployment machine.

Source

After launching Gemini Enterprise for Legal, a preview that connects permission-aware agents to firms’ document and case systems, Google is adding pay-as-you-go billing, project spending caps, and commitment discounts to Gemini Enterprise. The changes target unpredictable agent workloads that can make fixed per-user pricing difficult to forecast.

Source

Kubernetes v1.37 adds 67 enhancements, including default-enabled HPA scale-to-zero support and stronger kube-apiserver protection during startup and recovery. The release also moves admission-control configuration toward local manifests, allowing policies to remain available even when etcd cannot be reached.

Source

Anthropic’s flagship Claude Fable 5 has captured only about 11% of corporate spending on the company’s models two months after launch, as businesses favor cheaper systems for routine coding, analysis, and automation. The weak premium uptake contrasts with Anthropic’s broader enterprise gains, suggesting that companies want access to frontier AI but are rationing its most expensive model.

Source

OpenAI is reinstating the five-hour usage limit for Codex and ChatGPT Work on ChatGPT Plus subscriptions from August 25, after temporarily relying only on a weekly cap. The change is intended to control computing demand and prevent users from consuming an entire week’s allowance during one extended session.

Source

Microsoft Teams users can now turn a channel, thread, or direct message into a shared GitHub Copilot cloud-agent session. The public preview lets teams steer coding work together, but administrators must enable cloud-agent and sandbox policies, manage separate usage budgets, and consider extra approval requirements for Copilot-created pull requests.

Source

Google is bringing its Antigravity agentic AI coding assistant under Gemini Enterprise subscriptions, giving organizations centralized controls for licensing, spending, security, compliance, and auditing. The move also makes Antigravity available inside Visual Studio Code, Visual Studio, JetBrains IDEs, and Zed.

Source

GitLab 19.3 lets GitLab Dedicated customers run the Duo Agent Platform inside the same single-tenant environment and region as their existing workloads, keeping AI processing within their established security boundary. The release follows GitLab 19.2’s autonomous agents with tighter controls for data residency, model selection, spending, secrets, and automated vulnerability fixes.

Source

GitHub has attributed its 7-hour-47-minute outage on August 17 to a Central US infrastructure component that failed to scale when traffic reached a new peak. The resulting capacity shortage cascaded into authentication, GitHub Actions, APIs, pull requests, issues, Pages, webhooks, and Copilot, while a client-side retry loop prolonged recovery.

Source

Slack Code turns AI coding agents into visible collaborators by creating dedicated channels for each development task. Teams can work with Claude Code, Devin, Vercel Agent, or GitHub Copilot without leaving Slack, while non-technical colleagues can follow, pause, or stop the work.

Source

Visual Studio Code 1.135 Insiders improves Copilot agent management with consistent sandbox policies, enterprise-controlled permissions, workspace-aware session handling, and notifications for sessions that need attention. The release also expands voice interactions and adds a signed-out BYOK testing option for the Copilot Agent Host.

Source

A Microsoft deployment pattern puts Azure Landing Zones under version control and approval gates instead of relying on manual portal configuration. By combining Azure DevOps with Terraform, organizations can provision subscriptions, networking, identity, policies, security, and monitoring through a repeatable pipeline that produces an audit trail before changes reach production.

Source

Cursor has launched Origin, a code-hosting platform that aims to challenge GitHub just as GitHub endured a worldwide outage lasting more than six hours, with error rates reportedly nearing 20%. Origin supports repositories, collaborative editing, and pull requests, while allowing teams to keep existing GitHub workflows in place.

Source

Docker is expanding beyond container packaging with Docker Sandboxes, which run autonomous AI coding agents inside isolated microVMs, and Docker AI Governance, which lets organizations control their access to filesystems and networks. The shift gives administrators a way to adopt AI-assisted development without allowing unpredictable agents to reach developer laptops or internal systems directly.

Source

GitHub’s August 17 outage, whose recovery began after Microsoft identified the failing component, was caused by a monitoring blind spot that let Central US load balancers overload. GitHub now says a Visual Studio Code retry bug then amplified Copilot authentication traffic roughly tenfold, extending the disruption to 7 hours and 47 minutes.

Source

VS Code 1.134 adds a grid layout for running related AI chats side by side, plus a prompt timeline that shows which requests changed files. Building on side chats introduced in VS Code 1.132 and the chat-navigation improvements covered in VS Code 1.133, the update focuses on keeping long agent sessions understandable and reviewable.

Source

GitLab a sorti hier (lundi 17 août), un correctif d'urgence , complètement en dehors de son calendrier habituel, pour une faille qui permet à quelqu'un sans compte ni mot de passe de modifier ou de supprimer vos projets publics et des données utilisateur. Hé ouais c'est chaud et c'est pour ça que son score CVSS est de 9,4 sur 10.

5 jours plus tôt, le 12 août, GitLab publiait son patch de routine pour la 19.2, 19.1 et 19.0. C'est un périmètre normal puisque sa politique de maintenance ne couvre que la version stable et les deux précédentes. Mais comme là, on est dans l'exceptionnel, ce correctif du 17 août en couvre une quatrième, la 18.11, dont le support avait pris fin le 16 juillet dernier. Ils sont allés rouvrir une branche morte juste pour patcher ce GROS problème !

La faille elle-même, on n'en sait presque rien par contre. Estampillée CVE-2026-19478, c'est une histoire de directive GraphQL, mais GitLab ne dit ni laquelle, ni dans quelles conditions ça se déclenche. Les détails techniques sortiront vers la mi-novembre, c'est-à-dire 90 jours après le correctif, comme d'habitude, histoire d'être sûr que tout le monde ait patché son install.

Maintenant, la bonne nouvelle c'est que si vous êtes sur GitLab.com ou sa version Dedicated , vous n'avez rien à faire, puisque c'est déjà patché. En fait cette histoire ne concerne que les instances auto-hébergées.

Et parmi elles, tout le monde n'est pas impacté de la même manière. En effet, le vecteur d'attaque passe par le réseau et vise les projets publics. Cela veut dire que votre instance planquée derrière un VPN, sans visibilité publique, risque beaucoup moins que celle qui expose ses dépôts à Internet.

Ensuite, pour la mise à jour, ça dépend d'où vous partez. Entre la 18.2 et la 18.10, aucun correctif n'existe sur votre branche. Il faudra upgrader jusqu'à la 18.11.11, en vous arrêtant aux paliers de 18.5 et 18.8 s'ils sont sur votre route.

Si vous tournez déjà en 18.11, prenez la 18.11.11. Sur une 19, c'est 19.0.8, 19.1.6 ou 19.2.4. Et plus ancien que 18.2 ? Bah là, GitLab ne liste pas ces versions parmi les affectées, mais elles ne reçoivent plus de correctif depuis un bon moment, donc ce serait bien de mettre à jour quand même, hein...

Pour le moment, personne n'a signalé d'attaque et aucun exploit ou PoC n'a fait surface sur GitHub. Ça ne veut pas dire grand-chose, je vous l'accorde mais on se rassure comme on peut...

Allez, bon courage !

Source : The Hacker News