GliderTrace Compatibility

GliderTrace runs locally as a .NET global tool and stores runtime evidence under the configured workspace artifact root.

Most workflows need only the .NET SDK and an MCP client. Optional diagnostics collectors unlock counters, GC dumps, and extra runtime artifacts.

Runtime and Workspace

The server scopes command and test runs to a workspace root.

AreaCurrent supportNotes
.NET SDKRequiredInstall .NET 10 SDK before installing or running glider-trace.
dotnet on PATHRequiredNeeded for global-tool execution and default command/test workflows.
Workspace rootRequiredDefaults to the current directory. Override with --workspace when the MCP client starts elsewhere.
Test projectsSupportedtrace_run_tests runs dotnet test and stores stdout, stderr, TRX, and normalized evidence when the project emits it.
Long-running commandsSupportedtrace_start and trace_stop capture evidence across a running interval.

Optional Diagnostics Tools

AreaCurrent supportNotes
dotnet-countersOptionalEnables counter collection and trace_counters summaries.
dotnet-gcdumpOptionalEnables trace_capture_gcdump for explicit GC dump capture.
EventPipe tracesSupportedtrace_run, trace_attach, and trace_hotspots work with runtime trace artifacts.
Process dumpsOpt-intrace_capture_dump requires acknowledgeSensitive=true. Dumps can contain application data.

Artifacts and Sensitive Data

AreaCurrent supportNotes
Artifact rootLocalDefaults to <workspace>/.glider-trace. Override with --artifact-root.
Stdout/stderrCapturedStored as session evidence and summarized for agents.
Raw dumpsSensitiveDump and GC dump capture is explicit and marked sensitive.
ExportsBoundedtrace_export returns compact summaries or artifact references. Raw sensitive artifacts are excluded by default.

MCP Clients and Transports

AreaCurrent supportNotes
Claude CodeSupportedUse stdio project scope for local runtime evidence; HTTP is available when the server is started separately.
CodexSupportedUse config.toml with stdio or Streamable HTTP.
Cursor, Copilot, Gemini CLI, OpenCode, PiSupportedUse direct command-based MCP configuration where available.
StdioDefaultThe default transport when an MCP client launches glider-trace.
Streamable HTTPSupportedRun glider-trace --transport http. Default port is 5003 so it can run beside Glider on 5001.

Notes

  • 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_run accepts dotnet commands.
  • Use project/workspace MCP configuration when possible so artifact roots and relative paths are predictable.
↑/↓ NavigateEnter OpenSpace Expand