15.1 Where MCP Is Heading

MCP (Model Context Protocol) began as a way to let an AI agent call an external tool. Sixteen months later, it has become infrastructure --- and the 2026-07-28 revision is the largest since the protocol launched in November 2024.

The MCP specification is stable at 2025-11-25, with the 2026-07-28 revision moving through release-candidate as of September 2026. It introduces four changes that matter for Open Design specifically.

Stateless HTTP. The current protocol requires session affinity --- a client and server must hold a persistent connection. The RC makes the core protocol stateless: clients cache the tools list, servers run behind ordinary HTTP load balancers. This means MCP can operate at cloud scale without custom session routing. For local-first use, it changes nothing. For the ecosystem, it removes the biggest adoption barrier for enterprise deployments. That matters to Open Design because it means the MCP surface that Open Design exposes will be reachable from more agents running in more environments.

MCP Apps. The RC adds a mechanism for servers to ship interactive HTML into sandboxed iframes with bidirectional JSON-RPC. In plain terms: an MCP server can now render a UI panel inside the agent's host application. This is structurally similar to what Open Design already does with its preview iframe --- the difference is that MCP Apps puts that capability in the protocol itself, so any MCP-compatible host can surface it without custom integration code.

Tasks. Long-running work moves to an independent extension. Generation runs in Open Design are already long-running; this extension standardizes how agents report progress and intermediate results across the ecosystem.

OAuth 2.0 / OIDC with Resource Indicators (RFC 8707). Standardized auth prevents token misuse across multi-server setups. This matters most in team and enterprise deployments of Open Design.

By March 2026, MCP hit 97 million monthly SDK downloads, up from approximately 2 million a year earlier. It is used across Claude Code, ChatGPT, Gemini, GitHub Copilot, and Cursor. The MCP Registry transferred to the Linux Foundation's Agentic AI Foundation on March 20, 2026. That governance structure --- an open foundation, vendor-neutral, with a chartered roadmap --- is the best available signal that MCP is infrastructure and not a vendor play.

15.2 The Agent and Model Trajectory

The agent market is in its most volatile phase. Between April and June 2026, a major model pricing cut and the sunset of an entire agent CLI happened within weeks of each other. That pace is the norm, not an anomaly.

The Consolidation Timeline

The clearest example of agent volatility is Gemini CLI. Google announced its sunset on the Google Developers Blog, with the service stopping for consumer tiers on June 18, 2026. According to multiple reports including The Register and the Google Developers Blog announcement, its announced replacement is Antigravity CLI, described in those reports as closed-source and Go-based, in contrast to Gemini CLI's open-source model. Multiple news sources and community discussions noted that this transition was announced without a prior open-source community consultation process. That is the documented cost of anchoring your workflow to a single vendor's CLI.

At the same time, OpenCode has emerged as the leading open-source alternative, reaching approximately 150,000 GitHub stars and a reported 6.5 million monthly active developers as of Q2 2026, per OpenCode's own published figures (opencode.ai). It is MIT-licensed, model-agnostic, and supports 75+ LLM providers. Those numbers will continue to grow; the point is not the count but what they signal: there is now a credible, community-owned option at the terminal-native tier.

The agent market had consolidated into five observable categories as of mid-2026 (a snapshot; section 15.7 shows what moved next):

Model Cost Trajectory

Between February 2026 and June 2026, Anthropic reduced Claude Opus 4.7 pricing from the previous Opus 4.1 rate of $15/$75 to $5/$25 per million tokens --- a reduction of approximately 67% in four months. As of June 2026, GPT-5.5 is reported at $5/$30 per million tokens, with a $0.50 cached-input option for repeated context. Small and medium models (Haiku-class, GPT mini, Gemini Flash) have seen even steeper reductions since 2023 --- one pricing tracker (morphllm.com) puts the cumulative drop at 99.7% from the 2023 baseline, though that figure is from a single source and should be treated as directionally correct rather than precise.

The practical implication: the cost barrier to running local-first agent workflows has collapsed. Design generation requires multiple model calls per artifact --- the initial generation pass, iteration rounds, export validation. At $5 per million input tokens, a complete generate-preview-iterate-export loop costs less than a cup of coffee. The durable layer --- DESIGN.md, the local daemon, the skill catalog --- becomes more valuable as the cost of running inference against it approaches zero.

There is also a second-order effect worth naming: as inference costs fall, the differentiator is no longer which model you use, but how well you have structured your design intent. A DESIGN.md that precisely encodes your brand's type ramp, spacing scale, and component rules will consistently produce better output than a vague prompt regardless of the underlying model. Cheap inference raises the relative value of good brand contracts.

Consolidation is not over. Cognition Labs acquired Windsurf (formerly Codeium's IDE) and relaunched it as Devin Desktop in 2026. Near-weekly Codex CLI releases mark OpenAI's terminal-native push. The five-category taxonomy above describes where things stand in June 2026, but it will likely need revision by end of year --- probably because one or more categories collapses through acquisition.

15.3 Design-as-Code Deepens

The DESIGN.md specification is the most consequential recent development for local-first autonomous design. Not because it is new --- Open Design has used design-as-code contracts since its first release --- but because Google open-sourced the specification on April 21, 2026, which means the format is now standardized, portable, and no longer tied to any one tool.

The DESIGN.md spec, published at github.com/google-labs-code/design.md as of April 21, 2026, defines a machine-readable brand contract structured around W3C Design Token Community Group (DTCG) format. Tokens export to tokens.json, tailwind.config.js, and design-system.css natively. The spec is documented as compatible with Claude Code, Cursor, OpenCode, and Google's own Stitch tool.

Within 10 days of the associated "awesome list" being published in March 2026, it reached 40,500+ GitHub stars --- among the fastest initial growth of any awesome list on record, according to one tracking source. That speed of adoption is a signal that the design-as-code model was already latent demand waiting for a portable specification to anchor it.

This matters for Open Design specifically because the DESIGN.md files in Open Design's bundled brand systems are now written against a portable, spec-compliant format. If Open Design ceased to exist tomorrow, every DESIGN.md in your project directory would still work with any agent CLI that implements the spec. The durable layer, volatile layer model is not a metaphor --- it is a practical portability guarantee.

15.4 Open-Source Community Dynamics

Open Design at 0.21.1, released August 31, 2026, carries 93.1K GitHub stars and 10.7K forks. Twelve releases in five weeks (mid-July through August 2026, on top of a steady spring cadence) point to a project in sustained acceleration --- and, notably, v1.0.0 has still not been claimed. The maintainers are shipping capability, not a stability declaration.

These counts age weekly and should not be treated as precise --- the point is the pattern. Weekly releases, consistent star growth, and a contributor base large enough that the project visibly outlives individual maintainers describe a project in active maintenance, not a project coasting on early momentum.

The Open Design Fellow program offers funded community engagement, including reported incentives for merged pull requests and LLM credits for contributors. The strategic intent is clear --- lower the barrier to building skills and plugins, so the catalog keeps growing without the core team having to own everything.

More broadly, the design tool market is unsettled. A 2026 Figma design trends report noted that nearly half of designers are still searching for their go-to stack, and the average toolstack has doubled to seven tools. Local-first autonomous design is one answer to that fragmentation, not the only one. The community dynamics of Open Design --- an Apache-2.0 license, a funded Fellow program, an active Discord, and a plugin ecosystem that grows with each release --- are a hedge against the project itself stalling. If the core team slows down, the plugin and skill contributors carry it forward. That is the structural advantage of an open-source project with a large enough contributor base, and it is one of the reasons I read the 7,000+ fork count as a signal of genuine community investment rather than passive curiosity.

15.5 My Bet on What Endures

Forward-looking chapters are cheaply written and expensively wrong. I will be specific about what I think is durable, what I think is volatile, and where I could be wrong on each.

The durable layer, volatile layer model is the mental model this chapter has used throughout, and it is also my actual operating framework. Here is how I apply it to a concrete investment decision.

The phrase to hold onto is durable layer, volatile layer. Build everything repeatable --- your brand contract, your skill library, your export workflows --- on the durable side. Treat agents, models, and pricing as infrastructure you rent, not infrastructure you own. That posture keeps you competitive regardless of which tool wins the next eighteen months.

15.6 What Shipped Since This Chapter's First Draft

This chapter was first drafted against Open Design v0.16.1 in June 2026. Ten weeks later, several of the trajectories named above stopped being trajectories. The scoreboard, as of August 2026:

The new trajectory was convergence with DeepSeek Harness --- and it converged. The daemon runtime definition that landed on the main branch on August 14, 2026 shipped the same day in 0.19.1 ("Design with DeepSeek Harness"): dsh became a first-class in-app agent, discovered like any CLI, with guided connection-profile setup, structured event streaming, and session resume across turns. 0.19.2 added one-command bootstrap scripts for macOS, Linux, PowerShell, and CMD, so the "imminent adapter" caveat this section carried for exactly one draft cycle is retired. Around it, watch the Vela/AMR centralization of hosted inference and media, Launch Week Vol.01 and the Feishu community joins pushing adoption well past the GitHub-star crowd, DeepSeek campaign pricing as a growth lever, and the retirement of the light-first theme setting --- every install has defaulted to light since 0.18.0.

Sort all of it with the durable layer, volatile layer model. Durable: DESIGN.md, your skills, the brand contracts --- everything above strengthened them. Shared toolkits make the contract a team artifact; workspace-scoped MCP operations make it addressable. Volatile: model tiers, adapter lists, campaign pricing --- the $5 seat fee, the two-week unlimited windows, and the Harness adapter's ship date will all have moved by the time you read this. Plan against the first list. Rent the second.

15.7 Three Signals in 0.21.1

Beyond the scoreboard, the 0.21.1 release --- "Community First: No Login Required," August 31, 2026 --- carries three signals about where local-first autonomous design goes next. None is a roadmap promise; all three are already running code, which in this project is the only kind of prediction that ages well.

Labs: a sanctioned place to be wrong

The new Open Design Labs settings page formalizes what fast-moving projects usually do informally. The copy is worth quoting in full, because it is a distribution strategy in three sentences: "Get early access to capabilities that have not shipped yet. They are usually better than what you have today, and turning one off restores the current behaviour right away." The first experiment, the Design Harness switch, sends your next generation through the project's latest generation strategy --- "noticeably more polished results (beta)" --- and the setting persists across restarts. For the local-first thesis this matters structurally: quality experimentation now happens on the client, behind a toggle the user controls, not behind an A/B test on a server you don't. Expect the durable-versus-volatile boundary to run straight through this page: Labs is where tomorrow's defaults get field-tested before they harden into the behavior of the stable 10-type creation list.

OD Next: artifact types get their own grammars

0.21.1 also shipped purpose-built structure for phone prototypes under the OD Next work: calendars, stats, settings rows, top bars, bottom navigation, images, confirmation dialogs --- each gets structure purpose-built for the phone rather than desktop patterns squeezed into a narrow viewport. Read it as a signal about generation strategy generally. The creation list stopped mutating at 0.20.0 (ten stable types, product-owned), and OD Next is the companion move: beneath a stable list of types, the per-type generation strategies keep specializing. The plausible 2027 trajectory is artifact-type-specific grammars --- deck grammars, dashboard grammars, phone grammars --- improving independently behind an unchanged composer. Your prompts and DESIGN.md survive that kind of change; agent-specific prompt tricks do not.

The community-first pivot as strategy

The no-login release is the most legible strategic document the project has published. When account sign-in became effectively required around 0.18.1 in early August, community pushback was immediate and sustained; three weeks later, 0.21.1 removed the requirement entirely --- pick a local CLI or BYOK and start, Cloud optional, sign-out preserves your local keys, URLs, and model choices. Combined with 93.1K stars, Powerformer Inc. as the company of record, and Launch Week marketing (five days, five design jobs, five tools "on the kill list"), the growth model is now explicit: maximize the top of the funnel at zero friction, monetize the Cloud lane and team seats above it, and let the local-first free tier be the moat. For the category, that validates the bet section 15.5 made: local-first control is the durable layer --- so durable that the space's dominant player now gives it away as customer acquisition.

Each signal has a failure mode worth watching. Labs experiments that never graduate would make the page a feature museum. OD Next structure that stops at phones would be a one-off, not a strategy. A quiet re-tightening of account requirements would reveal that the moat was pricing, not principle. Watch those three, and the 2027 version of this chapter largely writes itself.