What’s New in Infragistics Ultimate 26.1

Name: What's New in Infragistics Ultimate 26.1: AI-Powered Development with Ignite UI CLI
Uploaded: 2026-06-17
Duration: 48 min 24 s
Description: Webinar walkthrough of the Ignite UI CLI MCP server, AI-configured project scaffolds, the Generate-from-Image workflow, and the Ignite UI for Angular 21.2 updates.

Infragistics Ultimate 26.1 ships a complete AI toolchain - Agent Skills, the Ignite UI CLI MCP server, and the Theming MCP server - across Angular, React, Web Components, and Blazor. The release also introduces Grid Lite, a free MIT-licensed open-source data grid, grid scroll performance gains of up to 150% FPS at 100k rows, PDF export for every grid family, a new Intl-based i18n engine, and new components including IgbQueryBuilder.

Radoslav Mirchev Last Updated Jun 17, 2026 15 min read

Infragistics Ultimate 26.1 has one organizing idea: the same AI-assisted development toolchain, working the same way, across every modern Ignite UI framework. Agent Skills, the Ignite UI CLI MCP server, and the Theming MCP server now cover Angular, React, Web Components, and Blazor – set up with a single command, and built to keep the four frameworks at parity rather than treating any one as a second-class target.

Around that toolchain, the H1 2026 cycle also delivers Grid Lite (a new free, MIT-licensed data grid), grid scroll-performance work, PDF export across grid families, an Intl-based i18n engine, and a steady stream of new components. The release notes further down capture what landed in each framework and when; this post leads with the part that ties them together.

One AI-Assisted Development Toolchain

The toolchain grounds AI coding assistants in correct Ignite UI APIs, import paths, and design tokens – so the agent builds with your component library instead of guessing around it. It has three independently usable layers, and in 26.1 all three cover Angular, React, Web Components, and Blazor. The full overview is at infragistics.com/ai-assisted-app-development.

See it in action: in the What’s New in Infragistics Ultimate 26.1 webinar, Konstantin Dinev, Director of Product Development at Infragistics, walks through the CLI MCP server, the AI-configured project scaffolds, and the Generate-from-Image flow end to end – on the same premise this post starts from: an AI assistant is only as good as the context it is given.

The Ignite UI AI-assisted development workflow: a developer prompt flows through the IDE and agent, is grounded by Agent Skills and the Ignite UI MCP servers, and is rendered by the Ignite UI component library as production-ready output

Layer	What it does	Frameworks
Agent Skills	Developer-owned markdown that encodes component selection, import paths, and decision flows for AI assistants	Angular, React, Web Components, Blazor
Ignite UI CLI MCP server	Documentation, API reference, and scaffolding tools exposed to the agent over the Model Context Protocol	Angular, React, Web Components, Blazor*
Ignite UI Theming MCP server	Design tokens, palette generation, CSS custom properties, WCAG AA contrast validation	Angular, React, Web Components, Blazor

* The CLI MCP server provides full Blazor documentation and API support (shipped in CLI 15.2.0). CLI project scaffolding templates for Blazor are still in development – everything else in this section covers Blazor today.

One Command for All Four

A single command configures Agent Skills and both MCP servers in any existing Angular, React, Web Components, or Blazor project:

npx igniteui-cli ai-config

It copies the framework’s Agent Skills into the agent discovery path and writes the igniteui-cli and igniteui-theming server entries to .vscode/mcp.json. The same command, the same servers, the same setup story regardless of which of the four frameworks you work in. (After it runs, start each server in your AI client; Claude Code starts them automatically on first tool invocation.) The toolchain is configured for VS Code with GitHub Copilot, Cursor, Claude Desktop, Claude Code, and JetBrains AI Assistant.

Agent Skills Across the Board

Every modern framework ships its own Agent Skills inside its package, so the instruction layer is consistent everywhere – including a Generate-from-Image skill in each framework that turns a design image into a themed, working view.

Framework	Agent Skills
Angular	4
React	5
Web Components	5
Blazor	4

Skills are developer-owned: edit the SKILL.md, add your team’s conventions, and version it with your codebase. Because skills persist on disk, AI output in a workspace improves over time without any change to the underlying model – the mechanism is explained in Why AI Results Improve Over Time Without the Model Actually Learning. Setup and per-client wiring are in the Agent Skills documentation.

The Difference Is Measured

In a 7-scenario benchmark study across Ignite UI for Blazor and Ignite UI for Angular (May 2026), two Infragistics developers ran identical tasks in paired sessions – with and without the Ignite UI MCP servers and Agent Skills – using Claude Sonnet 4.6 in VS Code Copilot agent mode. In every scenario where the untooled model ignored the library entirely despite explicit prompts, tooling raised component compliance from 0/5 to 5/5. In the hardest single-prompt build, feature completion rose from 71% to 100%. Counting correction turns, the with-tooling sessions were cost-competitive or cheaper – the untooled path charges its correction cost later. Full tables and methodology are in the research paper An Empirical Study of MCP and Agent Skills Benefits and the companion blog Your AI Coding Assistant Is Confidently Wrong About Your Component Library. Both benchmark apps are public: with MCP and without MCP.

Optional: MAKER Multi-Agent Orchestration

For teams exploring multi-step AI automation, @igniteui/maker-mcp is an experimental orchestration server that decomposes complex tasks using consensus-based voting across multiple agents. It is separate from the standard toolchain setup and requires a GitHub PAT (read:packages) and an AI provider key (OpenAI, Anthropic, or Google). See the MAKER documentation.

Where the CLI MCP Server Lives

The CLI MCP server is publicly discoverable – listed on the official MCP registry (registry.modelcontextprotocol.io) and in the community-curated Awesome MCP Servers directory (mcpservers.org).

Redesigned Documentation and llms.txt

The help documentation and API reference for Angular, React, Web Components, and Blazor have been redesigned and migrated to the Astro framework. Existing URLs are preserved 1:1, so current bookmarks and deep links keep working.

For AI workflows, each docs site now publishes an llms.txt family: llms.txt (a curated index), llms-small.txt (a compact build for limited context windows), and llms-full.txt (the full documentation as plain markdown). AI assistants can ingest clean markdown instead of scraping rendered HTML – a complement to the CLI MCP server’s per-query lookups, not a replacement. Example: Ignite UI for Angular llms.txt.

Grid Lite: A Free, Open-Source Data Grid

Grid Lite is a new product in the Ignite UI family – a lightweight, high-performance data grid under the MIT license, free for commercial use with no feature gating. It is built as a Web Component (igniteui-grid-lite), so it runs with or without a framework, and the first framework-native wrapper, IgxGridLiteComponent for Angular, ships in 21.1 as a Developer Preview (React and Blazor wrappers are on the roadmap). It covers virtualization, sorting, filtering, theming, and Excel-style keyboard navigation, with a direct upgrade path to the full Ignite UI Data Grid. Grid Lite overview.

Grid Performance

The H1 2026 cycle delivers six rendering and change-detection optimizations across the grid scroll pipeline – applied automatically, with no API changes – to the Data Grid, Tree Grid, Hierarchical Grid, and Pivot Grid. Measured on a 100k-row dataset (Angular, React, Web Components):

Metric	Before	After	Change
Total Blocking Time	~8-12 sec	~3-5 sec	-50% to -60%
Frames per second	~15-25 fps	~40-55 fps	+100% to +150%

Blazor (25.2.77) gets the same dynamic scroll-throttle optimization; Blazor-specific FPS and TBT numbers are not published. This scroll work is one milestone in a longer arc – earlier releases reworked the data pipeline (Schwartzian-transform sort, iterative grouping, Excel-style filtering) to handle 1M+ rows. Full account: Engineering Fast Data Grids. Delivered in Angular 21.1, React 19.5.0/19.5.1, Web Components 7.0.0, and Blazor 25.2.77.

Grid PDF Export

PDF export ships across the grid families, producing multi-page documents with automatic page breaks, column group headers, summary rows, and landscape orientation by default, and respecting current filter, sort, and column-visibility state. Per-framework grid coverage:

Angular (21.1) – IgxGrid, IgxTreeGrid, IgxHierarchicalGrid, IgxPivotGrid; a new customFont option on IgxPdfExporterOptions adds Unicode support (Cyrillic, CJK, Arabic, Hebrew) via a Base64 TrueType font, with an optional bold variant.
React (19.5.x) – IgrGrid, IgrTreeGrid, IgrHierarchicalGrid, IgrPivotGrid (all four).
Web Components (7.0.0) – IgcGrid, IgcTreeGrid, IgcHierarchicalGrid; IgcPivotGrid is not covered.
Blazor (25.2.77) – IgbGrid, IgbTreeGrid, IgbHierarchicalGrid; IgbPivotGrid is not covered.

Intl-Based i18n

Grid date and number rendering moves to a native Intl-based pipeline, with a new public localization API and a separate igniteui-i18n-resources package; existing resource strings continue to work. Delivered in Angular 21.1 (grids, Calendar, DatePicker, DateRangePicker), React 19.5.0 (grids, IgrCalendar, IgrDatePicker, IgrDateRangePicker), and Web Components 7.0.0 (grid components). Not part of the Blazor release. Localization documentation.

Dock Manager 2.1

The Dock Manager is available across all four frameworks – Angular, React, Web Components, and Blazor – and advances to the 2.1 Web Component this cycle. In React 19.6.0, IgrDockManager moves to igniteui-dockmanager@2.1.0, adding minResizeWidth/minResizeHeight, a paneFlyoutToggle event, and additional layoutChange detail. In Blazor 26.1.51, IgbDockManager adds two-way synchronization between the Web Component layout property and the Blazor Layout property – making saved and restored layouts and more complex docking scenarios practical – plus a wider pane and tab event surface.

Ignite UI Dock Manager - docking, floating, and tabbed panes rearranged at runtime

More layouts are in the Dock Manager demos repo.

Release Notes: What Shipped, and When

The H1 2026 cycle delivered the following across each product line. Each release has its own dedicated blog and changelog with full detail.

Ignite UI CLI

15.0.0 (Apr 2026) – CLI MCP server; AI-ready scaffolds (AGENTS.md, CLAUDE.md, pre-wired .vscode/mcp.json); Generate-from-Image skills (Angular, React, Web Components); Angular template modernization; React templates expanded (30 added) to Web Components parity and updated to Vite 8; legacy project types removed.
15.1.0 (May 2026) – ai-config command; --agents / --assistants options on new; listed on the official MCP registry. Release blog
15.2.0 (May 2026) – official Blazor MCP support (docs + API); ai-config for Blazor; --framework option with auto-detection.
15.2.2 (Jun 2026) – in-tool API reference links; member-level get_api_reference lookup.
15.3.0 (Jun 2026) – side-nav-mini template (Angular, React, Web Components); side-nav and empty-project template alignment.

Ignite UI for Angular

21.1 – IgxGridLiteComponent (Developer Preview); HTML Popover API for overlays. Breaking change: grids require a new array reference for change detection. Release blog
21.2 – IgxCombo/IgxSimpleCombo selectionChanged event and disableClear; Snackbar/Toast positioning; overlay-settings shorthand (useContainerStrategy). Release blog

Ignite UI for React

19.5.0 / 19.5.1 – Agent Skills (4); HTML Popover API for dropdowns/dialogs. Breaking changes: CSS prefix rename, array-reference change detection, Node.js 22 minimum. Release blog
19.6.0 – Generate-from-Image skill; IgrSplitter and IgrHighlight.
19.7.0 – Invoker Commands API; Nav Drawer Popover positioning; Snackbar/Toast positioning; single-field Date Range Picker editing; Enter-to-submit form controls plus IgrInput date/time theming; updated Agent Skills. Release blog

Ignite UI for Web Components

7.0.0 – Agent Skills (4); HTML Popover API; IgcThemeProvider. Breaking changes: CSS prefix rename, removed Chat typingIndicator renderer and Tooltip disableArrow, Node.js 22 minimum. Release blog
7.1.0 – Generate-from-Image skill; IgcSplitter and IgcHighlight; grid maintenance.
7.2.0 – Invoker Commands API; Nav Drawer Popover positioning; Snackbar/Toast positioning; single-field Date Range Picker editing; Enter-to-submit form controls; updated Agent Skills. Release blog

Ignite UI for Blazor

Blazor uses a separate versioning scheme; the Ultimate 26.1 cycle is the umbrella that contains two builds.

25.2.77 (Mar 2026) – IgbQueryBuilder; IgbThemeProvider; Agent Skills (4). Breaking change: grids require a new array reference for change detection.
26.1.51 (Jun 2026) – IgbChat (Developer Preview); IgbSplitter; IgbHighlight. No breaking changes; supports .NET 10 and .NET 9. See the Ignite UI for Blazor 26.1 release blog.

Ultimate UI for Windows Forms and WPF

The desktop libraries ship a focused set of charting enhancements, identical across both products:

DataPieChart OthersCategory styling – new OthersCategoryBrush and OthersCategoryOutline properties style the aggregated “Others” slice directly.
Checkmark marker and configurable MarkerSize – a new marker shape plus a MarkerSize property (device-independent pixels) for line and scatter charts.
DataChart Range Bar Series – plots high/low value ranges as horizontal bars, the bar-oriented counterpart to RangeColumnSeries.
TimeXAxis LabelFormatOverride event – event-based control of time-axis label formatting at every level, from years down to milliseconds.
User Annotation Layers (Community Technology Preview) – users place annotations directly on chart visualizations at runtime.

Full details: What’s New in Ultimate UI for Windows Forms and What’s New in Ultimate UI for WPF.

On the horizon. Our aim is to support every framework our customers build on, and that includes the desktop. Extending the AI-assisted development experience to Ultimate UI for WPF and Windows Forms is a direction we are exploring, with more to share down the line.

Frequently Asked Questions

What’s new in Infragistics Ultimate 26.1? Infragistics Ultimate 26.1 extends the AI-assisted development toolchain – Agent Skills, the Ignite UI CLI MCP server, and the Theming MCP server – across Angular, React, Web Components, and Blazor, and adds Grid Lite (a free data grid), grid scroll-performance and PDF export work, an Intl-based i18n engine, and new components.

Does the Ignite UI AI tooling support Blazor? Yes. Agent Skills, the CLI MCP server (Blazor docs and API since CLI 15.2.0), and the Theming MCP server all cover Blazor. CLI project scaffolding templates for Blazor are still in development.

How do I set up the AI-assisted development toolchain? Run npx igniteui-cli ai-config in an Angular, React, Web Components, or Blazor project. It copies the framework’s Agent Skills and writes the CLI MCP and Theming MCP server entries to your AI client configuration.

Which frameworks does the toolchain support? Angular, React, Web Components, and Blazor – the same three-layer toolchain (Agent Skills, CLI MCP, Theming MCP) across all four.

Is Ignite UI Grid Lite free? Yes. Grid Lite is released under the MIT license, free for commercial use with no feature gating; the Angular wrapper (IgxGridLiteComponent) ships as a Developer Preview in 21.1.

Watch the Walkthrough

Konstantin Dinev demos the full AI-assisted toolchain – the CLI MCP server, AI-configured scaffolds, and Generate-from-Image – in the Ultimate 26.1 webinar.

Watch the Ultimate 26.1 Webinar ->

A Closing Thought

AI is a tool, and tools are neutral. An axe clears a path or causes harm depending only on who swings it and how – the blade decides nothing. Our own benchmarks say this more plainly than any opinion could: the same model and the same prompts produced production-ready output in a well-configured environment and confidently wrong code in a bare one. The tool did not decide which – the operator did. That is what a multiplier does: it amplifies whatever it is given, and it never changes the sign of what it multiplies. The teams that win with AI will not be the ones that bought it. They will be the ones who invested in what it multiplies.

Additional Resources

Infragistics Ultimate Angular Blazor React Web Components

Angular