Construction AI: now it's plumbing - Claude inside Bluebeam, and the standards racing to catch up

Bluebeam Max launched globally on 19 May 2026 as a premium subscription tier for Bluebeam Revu, and the headline is structural: Anthropic's Claude is now integrated directly into Revu via MCP (the Model Context Protocol), so teams can use natural-language prompts to extract data, summarise markups and build estimates without leaving the drawing. The launch ships four AI features that target real, daily pain - Smart Overlay (detecting design changes and discrepancies across phases, disciplines and drawing scales), Smart Review (flagging scope gaps and missing information before they become RFIs and delays), automatic sheet stitching for linear and infrastructure jobs, and "Magic Markups" to cut repetitive take-off clicks. Bluebeam reports a beta of 2,000+ users; early adopters including Martin-Harris Construction and KPFF's LA civil office describe it as a "gamechanger" for design and planning review (vendor-supplied quotes).

The significance is not any single feature - it's the distribution. This is mainstream AEC software that UK contractors, consultants and QSs already open every day, with frontier AI now built into the workflow rather than living in a separate tool. That lowers the adoption barrier considerably: no new platform to procure, no separate login, no data-migration project. It also normalises MCP as the way AI reaches into construction software, which matters for everything below.

The flip side of Bluebeam Max arrived the same week. AEC Magazine's May/June 2026 issue makes a sharp, uncomfortable point: the draft revision of the core BIM information-management standard, DIS/ISO 19650-1:2026 (published for consultation in March 2026), does not mention agents, autonomous workflows or agentic AI at all - despite vendors actively shipping agent-capable platforms with MCP hooks to customers right now. The standard that governs how information is managed across a project has, as the piece puts it, precisely nothing to say about the agentic shift.

The deeper argument is about MCP itself. It is an excellent interface-layer protocol for getting human intent into an application quickly - but it is not a framework for delegated authority, and it is increasingly being asked to carry a governance-layer load it was never designed for. Through spring 2026, MCP has come under visible security pressure, with MCP servers in the wild found to be vulnerable at scale. So the picture is: AI is being plumbed into BIM tools via a protocol that solves "how do I ask" but not "who is allowed to act, on what, and how is it logged" - and the standard meant to govern information management hasn't addressed it.

Launched at Google I/O on 19 May, Antigravity 2.0 turns Google's agentic coding tool into a standalone, agent-first platform: a desktop app, a CLI written in Go, and an SDK for custom workflows, all sharing the same agent harness. The defining idea is multi-agent orchestration as a first-class concept - a planner agent can spawn subagents at runtime, with several specialised agents working at once (one writes code, one runs terminal commands, one tests in the browser) and tasks that can run scheduled in the background. It's powered by Gemini 3.5 Flash, the fast, cheap engine we covered last week. It's free to start, with paid tiers (AI Pro at ~£16/$19.99 a month, AI Ultra at $100 a month with 5× usage limits) for heavier use - so the "completely free" framing doing the rounds is only half true.

The honest head-to-head: independent reviews put Antigravity 2.0 ahead on breadth and speed (IDE + CLI + SDK, parallel orchestration), while Claude Code still leads on raw coding quality and production-ready output per SWE-Bench, and matches on price via Claude Pro at $20. For most construction software teams the takeaway isn't "switch" - it's that capable agentic coding is now a commodity at ~£16-20 a month, and the differentiator is orchestration breadth versus output quality, not access.

Three of this week's threads point to the same operating discipline. AI is now embedded in mainstream tools (Bluebeam Max), the standard governing your information hasn't addressed agents (ISO 19650), and the model layer is commoditising and being over-claimed (Antigravity's "free", Qwen's "open-weight"). The intent and investment are there - IFS's research across 300+ senior construction and engineering executives found 91% planning to increase AI investment, with project delivery and business intelligence the leading use cases. The gating issue is no longer appetite; it's verification and control.

So the practical posture for an ops or digital lead is unglamorous and durable: verify model and tool claims against primary sources before committing; build a routing layer that sends each workload to the cheapest model clearing your quality bar rather than hard-wiring one vendor; and write the governance - agent permissions, approval gates, audit trails, data-access rules - into your own information-management plan, because the formal standards are lagging the technology by a year or more. The teams that win the next 12 months won't be the ones with the flashiest model; they'll be the ones who can show, on demand, exactly what their AI is allowed to do and prove what it did.