Oliver Kieselbach
f783d609cf
GitHub Copilot / VS Code stalled forever on "Waiting for server to respond to initialize". Root cause is NOT initialize handling (the server answers it correctly) but the per-client redirect_uri binding at /oauth/authorize: it used an exact-string includes() match, while VS Code registers the loopback URI without a trailing slash (http://127.0.0.1:PORT) and then authorizes with the URL-normalized form (http://127.0.0.1:PORT/). The exact match returned false -> 400 invalid_request at /authorize -> no code -> no token -> initialize never authorized -> perpetual wait. Reproduced live against the deployed server. Replace the exact match with canonicalizeRedirectUri + redirectUriMatches: - parse + re-serialize so a trailing-slash / serialization difference compares equal; - drop the port for loopback hosts, per RFC 8252 section 7.3 (the AS must allow any port for loopback redirect URIs) — this also covers the ephemeral-port-per-run behaviour of native clients. The host allowlist already permits any loopback port, so this grants no new reach. Non-loopback hosts (e.g. vscode.dev) keep full host+port+path matching. Applied at both /oauth/authorize and /oauth/callback. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Autopilot Monitor
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 documentation is available at autopilotmonitor.com/docs
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.