The Angular team shared their roadmap for AI-assisted coding workflows built on MCP Servers, enabling large language models to autonomously write, validate, and fix Angular apps. Also covered: migration routes for Signal Forms, the @ng-forge/dynamic-forms package, and NgRx version 21.
▶️ Catch the complete episode on YouTube:
This broadcast highlights developments from the Christmas period through New Year's Eve. The upcoming edition will cover only 2026 news.
Ng-Poland Keynote
Held in November, Ng-Poland has since published its keynote and Angular team Q&A sessions on YouTube. Below are the key points discussed.
Angular 21 features were the focus of the keynote, and they'd already been detailed in an earlier episode. Still, AI dominated the talk.
MCP Server Workflow
Jeremy Elbourn led off by walking through a proposed AI-driven development process.
Using Angular's MCP Server (Model Context Protocol), the LLM would initially craft up-to-date Angular code. Then it would launch the app and verify the generated output with Playwright's MCP Server.
When a bug arose, the Angular MCP could attach to the live browser, pull in data from the running app's state, and then locate the issue and patch it.
AI as User
Next, framework tech lead Alex Rickabaugh described what shifts the framework needs to stay viable moving forward. Past research involved observing real developers interact with proposed APIs. In contrast, they now treat AI as another kind of end-user and apply a matching methodology.
Alex pointed out the need to support more adaptive UIs as well. Concrete plans haven't been set, but he suggests reviewing community projects like Hashbrown.
Keynote video:
Q&A Session
Afterward, a Q&A took place, and a few notable points emerged:
Security
One inquiry focused on shielding your codebase against untrusted packages, particularly the type of attacks observed during the latter half of 2025. The answer pointed to the practices Angular applies within its own repository.
- It relies on
pnpm, which brings multiple benefits compared tonpm—for instance, it avoids running post-install scripts by default. - Renovate handles dependency updates, with a configuration that waits a specified duration, like 2 days, before installing newly released packages.
In general, exploring the Angular repository reveals additional security enhancements.
Angular Material and UI Libraries
Another query touched on @angular/aria and its relationship with Angular Material. According to Jeremy, the era of comprehensive UI libraries that are often challenging to tweak has come to an end.
The emphasis now leans toward adaptable, bespoke design systems, which is why @angular/aria thrives. It delivers solely the functionality, leaving all visual styling in the hands of developers.
Signal Forms Migration
Naturally, several questions about Signal Forms were raised as well.
The transition from Reactive Forms or Template-Driven Forms remains a key topic. Currently, you can employ FormControl or FormGroup from Reactive Forms within Signal Forms, but Alex mentioned that support for the reverse is coming: Reactive Forms will eventually accommodate Signal Forms.
Q&A video:
Dynamic Forms
The concept of dynamic forms revolves around supplying metadata—encompassing the value, validation constraints, and UI components like selects, text inputs, radio buttons, or checkboxes—from which the form gets constructed on the fly.
In the previous form system, libraries existed for this purpose. A notable example was ngx-formly. Currently, whether ngx-formly will extend support to Signal Forms, and the exact mechanism for doing so, remains undetermined.
However, a fresh library has emerged, specifically designed for Signal Forms from the outset. This library is called @ng-forge/dynamic-forms. It offers compatibility with widely-used UI frameworks: Angular Material, Bootstrap, as well as PrimeNG and Ionic.
ng-forge - Dynamic Forms for Angular
Forms are boring. Your code shouldn't be. Write the config, we handle the rest. Type-safe, signal-native, zero boilerplate Angular forms.
ng-forge.com
NgRx 21
Version 21 of NgRx, Angular's go-to state management solution, has arrived. Alongside a redesigned website and assorted enhancements, the events plugin for the SignalStore has officially graduated to a stable release.
NgRx Signals Events and a Fresh Coat of Paint in v21
The NgRx team is rolling out version 21, and it marks a full decade since the library first appeared. Alongside the anniversary, the release introduces a new badge and branding, signalling a refreshed identity for the project. The headline feature for developers is the debut of NgRxSignalsEvents.
The New NgRxSignalsEvents Feature
This new capability extends the Signals store inside the NgRx ecosystem. Simply put, NgRxSignalsEvents provides a set of APIs tied to the lifecycle of an application. If you are familiar with the existing class-based ComponentStore, you will likely recognise the design patterns here. The events library includes an interface called SignalsEvents, alongside helper functions for connecting into the Signals store's event stream.
Key APIs and Their Purpose
Through SignalsEvents, developers gain access to a set of hooks and utilities. With these in hand, you gain notification triggers and stream connections; for instance, there is an InitSignal API which can serve as a straightforward initialisation gate. This proves handy when you need to conduct some setup chore exactly once, before the primary application logic kicks off.
Furthermore, the package delivers a handy hook called effectOnInit. This functions as a wrapper around Angular's effect() that checks the init state, storing its results and clearing them when no longer relevant. The result includes a return value with dedicated properties—an isInit flag and an init method—to help manage the lifecycle efficiently.
The creation of the corresponding stream relies upon theeventproperty, which is declared on theAppEventmodel.
With this new facet, connecting to signals-based stores never felt more streamlined.
- The stable v21 release brings the new
NgRxSignalsEventsfeature. - The change log contains full details for the update.
- You can examine the migration guide to see how this feature fits into the overall picture.