The agent is no longer the user
Professional infrastructure is mutating from "tools humans use" to "tools agents consume". Unity adopts MCP, video editors are designed agent-driveable, design systems are rewritten as machine context.
The thesis
This isn't AI adoption — it's control surface redesign.
Signals of the week
Unity MCP: the Editor is now controllable by LLMs
Unity released an MCP server that lets AI assistants control assets, scenes, and scripts directly from the editor. Joins VS Code, Cursor, and now game engines. MCP is becoming the standard protocol for making any professional tool agent-controllable — the "USB-C of AI tools". If your critical stack doesn't expose programmable primitives for agents, you're accumulating silent integration debt. Source: GitHub.
FableCut: video editor designed to be driven by agents
FableCut isn't "an editor that uses AI" — it's an editor that can be driveable by external agents, without dependencies. The "UI as API for agents" pattern is appearing across multiple verticals. The human interface was the constraint; now it's legacy. Whoever adopts this model first in their tool will have integration advantage when the market demands it — and it will demand it soon. Source: GitHub.
awesome-design-md: design systems as agent context
Design systems from popular brands are being rewritten as DESIGN.md files that coding agents read to generate UI automatically. The emerging pattern: design systems are designed for machines, not humans. Drop one in your repo and your agents already know which components to work with. Technical documentation is ceasing to be a human communication artifact to become an automation primitive. Source: GitHub.
My read
Anyone not exposing their stack as a programmable API for agents will have architectural debt in 18 months.
Useful? Forward it to someone it'd serve.
Subscribe— Jorel