The command returns up to 100 spans from the last hour by default, newest first, without requiring a request or trace ID. Thesis: This is a small observability workflow shift: trace exploration becomes callable from the same terminal environment as code and automation.
Mechanism: Users can filter by environment, service, span name, status, deployment ID, request ID, trace ID, or span ID; --since and --until narrow the time window. A supported subset of KQL enables conditions such as span.duration > 2000, while --json emits one JSON object per span for scripts and agents. Why now: The release explicitly presents the feature for both developers and coding agents, and structured output makes trace results consumable by automation rather than only by a human browsing a dashboard.
Implications: Teams can test whether command-line incident triage or agent-assisted debugging becomes easier to incorporate into existing workflows. The CLI interface may lower friction for targeted investigations, but the announcement does not establish improved diagnosis quality or autonomous remediation. Evidence boundary: The source documents the command, defaults, filters, query syntax, and JSON output; it provides no adoption, performance, or outcome measurements. Watch condition: Look for evidence that teams or agents use these filters and JSON results in repeatable debugging workflows, rather than treating CLI availability alone as proof of impact.