trace_status

[debug]

Reports workspace roots, runner policies, session settings, and optional diagnostics capabilities. Development builds with local journal status also report cached local error journal state; released GliderTrace 1.3.0 does not.

Try it locally in the GliderTrace playground

Parameters

Examples

Replace sample paths and symbol keys with values from your workspace.

Check GliderTrace readiness

{}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_status",
    "arguments": {}
  }
}

Check which build/test/restore runners work here before the first run

{
  "includeEnvironment": true
}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_status",
    "arguments": {
      "includeEnvironment": true
    }
  }
}

Check whether this server process is leaking handles or memory

{}

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "trace_status",
    "arguments": {}
  }
}

Response Notes

Returns server version, workspace root, artifact root, retention/redaction defaults, a <code>telemetry</code> block (<code>enabled</code> plus the reason it is off), a <code>feedback</code> block (<code>enabled</code>, <code>reason</code>, <code>detail</code>, and the session quota as <code>remainingThisSession</code> and <code>maxPerSession</code>), and a <code>capabilities</code> block listing each executable policy and the runners for <code>trace_run_tests</code>, <code>trace_build</code>, and <code>trace_restore</code> with a reason when one is unavailable.

GliderTrace 1.4.0 and later add a sanitized <code>license</code> block. It includes <code>environment</code>, <code>state</code>, <code>valid</code>, <code>commercialRights</code>, <code>paidThrough</code>, <code>action</code>, <code>revocationPending</code>, <code>licenseType</code>, <code>notice</code>, <code>pricingUrl</code>, and <code>termsUrl</code>. <code>valid</code> describes the signed grant, not permission under the free license. <code>commercial</code> requires verified production rights; <code>sandbox</code> identifies a test grant without production rights. <code>free</code> covers non-commercial and open-source use and a 30-day organization evaluation; commercial use beyond evaluation requires a paid license. The packaged LICENSE controls each version.

Status makes no network or vault call and exposes no credentials, complete grants, or account identifiers. Production is the default; sandbox requires explicit selection.

Development builds with local journal status add a separate <code>localErrorJournal</code> block. Released GliderTrace 1.3.0 does not expose it.

It reports <code>enabled</code>, nullable <code>available</code>, <code>reason</code>, resolved <code>directory</code>, <code>filePattern</code>, <code>schemaVersion</code>, retention limits, <code>writeState</code>, <code>storageFailure</code>, and <code>droppedRecords</code>. It contains cached observations, no journal contents, and performs no storage check.

<code>writeState</code> is <code>not_attempted</code>, <code>succeeded</code>, or <code>failed</code>. <code>available: null</code> means no record write has established availability. A prior successful write does not guarantee current disk access. Disabled or unavailable status does not prove that older records are absent.

A <code>process</code> block reports this server process’s own <code>handles</code>, <code>privateMemoryMb</code>, <code>threads</code>, <code>uptimeMinutes</code> and <code>sampledUtc</code>, plus <code>diagnosticsLog</code> — the directory holding a capped local NDJSON history of those readings, written every five minutes and never sent anywhere. The block is absent until the first sample is taken, and on a platform that does not report a handle count. Executable resolution and local diagnostic tool discovery are included only when <code>includeEnvironment</code> is true.

From GliderTrace 1.0.0: capabilities.runtimeCapture describes support by runtime family. captureSelection explains target selection and identity checks. The matrix describes runtime support, not permission or readiness for a selected process. Set includeEnvironment=true to check local helper availability.

GliderTrace 1.0.0 returns compact JSON for every tool. Result fields appear beside success; there is no response-format parameter. success describes the tool call. Check the process or session status and exitCode separately. Scalar results and fields that conflict with reserved names appear under result.

To migrate an envelope consumer, read response.sessionId instead of response.data.sessionId. Stored sessions and exported files keep their formats. --max-response-chars limits response text to 60,000 UTF-16 characters by default. Use 0 to disable it, or at least 1,000. This limit counts text characters, not transport bytes or tokens.

outputLimit.truncated marks omitted response detail. It does not change capture completeness. Use the returned next tool and arguments when available. Do not repeat a command or feedback submission to recover omitted output. For event pages, keep the filters and cursor while reducing limit.

For session details, set includeArtifacts and includeTopFindings to false to reduce output. Check error, actionable meta, warnings, and coverage before drawing conclusions. Internal diagnostics stay in local server logs.