Tool selection guide
When structured runtime evidence helps
Choose tools to execute commands, collect runtime evidence, or inspect stored sessions.
Choose a task
Commands and tests
Run a workspace-scoped command and retain its evidence.
- Sessions retain exit codes, stdout, stderr, and normalized findings.
- Test runs can retain TRX artifacts and identified failures.
Long-running processes
Give a service or application an explicit evidence boundary.
- Start and stop one stored session around the process.
- Inspect the finalized session after the process stops.
Existing artifacts
Bring CI or local artifacts into a queryable session.
- Import supported logs, TRX, counters, traces, dumps, or OpenTelemetry data.
- Exports can reference local artifacts instead of placing raw binary data in a prompt.
Counters, traces, and dumps
Collect explicit runtime diagnostics from a local .NET process.
- Sensitive dump capture requires explicit acknowledgement.
- Findings retain their session and artifact identity.
Session queries
Read a bounded part of stored evidence after a run.
- Filter normalized events by kind, text, severity, or cursor.
- Group exception evidence by type, message, and first stack frame.
Before and after
Compare two stored sessions after a code change.
- Comparison output groups fixed, new, and persisting evidence.
- Keep the underlying commands and session identifiers with the result.