State of AI: what the last 24 hours mean for enterprise leaders

What happened in the last 24 hours

Five developments between Friday morning, 30 October, and Saturday morning, 31 October (Bucharest time), tell us more about where AI stands than any single product launch. Two of them began on Thursday, 29 October, but were confirmed or reported on Friday.

1. Markets turned on AI spending. On 30 October the Nasdaq fell 2.9%, its largest one-day drop since early June, after Intel and Amazon results showed heavy cash burn tied to AI investment, Reuters reported. Intel fell 28.6%, the PHLX semiconductor index lost more than 7% and Alphabet slipped again after a 12.6% drop on Thursday, when it reported that AI spending had turned its cash flow negative. According to TechCrunch, Alphabet, Amazon, Meta and Microsoft have outlined more than $740 billion of capital spending this year. Amazon reported negative free cash flow of $42.4 billion over the past 12 months, even though AWS grew 39%.

2. The cost of financing AI capacity became visible. The Financial Times reported, as relayed by TechCrunch, that Blackstone now expects Anthropic to receive a "high junk" (double-B) credit rating after its IPO, reversing an earlier expectation of investment grade. Anthropic and Blackstone declined to comment. Separately, The Information reported and Bloomberg corroborated that Nvidia is in talks to guarantee debt for Nscale's planned Anthropic data centre in West Virginia (TechCrunch). Both items are reports, not confirmed transactions.

3. An AI coding tool became a supply-chain attack route. Cursor said that malicious versions (2.1.312 and 2.1.313) of the Claude Code extension were available in its VS Code extension marketplace for about 11 hours on 29 October. The code tried to plant an attacker's SSH key, open a reverse tunnel, set up persistence and send host details, including the names of environment variables (Cursor security notice). Cursor estimated that at most 5,000 users were affected, Ars Technica reported. Microsoft Threat Intelligence said on 30 October that the packages did not come from the Visual Studio Marketplace or npm, and that Anthropic had confirmed its systems were not compromised. How the attacker got the package published has not been explained. Updating to the clean version does not remove what the malicious one installed.

4. AI companies agreed on one opt-out signal for web content. OpenAI, Google, Microsoft and Anthropic said they will honour a shared "policy token" in robots.txt, proposed at the Internet Engineering Task Force (IETF), that lets a website state its AI training preferences once for all of them (The Verge). Anthropic already supports it. Google and Microsoft plan to support it next year, and OpenAI "in the coming months". Microsoft says it will let sites opt out of training and of grounding separately, without affecting Bing search results.

5. Agentic commerce is still mostly a promise. On DoorDash's third-quarter earnings call, chief executive Tony Xu said outside AI agents had generated "several hundred orders" since its connector launched less than a month ago, against almost 1 billion orders in the quarter (Ars Technica). DoorDash's own built-in AI ordering features are not included in that number.

Two smaller items fit the same picture. Apple said Apple Intelligence will reach China with iOS 27.3, using Alibaba's Qwen for some chatbot features (The Verge). And researchers showed that a shared ChatGPT link could run code in a victim's session and read private chats. OpenAI fixed it on 26 October, and the details were covered on 31 October (The Hacker News).

The state of AI, read from one day of news

Demand is real, but so is the bill. Cloud revenue keeps growing, yet investors are now pricing the cash and debt needed to sustain it. Capacity is increasingly financed through bonds, guarantees and partner balance sheets rather than from profits alone. That makes the supply side of AI more sensitive to interest rates and credit conditions than most buyers assume.

Model providers are becoming financial counterparties as well as technology suppliers. A speculative-grade rating for a leading model developer, if it happens, would not stop its services. It would mean its growth depends more on partners such as cloud providers and chipmakers. For enterprise buyers, the stability of the whole chain behind a model now matters, not only the model's quality.

The attack surface has moved to developer tools and agents. The extension incident did not need a flaw in the model. It used the trust developers place in an official listing and in automatic updates. AI coding assistants run with broad access to source code, credentials and cloud tooling, so a compromised plug-in has the reach of a privileged insider.

Rules are forming through industry standards before regulation. The shared opt-out token is a voluntary, technical answer to a legal and commercial dispute over training data. It will simplify things for publishers, but it is not a licence and does not settle questions of copyright.

Adoption is uneven. Agents handle long, complex tasks well in some settings, but for simple, habitual purchases customers still go straight to the app. Business cases built on agents replacing existing channels quickly deserve scrutiny.

What this means in practice

For CIOs and procurement

Review concentration risk on AI suppliers. Know which model providers, clouds and data centre partners your critical workloads depend on, and what happens if prices rise or capacity is rationed.
Ask for contract terms that protect you: price change notice, data portability, model version stability and exit support.
Keep an abstraction layer between your applications and any single model API so that switching is a planned change, not an emergency.

For CISOs and engineering leaders

Treat IDE extensions, AI coding assistants and MCP connectors as software supply chain. Maintain an allow-list, pin versions for sensitive teams and decide deliberately where automatic updates are acceptable.
If teams use Cursor, check now whether anyone installed version 2.1.312 or 2.1.313 of the Claude Code extension, and follow the vendor's steps, including credential rotation.
Keep long-lived cloud keys and tokens out of developer environment variables; use short-lived credentials and a secrets manager.
Log what agents do, not only what users do, so an unusual action can be traced and stopped.

For CEOs and CFOs

Expect AI pricing and packaging to change as suppliers face pressure to show returns. Budget scenarios should include higher unit costs, not only falling ones.
Tie AI investments to measurable outcomes per process, and review them quarterly. The market is applying that discipline to suppliers; it makes sense internally too.

For digital and content teams

Decide your organisation's position on AI training and grounding use of your public content, then implement it in robots.txt as the shared token is adopted. Keep it separate from search visibility.
For agent-based customer channels, run small pilots with clear metrics before committing to large integrations.

The bottom line

The last 24 hours did not bring a breakthrough model. They brought something more useful for planning: evidence that AI is entering a phase where cost of capital, supply chain security and practical adoption matter as much as capability. Organisations that manage AI as critical infrastructure, with supplier diversity, controlled tooling and outcome-based budgets, will be in a better position whichever way the market moves next.

Facing a similar architecture decision?

An introductory conversation can help clarify options and risks. No obligation and no requirement to share assessment results.

Request an introductory discussion ↗

← All articles