ANALYSIS Across design tools, IDEs, and low-code platforms, a structural shift is underway: development environments are no longer optimizing for human keystrokes alone but rebuilding their core abstractions so AI coding agents can operate as first-class participants, governed by the platform rather than bolted on after the fact.
Why it matters
The moves by Figma, OutSystems, Microsoft's VS Code, and Google's Android Studio in rapid succession mark a transition from "AI-assisted" to "agent-native" development. ◆ The competitive question for platform vendors is no longer whether to support AI agents but how tightly to constrain them, and the divergent answers reveal fundamentally different bets on where value accrues in an agent-saturated toolchain.
The big picture
Figma, at its first Config event in India, introduced Figma Specs, a Markdown-based editor that lets teams define their design language so that both human designers and AI agents can reference it while working on the canvas2. The company also shipped code layers in open beta, allowing teams to build, edit, and compare code-backed prototypes directly inside Figma's design environment1,6. It expanded its Model Context Protocol ecosystem with 20 new partners, including Sarvam AI, Grok Bot, and Open Code. "The next evolution is a full-stack creative canvas where teams and agents can build together, from idea to ship, in a visual-first way," said Dylan Field, co-founder and CEO of Figma.
OutSystems took a governance-first approach, making its Agent Experience generally available at OutSystems World Tour Las Vegas9. The product opens the OutSystems platform to external AI coding agents including Claude Code, Cursor, Codex, and Kiro7,10. Rather than letting agents generate standalone code, Agent Experience lets them shape application architecture while OutSystems handles actual code generation deterministically8. The company cited developer survey data indicating that 74 percent of AI-generated code requires significant rework after generation or is never deployed to production at all. Agent Experience supports public cloud, private cloud, on-premise, and hybrid deployments.
Microsoft's VS Code 1.140, released as a stable update on September 30, 2026, added experimental multi-folder agent sessions across repositories, a Copilot harness for consistent agent behavior across VS Code, the GitHub Copilot app, and Copilot CLI, and a research preview called HydraFusion that can choose between single-model, cascade, and critique workflows for coding tasks14. Google's Android Studio introduced a Bring Your Own Agent feature, letting developers integrate their preferred coding agent, with named support for Claude Agent, Codex, and Google's Antigravity15.
ANALYSIS Figma's approach and OutSystems' approach sit at opposite ends of a spectrum that defines the emerging agent-platform relationship. Figma is building a shared canvas where agents and humans collaborate visually, with Figma Specs serving as a natural-language contract that steers non-deterministic AI toward predictable design outcomes. TechCrunch noted that "given the non-deterministic nature of AI, the company is providing tools to steer it toward more predictable outcomes". OutSystems, by contrast, treats the agent as an architect whose decisions are then compiled deterministically by the platform itself, removing the agent from the code-generation step entirely.
The common thread is that every platform is inserting a governance layer between the agent and production output. VS Code's Copilot harness standardizes agent behavior across surfaces. Android Studio's BYOA feature pairs external agents with Android Studio's "AI-optimized infrastructure and tool support". OutSystems enforces security, automated testing, and governance guardrails without requiring manual configuration. The platforms are competing not on which model they host but on how reliably they can translate agent intent into shippable artifacts.
Real-world adoption data from OutSystems sharpens the stakes. YESCO compressed its software release cycles to two weeks while maintaining quality and compliance standards using Agent Experience with Claude Code. Lowenstein Sandler built a production-ready Litigation Matter Tracker in under three hours.
ANALYSIS The simultaneous moves by four major platforms suggest that agent-native architecture is becoming table stakes rather than a differentiator. The next competitive front is likely interoperability: Figma's 20-partner MCP expansion and Android Studio's explicit multi-agent support point toward an environment where agents roam across platforms. OutSystems CEO Woodson Martin framed the value proposition as giving "AI leaders the speed of coding agents with compliance, security, and scalability for mission-critical systems". Whether governed determinism or collaborative canvas wins the most developer hours will shape which platforms capture the agent-era workflow.