Posts tagged with "Claude Code"

Anthropic relaunched Claude Code Projects on 17 September as a coordinator running parallel cloud threads that open and auto-fix pull requests, but the beta runs only on consumer Pro and Max plans, with no organisation-level controls, no Foundry route and github.com only. For Swedish and EU teams on Azure, that means company code processed under an employee's personal privacy settings unless you set a policy and use the GitHub App install as your control point.

Anthropic reports CI jobs grew 25x in six months as agents took over 80% of code authoring, and the single-writer service behind its test selection failed in stages: 70 days of relief from a bigger machine, then 29, then less than one. Here is what that curve costs on Azure Pipelines versus GitHub Actions, and which architecture in your own pipeline breaks first.

Spotify routes bulk file reads and boilerplate generation out of Claude Code to a cheaper worker model, cutting Claude token usage on those reads by 90% in tests on a Java monorepo. The pattern needs no Portal licence: Claude Code hooks, two wrapper scripts and a flash-class model in Microsoft Foundry rebuild it inside your own Azure tenant, with the boundaries Spotify itself draws around editing and reasoning.

A repository that arrives as a zip, sync folder or USB stick can execute attacker code the moment a CLI coding agent opens it, before any approval prompt and outside the agent sandbox. Manifold Security's GitSpawn disclosure covers eight findings across Claude Code, Codex, Cursor, Goose, Hermes Agent, Qwen Code and Grok Build, with four unpatched at publication.

A published attack chain achieved remote code execution against Claude Code in auto mode, with the safety classifier approving the steps that led to compromise and then blocking the cleanup command. What the break teaches teams running AI coding agents, and how to build real isolation on Azure with Hyper-V sandboxes, default-deny egress and short-lived credentials.

Claude Opus 4.8 arrives at unchanged pricing with an effort control on all plans, a fast mode at a third of the previous fast-inference cost, and a Messages API change that lets system entries sit inside the messages array so mid-task instruction updates no longer invalidate the prompt cache. Worked token math shows cache hit rate remains the biggest cost lever, and a four-question framework matches effort, speed and fan-out to each workload.