These are agent-facing workflows where runtime evidence matters more than another source-code search.
Ask
> Use GliderTrace to run the test project and summarize the first actionable failure with artifacts.
Why GliderTrace helps
The agent gets a stored test session with stdout, stderr, TRX evidence, and a compact failure summary instead of a long terminal log.
Tools: trace_run_tests, trace_get_session
Ask
> Run the failing dotnet command with GliderTrace and keep the evidence available while we inspect the code.
Why GliderTrace helps
The command result, exception-like output, warnings, and artifact references stay tied to a session the agent can revisit after edits.
Tools: trace_run, trace_query_events
Ask
> Start the app under GliderTrace, let me trigger the bug, then stop the session and summarize what happened.
Why GliderTrace helps
Start and stop boundaries keep the runtime evidence attached to the process interval instead of relying on a mixed terminal scrollback.
Tools: trace_start, trace_stop, trace_get_session
Ask
> Import these CI TRX and log artifacts into GliderTrace and export an agent-ready markdown summary.
Why GliderTrace helps
Large logs and test artifacts become a compact local session summary with artifact references and sensitive raw contents excluded by default.
Tools: trace_import_artifacts, trace_export
Ask
> Compare the failing session with the new session and tell me which failures are fixed, new, or persisting.
Why GliderTrace helps
The agent can report runtime change directly from stored sessions instead of mentally diffing two noisy command outputs.
Tools: trace_compare_sessions, trace_export
Ask
> Collect runtime evidence for this slow path and summarize counters or CPU hotspots without pasting raw artifacts.
Why GliderTrace helps
Counters and trace artifacts stay local while the agent receives bounded summaries and references to the files that produced them.
Tools: trace_run, trace_counters, trace_hotspots
Ask
> Group exceptions from the last session and correlate the stack frames to C# symbols.
Why GliderTrace helps
The agent can move from runtime evidence to code navigation using stored stack-frame data instead of searching exception text manually.
Tools: trace_exceptions, trace_correlate_code