Iris Apps opt into AI navigation with @trackunit/iris-app-api 2.4.0
Your extensions can now describe their own pages to Trackunit Manager's AI assistant. Add an
aiNavigation field to a manifest — a list of in-app routes, each with a path, a title, and a
description — and the assistant can take a user straight to the page inside your app that answers
their question instead of dropping them on its root.
This works today for every extension type that has a page a user can land on: Fleet, Admin, App Settings, Asset Home, Site Home, Customer Home, and Asset Events Actions. The field is opt-in and purely additive — apps that don't declare it behave exactly as before.
See Extension Point Types — AI navigation for the full reference: the manifest shape, both Tanstack Router styles, and in-app paths for entity-scoped extensions.
If your app routes with Tanstack Router you don't have to keep a second copy of your routes in the
manifest. Annotate the routes you want to expose with staticData.aiNavigation and derive the field
with extractAiNavigationFromTanstackRouter(routeTree). Routes without the annotation are skipped, so
you opt in page by page.
@trackunit/iris-app-api 2.4.0 also ships a migration that does the mechanical part of that setup: it
adds the staticData.aiNavigation type augmentation to your router and derives aiNavigation from
your route tree in navigable extension manifests. Annotating individual routes is left to you.
nx g @trackunit/migrations:migrate
nx g @trackunit/migrations:run-migrations
Included migration
v2-4-0-add-ai-navigation(from@trackunit/iris-app-api2.4.0) — only touches extension types that supportaiNavigationand leaves everything else untouched.