Despite talk of its impending demise, the vibe coding craze appears to be alive and well, particularly in Europe.

A new study by vibe marketing website LeadsNavi analyzed Google search data to identify which countries are searching for vibe coding the most. The research examined both total annual search volume and searches per 100,000 residents, offering insight into where curiosity and adoption are most concentrated globally.

Developers and non-tech users alike are looking at new ways to code more intuitively and are researching vibe coding via search engines.

According to the study, interest in the concept of vibe coding is growing steadily worldwide, with Europe leading global interest.

“This rise in search activity reflects broader shifts toward creative coding, AI-assisted development, and more expressive programming workflows,” the study says.

Across both high- and low-ranking countries, common search phrases include “vibe coding,” “how to use vibe coding,” “vibe coding tools, “Claude code,” “lovable,” and “bolt”.

“This mix suggests many users are still learning the concept, while others are actively exploring how to implement it in real-world projects,” the study authors surmise.

Switzerland, Germany, Sweden, and Finland all rank in the top five countries most interested in vibe coding, with outlier Canada coming in third. The bottom five countries consisted of Italy, Spain, Hungary, Slovakia, and Czechia.

Brad Shimmin, an analyst at the Futurum Group, explains the breakdown to the The New Stack this way:

“My first impression is that these countries must surely participate heavily in the global software engineering market,” Shimmin says. “But interestingly, the usual hotspots in Eastern Europe — Poland and Ukraine — don’t appear to be on their list. That aside, I would say that these numbers favor countries with strong labor laws such as Germany, which may indicate that agentic code generation has a greater impact where perceived job security is at its highest level, comparatively.”

The top 5

Switzerland ranks first overall with 41.19 vibe coding searches per 100,000 residents.

“Despite a relatively small population, it shows the highest intensity of interest, suggesting a strong concentration of developers and tech professionals engaging with new programming approaches,” the study says of Switzerland.

Germany ranks second with 40.29 searches per 100,000 residents and a total of 33,700 searches, with common queries including “how to use vibe coding.”

As stated, Canada comes in third with 37.78 searches per 100,000 residents. Canada’s searches appear to be more application-focused, the study shows. There was strong interest in “vibe coding tools,” suggesting users may already understand the concept and are looking to apply it.

Sweden and Finland rank fourth and fifth place, with 35.04 and 34.69 searches per 100,000 residents, respectively. This reinforces Northern Europe’s reputation for early adoption of developer-led trends and experimental coding practices, the study says.

The next five

Malta ranks sixth with just 190 total searches but a high per-capita figure of 34.61. France ranks seventh, with per-capita interest at 33.53 searches per 100,000 residents. Denmark and Luxembourg rank eighth and ninth, with 32.71 and 32.00 searches per 100,000 residents.

Meanwhile, Australia rounds out the top 10 with 31.22 searches per 100,000 residents, which makes it the highest-ranking country outside Europe and the strongest performer in the Asia-Pacific region, the study said.

Asia and the US

The study did not include Asian countries. “As the data were based on Google search volumes, we chose not to include Asian countries, as Google is not the primary search engine in many of those markets,” a spokesperson for LeadsNavi tells The New Stack.

Interestingly, the United States ranks 15th with 26.78 searches, just behind the United Kingdom at 26.93 and ahead of New Zealand at 25.53. This may indicate that the US is further advanced with vibe coding or is losing interest.

“From our data, it is US leading clearly – both from end users and SI engagement doing work for customers, and customers asking for it,” Holger Mueller, an analyst at Constellation Research, tells The New Stack.

Overall, the findings show that interest in vibe coding is strongest in smaller, highly tech-literate countries, particularly in Northern and Central Europe.

The Bottom Five

Regarding the bottom five, Czechia and Slovakia rank 20^th and 21^st with 18.90 and 16.69 searches per 100,000 residents, respectively. Italy places 22nd overall with 14.00 searches per 100,000 residents. Spain and Hungary tie for last with each recording 13.98 searches per 100,000 residents, despite both countries having active tech sectors.

Full list of countries using vibe coding the most:

Image by LeadsNavi

To identify which countries are searching for “vibe coding” most, the study analyzed Google search data for “vibe coding” and related queries. The study combined total annual search volumes with population data to calculate searches per 100,000 residents.

Countries were ranked based on per-capita search intensity, with total search volume included for context.

The post Where on Earth is vibe coding taking off the most? appeared first on The New Stack.

At Microsoft we believe that intelligence and trust are the core requirements of agentic AI at scale. Built on Azure, Microsoft Foundry brings these capabilities together on a secure, scalable cloud foundation for enterprise AI. Today, with the launch of Claude Opus 4.6 in Microsoft Foundry, we bring even more capability to agents that increasingly learn from and act on business systems.

Claude Opus 4.6 brings Anthropic’s most advanced reasoning capabilities into Microsoft Foundry, our interoperable platform where intelligence and trust come together to enable autonomous work. In Foundry, Opus 4.6 can activate knowledge from everywhere: leveraging Foundry IQ to access data from M365 Work IQ, Fabric IQ, and the web. The model is best applied to complex tasks across coding, knowledge work, and agent-driven workflows, supporting deeper reasoning while offering superior instruction following for reliability.

Developers can now delegate their most complex work to AI systems for full-lifecycle development from, requirements gathering to implementation and maintenance. Business users can generate documents, perform research, and draft copy with professional polish and domain awareness.

At Adobe, we’re continuously evaluating new AI capabilities that can help us deliver more powerful, responsible, and intuitive experiences for our customers. We’ve been testing Claude models in Microsoft Foundry and are excited about the direction of Anthropic’s model roadmap. Foundry gives us a flexible, enterprise-ready environment to explore frontier models while maintaining the trust, governance, and scale that are critical for Adobe.

—Michael Marth, VP Engineering for Experience Manager and LLM Optimizer, Adobe

Introducing Opus 4.6: Frontier intelligence, built for real work

Claude Opus 4.6 is the latest version of Anthropic’s most intelligent model, and is considered the best Opus model for coding, enterprise agents, and professional work. With a 1M token context window (beta) and 128K max output, Opus 4.6 is ideal for:

• Production code
• Sophisticated agents
• Office tasks
• Financial analysis
• Cybersecurity
• Computer use

By combining Anthropic’s most advanced model with Foundry’s end-to-end tooling, customers can move from experimentation to production faster, without stitching together infrastructure.

1. Autonomous coding at a new level

Opus 4.6 handles large codebases well and is particularly effective at long-running tasks like refactoring, bug detection, and complex implementations.

This allows senior engineers to delegate work that previously took days, covering everything from requirements gathering to implementation and maintenance, while staying focused on reviews and decision-making.

With Foundry’s managed infrastructure and operational controls, teams can compress development timelines from days into hours, while maintaining the rigor required for real-world production systems.

Macroscope has relied on Anthropic’s frontier models to push what’s possible in AI code review, helping us catch the bugs that matter most to customers before they ever reach production. We’re incredibly excited to deepen this partnership by scaling on Azure infrastructure and delivering our product to teams around the world.

—Kayvon Beykpour, CEO & Co-Founder, Macroscope

2. Better knowledge work across the enterprise

Opus 4.6 delivers a step-change in how enterprises approach knowledge work, which Anthropic defines across three pillars: search, analyze, and create. In Microsoft Foundry, these capabilities can be applied directly to enterprise data, workflows, and agent-driven applications.

Opus 4.6 understands the conventions and norms of professional domains, producing documents, spreadsheets, and presentations that look and read like expert-created work. Combined with Foundry’s governance and access controls, this makes Opus 4.6 a great fit for finance, legal, and other precision-critical industries where quality, context, and compliance matter.

At Dentons, we are scaling generative AI across drafting, review, and research workflows across our global teams. Claude in Microsoft Foundry brings the frontier reasoning strength we need for legal work, backed by the governance and operational controls required in an enterprise environment. Better model reasoning reduces rework and improves consistency, so our lawyers can focus on higher value judgment.

—Matej Jambrich, CTO, Dentons Europe

High context financial analysis

Opus 4.6 excels at connecting insights across regulatory filings, market reports, and internal enterprise data, surfacing conclusions that would traditionally take analysts days to compile.

Its advanced reasoning capabilities allow it to:

• Navigate nuanced financial and regulatory contexts
• Generate compliance-sensitive outputs
• Maintain consistency and traceability across complex analytical workflows

When deployed through Microsoft Foundry, these workflows benefit from Azure’s security, compliance, and auditability, helping organizations apply frontier AI to high-stakes analysis with confidence.

3. Advancing agentic and computer use capabilities

According to Anthropic, Opus 4.6 delivers major gains in computer use, with strong performance on industry benchmarks for visual understanding and multi-step navigation. Opus 4.6 sets a new standard for computer use. Claude can now operate computers more accurately, handle more complex tasks, and work across multiple applications seamlessly.

It can interact with software, navigate interfaces, complete forms, and move data across applications. When deployed in Microsoft Foundry, these actions can run as secure, governed agents, enabling automation of workflows that span legacy systems, document processing, and operational tools.

Opus 4.6 can manage complex, multi-tool workflows with less oversight—an essential requirement for teams operating AI systems at scale.

Anthropic on Azure provides Momentic with the reliability guarantees needed to process millions of tokens per hour on state-of-the-art models like Opus 4.5. Azure’s platform works seamlessly with Anthropic’s SDK, even supporting beta features such as reasoning effort out of the box.

—Jeff Ann, CTO & Co-Founder, Momentic AI

4. Agents, security, and high-stakes reasoning

Opus 4.6 is also best suited for agentic workflows, reliably orchestrating complex tasks across dozens of tools. It can proactively spin up sub-agents, parallelize work, and drive tasks forward with minimal oversight.

For security workflows, Opus 4.6 delivers deep reasoning, enabling teams to identify subtle patterns and complex attack vectors with high accuracy.

Anthropic is a trusted partner for governments and companies alike. Their speed, accuracy, and toolkit are already helping Everstar make fast, safe nuclear energy deployments a reality. I’m excited to see these capabilities integrated natively on Azure for secure deployments for our government and nuclear customers.

—Kevin Kong, Founder & CEO, Everstar

New API capabilities co-launching with Opus 4.6

Alongside Opus 4.6, Anthropic is introducing new API capabilities, available through Microsoft Foundry—that give developers greater control, scalability, and efficiency:

• Adaptive thinking: Allows Claude to dynamically decide when and how much reasoning is required, optimizing performance and speed on simpler tasks, while allowing Claude to think harder on complex tasks.
• Context Compaction (beta): Supports long-running conversations and agentic workflows by summarizing older context as token limits are reached.
• 1M Context Window (beta): Support for up to 1M tokens, with premium pricing applied beyond 200K tokens.
• Max effort control: A new max effort level joins high, medium, and low, offering finer control over token allocation across thinking, tools, and output.
• 128K Output Tokens: Enables richer, more comprehensive outputs in a single response.

Claude Opus 4.6 in Microsoft Foundry

As AI systems move from assistance to autonomy, success depends on more than frontier intelligence, it requires intelligence that can be trusted to operate in real-world environments. Claude Opus 4.6 brings advanced reasoning and long-horizon execution, and Microsoft Foundry provides the system context where that intelligence can be applied responsibly, at scale.

Together, Claude in Foundry enables organizations to move beyond isolated experiments and toward intelligent, agent-driven systems that deliver real business impact—grounded in trust, governance, and operational rigor.

The post Claude Opus 4.6: Anthropic’s powerful model for coding, agents, and enterprise workflows is now available in Microsoft Foundry on Azure appeared first on Microsoft Azure Blog.

Managing the number of posts that show up on your blog page gives you more control over how visitors experience your site. Instead of being locked into the default settings, you can decide whether you want a shorter feed that highlights your latest updates or a longer list that encourages browsing.

In this guide, you’ll learn the different ways to change the number of posts displayed on your blog page, how those changes affect your site, and what you should consider before making adjustments. Whether you’re using the default settings, a plugin, or a custom theme, we’ll walk you through the options, step by step.

How WordPress decides the number of posts to show

When you install WordPress, the system is set to show ten posts on your blog page by default. A setting in your WordPress dashboard controls the number of posts that appear on your main blog page, category pages, tag pages, and other archive-style templates across your site.

If you haven’t changed this yet, the default number that you see is ten.

Method 1: Change the number of posts via WordPress settings

This is the most common and user-friendly method. It works for most WordPress themes and takes less than a minute.

To do this, log into your WordPress dashboard, then look for Settings on the left-hand side. Then, click Reading.

Look on the page for the setting that reads “Blog pages show at most” and input the number of posts you want to display.

Lastly, scroll down and click Save Changes. 

That’s it. Your blog page will now show the number of posts you set.

Method 2: Adjust post count in a custom loop (for developers)

If your site uses a custom theme or template that doesn’t rely on the default WordPress settings, the number of posts shown may be controlled directly in the code. This usually applies when the blog page is created with a custom query or template rather than the standards options under Settings → Reading.

If you’re comfortable editing PHP files, look for the file handling the blog index. This might be home.php, index.php, or a custom template file.

Look for a query that defines the number of posts. You’ll often see something like this:

$args = array(
    'post_type' => 'post',
    'posts_per_page' => 10,
);
$query = new WP_Query($args);
To change the number of posts, adjust the posts_per_page value:
'posts_per_page' => 5,

Before you start making changes to code, though, be sure to use a child theme if you’re editing theme files. This way, your changes won’t get lost during updates. Also, back up your site before editing any code.

Once you’re done making edits, clear or refresh your cache to see the updated post count.

Method 3: Use a plugin for more control

If you want more flexibility without editing code, a plugin can provide finer control over how many posts display across different parts of your site. Some plugins let you set unique post counts for the blog index, category archives, search results, or even custom taxonomies.

Here are two useful plugins worth considering: 

• Advanced Post Block: This plugin lets you design custom post grids and lists with options for how many posts to display per block. It’s a useful choice if you want different counts on different pages.
• TaxoPress: Use this plugin to manage categories, tags, and taxonomies. It also includes settings for how content is displayed, like how many posts appear in archives.

Once installed, these plugins usually add new settings panels or block options where you can choose how many posts to show in specific contexts.

Method 4: Change posts per page with the REST API 

This is a more advanced option, but if you have the development skills, it’s worth looking into. If you’re building a headless WordPress site or working with the REST API, you can control how many posts are returned by using the per_page parameter in your requests.

Here’s an example request:

https://yoursite.com/wp-json/wp/v2/posts?per_page=5

This code snippet will return five posts per page. By default, WordPress allows up to 100 posts per page. If you need more, the server or theme can raise this limit, but most setups keep 100 as the maximum for performance reasons.

This method is mainly useful if you’re:

• Fetching posts for a custom JavaScript front end, like React, Vue, or Next.js.
• Integrating WordPress content into a mobile app.
• Working with external applications that pull in your site’s posts.

Things to consider before changing post counts

Changing the number of posts that display on a page affects the look of your blog and influences site performance, user experience, and even how search engines crawl the content. It’s worth thinking through these factors before settling on a number.

Impact on performance

Showing more posts per page means that your site has to load more images, scripts, and layout elements at once. That can slow down page speed, especially on mobile devices or slower connections. That being said, showing fewer posts per page can speed up load time, which improves performance but may increase the number of requests if visitors need to click through multiple pages. 

Impact on user experience

A very long page with dozens of posts feels overwhelming and much harder to scan. Visitors may give up before finding the content they want. In contrast, too few posts per page frustrates readers if they have to keep clicking “Next.” 

The ideal number depends on your content style and audience. A photography blog might be better with fewer posts per page, while a text-heavy blog could comfortably show more. Test different post counts to find what works best for your audience.

What about pagination?

When you change the number of posts per page, WordPress automatically updates the pagination to match.

For example, if you have 30 posts and you set the display count to five, your blog page will show six pages. If it was set to ten posts per page, you’d only see three pages.

Customize how pagination looks and functions with plugins like WP-PageNavi or themes with built-in pagination styles.

Troubleshooting common issues

If the number of posts doesn’t update the way you expect, don’t worry: it usually comes down to caching or overrides. Start by clearing your browser cache and, if you’re using a caching plugin like WP Super Cache, clear that as well. 

If the problem persists, your theme or page builder may be overriding the global settings. Developers sometimes use the pre_get_posts function or custom loops in theme files to control post output. In other cases, a plugin may be forcing its own post count. Try disabling plugins one at a time to see if one of them is the culprit.

Speed up your content process with Jetpack AI Assistant

Adjusting the number of posts that show on your blog page can shape performance and how visitors interact with your content. Once you’ve found a layout that feels right, the next step involves keeping your site fresh with consistent updates.

That’s where Jetpack AI Assistant can really help. Built directly into the WordPress editor, Jetpack AI Assistant helps you:

• Write new blog posts and pages from scratch using clear prompts
• Rewrite or shorten content to match your style and tone
• Create quick headlines, calls to action, or meta descriptions
• Translate your posts into multiple languages without extra tools
• Get real-time content suggestions without ever leaving your dashboard

It’s simple to use. Just type a prompt or ask a question in the block editor, and the AI Assistant responds in seconds. It helps you go from idea to draft much faster than writing everything on your own. Use it as often as you like while keeping full control over the final result.

To try it out, just make sure Jetpack is installed and activated, then look for the Jetpack AI block in your block editor. It works smoothly with your existing workflow and requires no setup.

In today’s globally connected environment, even minutes of downtime can disrupt supply chains, hinder customer experiences, and affect regulatory commitments costing organizations thousands of dollars per minute and risking lasting reputational harm. Data resiliency is no longer optional—it is the foundation that keeps mission‑critical applications running, teams productive, and compliance intact. Organizations must ensure continuous data availability and zero data loss to meet stringent regulatory and audit standards.

Azure NetApp Files (ANF) is an Azure first party, enterprise-grade file storage offering in the cloud built to deliver unmatched performance, security with instant provisioning, and enterprise data management capabilities like snapshots, replication, backups, and flexible, cost-efficient service levels. It’s the trusted platform for critical workloads and the engine behind numerous migrations that drive Azure enterprise cloud journeys.

As businesses scale, the impact of service disruptions grows, and storage platforms must evolve to help maintain operational continuity. To support these needs, we are introducing Azure NetApp Files Elastic zone‑redundant storage (ANF Elastic ZRS)—a new service that provides enhanced resiliency across availability zones (AZs) and advanced data management capabilities. Built on Azure infrastructure, ANF Elastic ZRS can be deployed rapidly, accelerating availability across a broad set of regions. As a customer, you benefit from a service that can quickly adapt, whether that means expanding to a new Azure region you require, or adopting new technological advancements faster.

Synchronous replication and service managed failover

Built on Microsoft Azure’s zone-redundant storage (ZRS) architecture, ANF Elastic ZRS synchronously replicates data across multiple AZs within a region.

The graphic below shows the high-level architecture of ANF Elastic ZRS.

The following summarizes the operational methodology used: 

• Synchronous replication: ANF Elastic zone-redundant storage (ZRS) volume replicates data within your NetApp Elastic Account to three or more AZs within the primary region of choice.
• Service managed failover: If one AZ goes down (think single datacenter failure, power outage), ANF Elastic ZRS automatically routes traffic to the failover zone that was chosen during initial setup without customer intervention. The mount target and service endpoint remain the same, so your applications barely notice.
• Zero data loss and high availability for mission-critical applications: ANF Elastic ZRS ensures uninterrupted operations for mission-critical applications and regulated systems by combining synchronous replication with service-managed failover. This architecture guarantees zero data loss and seamless continuity even during zone-level failures, meeting enterprise resiliency standards.

Capabilities for enterprise mission-critical applications

• NFS, SMB protocol support, multi-AZ file service: ANF Elastic ZRS supports NFS and SMB independently with the added benefit of zonal redundancy.
• Rich enterprise data management capabilities: Instant writeable space-efficient snapshots, clones, tiering, and backup integration all powered by the NetApp ONTAP® Unified data management platform.
• Metadata performance: Beyond consistent throughput, ANF Elastic ZRS provides efficient handling of metadata operations such as rapid file creation and fast enumeration of numerous small files, improving responsiveness of metadata-heavy workloads. Its shared QoS architecture dynamically allocates IOPS across volumes to maintain low-latency, metadata-intensive operations consistently.
• Cost optimized: ANF Elastic ZRS delivers multi-AZ high availability in a single volume at a lower cost than cross-zone replication with three separate ANF volumes, making it an efficient and valuable investment. You can create volumes as small as 1 GiB, giving you the flexibility to optimize storage for workloads of any size.

Apart from the above capabilities that are already supported, we will be adding the below capabilities in the future:

• Simultaneous multi-protocol, multi-AZ file service: The service will support simultaneous NFS, SMB, and Object REST API access to the same dataset. This flexibility is crucial for environments where Windows and Linux workloads share data, such as analytics platforms and enterprise file shares.
• Custom region pair for cross-region replication: ANF Elastic ZRS will be offering the flexibility to choose custom region pairs for cross-region replication, meeting strict compliance and disaster recovery requirements for large enterprise customers. This capability ensures business continuity while aligning with unique geographic or regulatory needs.
• Migration Assistant: This capability will simplify data movement from on-premises or other ONTAP® systems to Elastic ZRS service level for seamless cloud adoption.

Targeted use cases

Innovation in action

A global healthcare enterprise running mission-critical application, on-premises is looking to modernize its infrastructure by moving mission-critical workloads to the cloud. The organization’s top priorities are eliminating downtime during maintenance and ensuring seamless failover to maintain application availability.

By adopting ANF Elastic ZRS, the organization gained a fully managed, zone-resilient storage solution that synchronously replicates data across three Azure AZs. This ensures zero data loss and near-instant failover, even during zone outages or platform maintenance. The mission-critical application remains highly available without requiring operational intervention, dramatically improving uptime, and simplifying infrastructure management.

ANF Elastic ZRS delivers the same enterprise-grade features as existing Azure NetApp Files service levels—such as NFS/SMB support, snapshots, encryption, and backup—all while removing the complexity of managing high availability (HA) clusters or VM-level failover. For the healthcare provider, this translates into higher SLA compliance, reduced operational overhead, and a more resilient foundation for its mission-critical application landscape.

Take the next step toward resilient storage

NetApp on premises customers: this is the inflection point you’ve been waiting for to move to Azure. ANF Elastic ZRS‑ brings the ONTAP®-powered data management you trust to a fully managed, multi-AZ file service, so you can modernize mission‑AZ file service, so you can modernize mission‑critical workloads with enterprise resilience, meet availability commitments, and reduce operational overhead—without re‑architecting your applications.

ANF Elastic ZRS is available now in these Azure regions and we will be rapidly expanding region availability.

Learn more:

• Understand Azure NetApp Files Elastic zone-redundant storage
• Create an SMB volume for Azure NetApp Files
• Create an NFS volume for Azure NetApp Files
• Comparison of Elastic vs other ANF service levels

The post Enhanced storage resiliency with Azure NetApp Files Elastic zone-redundant service  appeared first on Microsoft Azure Blog.

AI-Native Dev Loops

Anthropic shipped Claude Opus 4.6 today. It tops the agentic coding benchmarks, has a 1M token context window, and claims to “plan more carefully” and “sustain agentic tasks for longer.”

We didn’t write a reaction post. We ran it.

The setup

We’ve been building cross-platform .NET apps with Claude Code and Uno Platform’s MCP tools for months. When a new model drops, we have a simple protocol: same task, same tooling, new model. Compare the results.

The task: build a Daily Inspiration quote app with MVUX state management, region-based navigation, and persistent storage. It’s a small app, but it touches everything that matters – reactive data binding, cross-platform file I/O, Material Design styling, and multi-target builds.

We built this same app with Sonnet a few weeks ago. We have a detailed iteration report documenting exactly what happened.

Today, we gave the same spec to Opus 4.6.

What Sonnet did

Sonnet completed the app. It works. But the path there was rough.

It took roughly 115 minutes and hit three significant detours:

The Card control trap. Sonnet used utu:Card from the Uno Toolkit for the quote display. The Card rendered empty. Visual tree showed elements present, DataContext confirmed data was loaded, but nothing appeared on screen. Sonnet spent roughly 30 minutes debugging this – inspecting the visual tree, checking data context, swapping templates – before discovering it was a rendering issue with the Card control itself. The fix was replacing Card with a plain Border.

The FeedView confusion. MVUX uses IState<T> for reactive state. But you can’t bind directly to it in XAML – you need to wrap it in <mvux:FeedView> and access data through a Data property. Sonnet tried {Binding CurrentQuote.Text} first. That doesn’t work. It had to search the docs, find the correct pattern, and refactor.

The style workaround. After the Card control issues, Sonnet gave up on Material text styles entirely and hardcoded FontSize="24", FontSize="16", etc. It worked, but it’s not how you ship a Material Design app.

The final app also had leftover template pages (MainPage, SecondPage) that were never cleaned up.

What Opus 4.6 did

Same spec. Same Uno Platform MCP tools. Same project template.

Both targets built on the first try. Zero warnings, zero errors. Desktop in 52 seconds, WebAssembly in 2 minutes 24 seconds.

No Card control trap. Opus 4.6 used Border with ThemeShadow for elevation from the start – it appears to have known that the Card control can be problematic in certain configurations and chose the reliable primitive with proper shadow support instead.

No FeedView confusion. The correct MVUX binding pattern appeared in the first version of the XAML:

XAML Copy

<mvux:FeedView Source="{Binding CurrentQuote}">
    <DataTemplate>
        <TextBlock Text="{Binding Data.Text}"
                   Style="{StaticResource TitleLarge}" />
    </DataTemplate>
</mvux:FeedView>

• No hardcoded font sizes.
• Proper Material text styles throughout TitleLarge, BodyLarge, BodyMedium – the way the design system is meant to be used.
• Clean project structure.
• Template files removed.
• Routes registered correctly.
• No dead code.

 

The whole thing took about 15 minutes from scaffold to running app.

What actually changed

Anthropic says Opus 4.6 “plans more carefully.” In practice, what we observed is that it made better architectural decisions upfront. It chose Border over Card not because someone told it to, but because it appears to understand which controls are reliable for content display versus which ones carry styling complexity. It used FeedView correctly because it understood the MVUX data flow pattern before writing the first line of XAML.

This matters for .NET developers because cross-platform UI frameworks have a lot of surface area. There are many ways to build the same screen. The difference between a model that picks the right abstraction on the first try and one that picks wrong and debugs for 30 minutes is significant when you’re iterating on real applications.

The 1M token context window is relevant here too. Our MCP tools send documentation, project structure, and runtime diagnostics back to the model. A larger context window means the model can hold more of the framework’s patterns in working memory while writing code. That translates directly to fewer wrong turns.

The tooling angle

Model upgrades only translate to better output when the tooling layer is solid. Claude Code with Uno Platform’s MCP tools provides:

• Documentation search and retrieval – the model can look up FeedView binding patterns, navigation APIs, and control usage before writing code
• Build verification – dotnet build results feed back into the model’s decision loop
• Project scaffolding – dotnet new unoapp with the recommended preset gives the model a correct starting point

The model got smarter. The tooling stayed the same. The combination produced a meaningfully better result.

The numbers

Metric	Sonnet 4.5	Opus 4.6
Time to working app	~115 min	~15 min
Build failures before success	Multiple	0
Card control debugging	~30 min	Avoided
MVUX pattern correct on first try	No	Yes
Material styles used correctly	No (hardcoded)	Yes
Template cleanup	No	Yes
Desktop build warnings	0 (after fixes)	0
WASM build warnings	0 (after fixes)	0

Try it yourself

The Uno Platform MCP tools work with Claude Code today. If you’re a .NET developer building cross-platform apps, the Opus 4.6 upgrade is meaningful – not because of benchmarks, but because it writes better code on the first pass.

• Claude Opus 4.6 announcement
• Get started with Claude Code and Uno Platform
• MVUX overview

The post Claude Opus 4.6 Just Shipped. We Had It Build a Cross-Platform .NET App appeared first on Uno Platform.