Oliver Kieselbach 00f3bf61ef feat(mcp,backend): server-driven response cap + version prefix + lean projection
Real-world test exposed two distinct LLM-context bottlenecks the pagination
rollout alone didn't solve:

  1. Anthropic's MCP client truncates tool responses at ~25-30k chars by
     default, mid-page; nextLink follows but rows in the truncated middle are
     silently lost. pageSize alone can't fix this — even pageSize=50 of full
     SessionSummary objects (~1.5KB each) blows the cap.

  2. Aggregation queries ("how many V2 enrollments?") shouldn't need 1.5MB of
     SessionSummary blobs paginated across 4 round-trips. The LLM only needs a
     handful of fields to count.

Three coordinated fixes, all server-driven so customers connecting via MCP
get them automatically without any client config:

* `_meta.anthropic/maxResultSizeChars` annotation on every tool response,
  calibrated per response density (sessions=300k, events=250k, rawTable=500k,
  small=50k). The Anthropic client respects it and stops mid-page truncation.
  New `toolResultText()` helper in shared.ts wraps the pattern.

* `fields=` projection on `search_sessions` and `query_raw_sessions` (server-
  side, prunes wire payload 5-20x) and on `query_table` (client-side, since
  TableEntity columns are dynamic). Always retains PartitionKey + RowKey for
  cursor stability. Tool descriptions now actively recommend it for counting /
  aggregation queries.

* `agentVersionPrefix=` / `imeAgentVersionPrefix=` filters on `search_sessions`
  and `query_raw_sessions`. Replaces the "one call per build" loop pattern when
  the LLM wants a whole version line. Mutually exclusive with the exact-match
  variants (exact wins). Fingerprint-bound so a token from "2.0." can't replay
  into "2.1.".

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-07 11:31:50 +02:00
2026-04-29 09:00:52 +02:00
2026-03-17 18:24:01 +01:00
2026-03-26 07:02:33 +01:00
2026-05-07 08:51:22 +02:00

Autopilot Monitor

Status License Website

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.

S
Description
Windows Autopilot & Intune enrollment monitoring: live session timelines, fleet health, diagnostics, and an MCP server for AI-assisted troubleshooting.
Readme AGPL-3.0 60 MiB
Languages
C# 72.7%
TypeScript 25.7%
PowerShell 1%
JavaScript 0.5%