glider-trace 1.1.0

.NET 10.0 This package targets .NET 10.0. The package is compatible with this framework or higher.
There is a newer version of this package available.
See the version list below for details. 
{
  "servers": {
    "glider-trace": {
      "type": "stdio",
      "command": "dnx",
      "args": ["glider-trace@1.1.0", "--yes"]
    }
  }
}
This package contains an MCP Server. The server can be used in VS Code by copying the generated JSON to your VS Code workspace's .vscode/mcp.json settings file. 
dotnet tool install --global glider-trace --version 1.1.0
This package contains a .NET tool you can call from the shell/command line. 
dotnet new tool-manifest
                    


                            if you are setting up this repo
                        

                    

                
dotnet tool install --local glider-trace --version 1.1.0
This package contains a .NET tool you can call from the shell/command line. 
#tool dotnet:?package=glider-trace&version=1.1.0
                    


                    

                
nuke :add-package glider-trace --version 1.1.0

GliderTrace

GliderTrace gives coding agents runtime evidence from .NET builds, tests, and processes through MCP. Capture failures, exceptions, counters, and traces; compare runs and connect stack frames to C# symbols.

Install

Requires the .NET 10 SDK and dotnet on PATH.

dotnet tool install --global glider-trace

See the installation guide for MCP client setup.

Capabilities

  • Run builds, package restores, tests, and workspace commands.
  • Capture traces, process dumps, GC dumps, and counters.
  • Import OpenTelemetry data, TRX files, build logs, and existing diagnostic artifacts.
  • Query exceptions and CPU hotspots; map stack frames to C# symbols.
  • Compare sessions, export summaries, and pin evidence for later use.

Use trace_status to check readiness. Set includeEnvironment=true to check available build and test executables. See the tool reference for the full catalog.

Run Modes

glider-trace --workspace /path/to/repo
glider-trace --transport http --workspace /path/to/repo

Stdio is the default. HTTP exposes MCP at http://localhost:5003/mcp.

Option Purpose
--workspace <path> Selects the workspace. Defaults to the current directory.
--port <1-65535> Sets the HTTP port. Default: 5003.
--artifact-root <path> Sets artifact storage. Default: <workspace>/.glider/glider-trace.
--allow-executable <policy> Enables msbuild, nuget-workspace, or vstest. Repeat for multiple policies.
--default-timeout 30m Sets tool timeouts; accepts ms, s, or m. Default: 20m; 0 disables them.
--max-response-chars <n> Limits response text in UTF-16 characters. Default: 60000; minimum: 1000; 0 disables the limit.
--max-pinned-bytes <n> Limits pinned storage. Default: 536870912 bytes. Retention never deletes pinned sessions.
--verbose Writes detailed logs to stderr.
--help / --version Shows CLI help or the installed version.

Troubleshooting

  • Command not found: add the global .NET tool directory to PATH, such as ~/.dotnet/tools on Linux or macOS.
  • Command rejected: only dotnet is allowed by default. Enable the required executable policy with --allow-executable.
  • Legacy build tools: msbuild uses Visual Studio; nuget-workspace uses .nuget/NuGet.exe; vstest uses Visual Studio or restored packages.
  • Target unavailable: inspect trace_list_processes capabilities and warnings. Framework capture is unsupported; CoreCLR capture requires diagnostics IPC.
  • Capture identity (unreleased): pass processId and targetId from the same fresh inventory item. Refresh inventory after an identity error.
  • Dump capture blocked: pass acknowledgeSensitive=true. GC dump capture also requires dotnet-gcdump.
  • Counter capture fails: install dotnet-counters and pass collectCounters=true.
  • Missing test evidence: check the project's TRX logger configuration. Failed-test retries require rerunFailed greater than zero and safe exact test identifiers.
  • Long operations time out: increase --default-timeout.

Updates

Each release expires 90 days after its release date.

dotnet tool update --global glider-trace

Feedback

send_feedback submits a public GitHub issue. It rejects code, paths, secrets, and stack traces. Set GLIDER_FEEDBACK=0, DO_NOT_TRACK=1, or --no-telemetry to disable it.

License

All non-commercial use and work on open-source projects are free with no time limit. Commercial use is free until paid plans become available. The full terms are in the LICENSE file inside this package.

Product Compatible and additional computed target framework versions.
.NET net10.0 is compatible.  net10.0-android was computed.  net10.0-browser was computed.  net10.0-ios was computed.  net10.0-maccatalyst was computed.  net10.0-macos was computed.  net10.0-tvos was computed.  net10.0-windows was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

This package has no dependencies.

Version Downloads Last Updated
1.3.0 115 9/26/2026
1.2.0 104 9/25/2026
1.1.0 93 9/24/2026
1.0.0 115 9/17/2026
0.18.0 131 9/4/2026
0.17.0 117 9/3/2026
0.16.0 119 9/2/2026
0.15.0 104 9/2/2026
0.14.0 105 9/1/2026
0.13.0 109 9/1/2026
0.12.1 132 8/30/2026
0.12.0 132 8/28/2026
0.11.0 116 8/26/2026
0.10.1 127 8/23/2026
0.10.0 127 8/20/2026
0.9.0 136 8/5/2026
0.8.0 140 7/27/2026
0.7.0 128 7/27/2026
0.6.0 152 7/15/2026
0.5.0 169 7/1/2026
Loading failed

## [1.1.0] - 2026-09-24
Features:
- add native VSTest workflows
- add gated dump analysis foundation
- extend package validity to 90 days
- add dump analysis capability kit
- add Framework IIS ETL import and ETW capture
Bug Fixes:
- preserve native runner evidence
- retain safe test evidence
- harden dump analysis preflight
- validate dump compatibility evidence
- enforce dump analysis limits
- complete dump analysis safeguards
- harden dump evidence provenance
- harden dump analysis limits and evidence
- close dump analysis trust gaps
- enforce dump backend evidence
- preserve dump identity consistency
- enforce protocol identity limits
- harden dump analysis evidence validation
- enforce terminal evidence identity
- preserve dump analysis request deadlines
- preserve dump analysis deadline provenance
- enforce dump analysis preflight boundaries
- harden dump analysis source contracts
- preserve terminal failure evidence
- inspect active server test assembly
- harden dump capability evidence
- enforce candidate resource limits
- bind candidate runtime evidence
- harden dump fixture evidence
- complete dump capability safeguards
- verify published files through opened handles
- isolate candidate launch files
- avoid macOS path interop and classify link failures
- separate validation rejections from fault telemetry
- keep ETW platform check in collector preflight
- align ETW identity and coverage reports
- report ETW capture failure details
- read ETW loss before session stop