skipTrailingSlashRedirect (added for the next-dev /api proxy 308) also defines __NEXT_MANUAL_TRAILING_SLASH, which disables the client router's trailing-slash normalization. Under output:'export' the router then requested RSC payloads as /<path>.txt while the build only emits /<path>/index.txt — every fetch 404ed and Next silently degraded EVERY <Link> navigation to an MPA (full-page) load. Most visible symptom: the sidebar remounted on each click and its expanded groups collapsed. - next.config.ts: dev-gate skipTrailingSlashRedirect (prod build normalizes links to /foo/ again; RSC fetches hit the emitted index.txt files) - GlobalSidebar: normalize usePathname() (client nav now yields /foo/, hard loads /foo — exact matches against the slash-less nav hrefs need both), and re-run the auto-expand effect when visibleExpandableGroups arrives so a hard load (deep link, F5) still expands the active group once MSAL resolves Verified: static export + local serve, marker survives Link nav (no document request, /terms/index.txt 200); tsc clean; vitest 611/611. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
AutopilotMonitor
Advanced monitoring and troubleshooting solution for Windows Autopilot deployments. Gain full visibility into every enrollment session with a detailed event timeline, fleet health dashboards, and session reporting. Define custom analysis rules to automatically detect issues and gather rules to collect targeted evidence. Retrieve diagnostics packages on demand, configure agent settings like auto-reboot behavior and automatic timezone adjustment — all managed centrally from the web dashboard.
Private Preview
Autopilot Monitor is currently running as a Private Preview. Visit autopilotmonitor.com to request access and learn more.
Overview
Autopilot Monitor provides real-time tracking, intelligent diagnostics, and automated troubleshooting for Windows Autopilot enrollment processes. It consists of:
- Bootstrap Script — PowerShell script deployed via Intune that starts monitoring early in the enrollment process
- Monitoring Agent — Lightweight .NET application that collects telemetry and evidence during enrollment
- Backend API — Azure Functions-based ingestion and processing pipeline
- Web Dashboard — Next.js application for real-time monitoring and fleet analytics
Architecture
For detailed information about the system architecture, components, and data flow, see Architecture Documentation.
Documentation
Full admin documentation is available at docs.autopilotmonitor.com
License
This project uses a split licensing model:
- MIT License — Agent (
src/Agent/) and Shared library (src/Shared/) — unrestricted use on end-user devices - AGPL-3.0 — Backend (
src/Backend/), Web Dashboard (src/Web/), and MCP Server (src/McpServer/) — server-side components remain open source
See LICENSE for full details.



