GliderTrace Compatibility
GliderTrace requires the .NET 10 SDK. Individual collectors also require compatible local diagnostics tools.
Runtime and Workspace
The server scopes command and test runs to a workspace root.
| Area | Current support | Notes |
|---|---|---|
| .NET SDK | Required | Install .NET 10 SDK before installing or running glider-trace. |
dotnet on PATH | Required | Needed for global-tool execution and default command/test workflows. |
| Workspace root | Required | Defaults to the current directory. Override with --workspace when the MCP client starts elsewhere. |
| Process inventory | From 1.0.0 | Windows inventory includes local processes, including Framework targets. Other hosts list diagnostics-published processes. Check inventory coverage and each target capability before capture. |
| Test projects | Supported | trace_run_tests runs dotnet test and stores stdout, stderr, TRX, and normalized evidence when the project emits it. |
| Prebuilt test assemblies | Supported | trace_run_tests with runner: "vstest" runs prebuilt test DLLs through dotnet vstest with parsed TRX results, for legacy .NET Framework repositories. |
| Native VSTest test assemblies | From 1.1.0 | On Windows, trace_run_tests with runner: "vstest-console" runs workspace-scoped prebuilt assemblies through native VSTest. It requires --allow-executable vstest. Verified targets are Framework 4.8 and 4.8.1 assemblies on an installed Framework 4.8.1 runtime, with x86 and x64 native hosts. |
| Legacy restore, build, and test pipeline | From 1.1.0 | On Windows, trace_pipeline can restore packages, build, and run prebuilt Framework tests with workspace NuGet.exe, Visual Studio MSBuild, and native VSTest. This workflow requires all three executable policies. The verified pipeline uses a Framework 4.8 assembly on an installed Framework 4.8.1 runtime with an x64 host. See the trace_pipeline technical reference for prerequisites and options. |
| Builds with binlog evidence | Supported | trace_build captures a build.binlog and normalized build errors/warnings. The runner: "msbuild" mode uses Visual Studio MSBuild (Windows with VS installed, --allow-executable msbuild). |
| Package restore | Supported | trace_restore runs dotnet restore, or a workspace-local .nuget\NuGet.exe for packages.config solutions with runner: "nuget" (--allow-executable nuget-workspace). |
| Long-running commands | Supported | trace_start and trace_stop capture evidence across a running interval. |
Optional Diagnostics Tools
| Area | Current support | Notes |
|---|---|---|
dotnet-counters | Optional | Enables counter collection and trace_counters summaries. |
dotnet-gcdump | Optional | Enables trace_capture_gcdump for explicit CoreCLR GC dump capture. Framework GC dump capture is unsupported. |
| EventPipe traces | Supported | CoreCLR supports EventPipe traces through trace_run and trace_attach. trace_hotspots reads these artifacts. Framework EventPipe capture is unsupported. |
| Framework IIS ETW traces | From 1.1.0 | On Windows, import an ETL file for one selected process incarnation or capture a verified Framework IIS worker with trace_attach, backend: "etw", and the framework-iis-cold-start profile. Live capture requires sensitive-data and machine-wide-capture acknowledgments. Full IIS x86 and x64 capture and re-import are verified. IIS Express request events remain unverified. Check provider, clock, loss, stack, and target-identity coverage before interpreting missing evidence. |
| Process dumps | Opt-in | trace_capture_dump supports eligible CoreCLR targets and requires acknowledgeSensitive=true. Dumps can contain application data. Framework dump capture remains future work. |
Artifacts and Sensitive Data
| Area | Current support | Notes |
|---|---|---|
| Artifact root | Local | Defaults to <workspace>/.glider/glider-trace. Override with --artifact-root. |
| Stdout/stderr | Captured | Stored as session evidence and summarized for agents. |
| Raw dumps | Sensitive | Dump and GC dump capture is explicit and marked sensitive. |
| Exports | Bounded | trace_export returns compact summaries or artifact references. Raw sensitive artifacts are excluded by default. |
MCP Clients and Transports
Choose a client in the installation guide.
| Area | Current support | Notes |
|---|---|---|
| Local stdio | Default | The client starts one local server process. |
| Streamable HTTP | Supported | See HTTP setup for a separately managed server. |
Notes
- From version 1.0.0, GliderTrace checks the target identity before capture. This reduces the risk of selecting a reused process ID. See the technical target reference for capabilities and capture requirements.
- Runtime module versions do not identify application target frameworks. Server readiness and workspace access do not establish target capture permission.
- GliderTrace is local-first: evidence stays on the machine unless your MCP client or agent sends it elsewhere.
- Command execution is policy-limited; by default,
trace_runacceptsdotnetcommands. Start the server with repeatable--allow-executable msbuild|nuget-workspace|vstestflags to also admit Visual Studio MSBuild.exe (via vswhere), a workspace-local.nuget\NuGet.exe, or vstest.console.exe — each path-validated against workspace/toolchain roots. - Use project/workspace MCP configuration when possible so artifact roots and relative paths are predictable.