Compose Multiplatform 1.12.0 Released

Summary

JetBrains has announced the release of Compose Multiplatform 1.12.0 with targeted capabilities for artificial intelligence integrations, web rendering, and desktop application layouts. The update incorporates an experimental Model Context Protocol server inside Compose Hot Reload, allowing AI agents to trigger reloads, capture screenshots, inspect the semantic tree, and simulate user interactions directly. For web deployments, the framework now provides automatic font fallback by downloading necessary Noto font subsets on demand when unresolved characters occur during rendering. Desktop developers receive an experimental v2 window and dialog application programming interface in the androidx.compose.ui.window.v2 package, which distinguishes requested states from actual window states and permits precise control over positioning, sizing constraints, and multi-screen placement. These combined enhancements improve developer workflows and runtime flexibility across multiple target platforms.

Context

Compose Multiplatform needed better developer tooling for AI coding assistants, simplified international font management on the web without bundling large font files, and finer control over desktop window positioning and sizing states.

Approach / What changed

JetBrains added an experimental Model Context Protocol server to Compose Hot Reload, implemented on-demand Noto font downloading for web font fallback, and created an experimental v2 WindowState and DialogState API in androidx.compose.ui.window.v2 for desktop.

Takeaways

• The experimental Model Context Protocol server lets AI agents verify their code changes by triggering reloads, reading logs, inspecting semantic trees, and simulating inputs.
• Automatic web font fallback dynamically downloads matching Noto font subsets upon encountering unresolved characters, enabling scripts like Japanese, Arabic, and Devanagari to render without local bundling.
• The desktop v2 window API explicitly separates requested window states from actual current states while supporting custom sizing providers and parent-relative dialog positioning.

Related reading

• Jetbrains · Aug 26, 2026

  OpenTelemetry Comes to IntelliJ IDEA, GoLand, PyCharm, and WebStorm

  With the 2026.2 release, JetBrains expanded its OpenTelemetry plugin from Rider to IntelliJ IDEA, GoLand, PyCharm, and WebStorm. The tool captures logs, metrics, traces, and service maps locally without requiring an external observability backend. Developers can search structured log records, plot metric values over time, inspect distributed spans, and verify communication paths across databases and message queues during local runs. To ingest telemetry, the plugin automatically configures OpenTelemetry Protocol environment variables for supported run configurations and terminal sessions, or accepts forwarded data from existing collectors. Additionally, experimental Model Context Protocol support allows AI coding agents to query gathered logs, spans, and service topology.

  Egor Klimov

• Cloudflare · Aug 6, 2026

  The next generation of MCP

  Model Context Protocol previously required stateful connections between clients and remote servers, creating operational complexity around sticky sessions, message replay, and open streams. The newly released MCP 2026-07-28 specification transitions MCP to a fully stateless protocol alongside updated SDKs across TypeScript, Python, Go, and C#. The protocol eliminates mandatory handshakes and session identifiers from core request paths while enabling servers to run on request-scoped infrastructure like Cloudflare Workers. Interactive elicitation is restructured through Multi Round-Trip Requests, which allow servers to return input requirements without sustaining persistent connections. Standardized headers for method names and improved OAuth authorization mechanisms further enable standard web infrastructure to inspect and manage MCP traffic efficiently.

  Matt Carey

• Salesforce · Aug 24, 2026

  From Prediction to Action: How to Turn AI Outputs Into Decisions

  Salesforce addressed an operational challenge where sellers faced roughly 12,000 dashboards and over 20 applications outputting machine learning predictions without clear next steps. The engineering team reframed machine learning outputs as raw signals rather than standalone answers. To bridge the gap between assessment and action, they built a Next Best Action layer that combines model signals, business logic, and contextual institutional knowledge into actionable recommendations. They integrated this layer with an AI agent using Model Context Protocol (MCP) tool contracts, enabling dynamic discovery and explicit handling of missing data. Finally, rather than introducing a separate dashboard destination, the agent serves on-demand recommendations directly inside Slack where sellers already collaborate.

  Scott Nyberg

• Cloudflare · Aug 24, 2026

  The Cloudflare Blog – Brought to you by EmDash

  Cloudflare migrated its official blog to EmDash, an Astro-focused content management system, acting as internal Customer Zero to evaluate scaling and usability. To prepare for traffic spikes reaching thousands of requests per second, engineers used k6 to execute ramp, breakpoint, and burst load tests. The resulting production architecture runs EmDash on Cloudflare Workers, pairing it with Workers Cache, an object cache backed by Workers KV, and Hyperdrive connected to PlanetScale. This layered caching design serves 99.5 percent of static files and 70 percent of requests from cache, flattening p95 latency under real-world loads reaching 850 requests per second. The migration also introduced a frontend redesign using the Kumo design system and added Model Context Protocol servers for automated agent workflows.

  Kody Jackson