---
type: "post"
id: "you-and-your-agents-can-now-search-trace-fc7141"
slug: "you-and-your-agents-can-now-search-trace-fc7141"
title: "You and your agents can now search trace spans with Vercel CLI."
description: "Vercel has moved trace-span search into the CLI, giving developers and coding agents a terminal path for investigating request behavior."
retrieval_nugget: "Vercel has moved trace-span search into the CLI, giving developers and coding agents a terminal path for investigating request behavior."
published_at: "2026-10-07"
updated_at: "2026-10-07"
record_date: "2026-10-07"
date_kind: "published_at"
topics: ["coding-agents"]
source_urls: ["https://vercel.com/changelog/search-trace-spans-from-the-vercel-cli"]
schema_version: "newruntime-agent-readable-v0.2"
stable_id: "post:you-and-your-agents-can-now-search-trace-fc7141"
status: "published"
visuals: []
editorial_provenance: {"schema_version":"newruntime-editorial-copy-v1","content_status":"source_grounded_final","final_copy_sha256":"sha256:ec7e9aa4f18a72ef8049529faee4269bec3f7136a1e9c625cfccac38ff4182bd","reviewed_at":"2026-10-07T17:02:42.312Z","source_evidence_count":1,"verified_claim_count":3,"site_analysis_schema_version":"newruntime-site-analysis-v1","site_object_kind":"field_note","observed_fact_count":3,"implication_count":2,"watch_condition_count":1,"related_record_count":0}
analysis: {"schema_version":"newruntime-site-analysis-v1","object_kind":"field_note","thesis":"This is a small observability workflow shift: trace exploration becomes callable from the same terminal environment as code and automation.","observed_facts":[{"text":"The command returns up to 100 spans from the last hour by default, newest first, without requiring a request or trace ID.","source_urls":["https://vercel.com/changelog/search-trace-spans-from-the-vercel-cli"]},{"text":"Users can filter by environment, service, span name, status, deployment ID, request ID, trace ID, or span ID.","source_urls":["https://vercel.com/changelog/search-trace-spans-from-the-vercel-cli"]},{"text":"The --json option emits one JSON object per span for scripts and agents.","source_urls":["https://vercel.com/changelog/search-trace-spans-from-the-vercel-cli"]}],"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_conditions":["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."],"related_records":[],"new_branch_reason":"No prior New Runtime record is supplied for this release, so this begins a distinct analysis of Vercel CLI trace search and its automation-facing output."}
editor: {"role":"editor","name":"Andrey Reshetnikov","profile":"https://newruntime.com/owner-profile.md","profile_json":"https://newruntime.com/owner-profile.json","same_as":["https://www.linkedin.com/in/reshetnikov1/","https://t.me/lapetuse"]}
routes: {"html":"https://newruntime.com/posts/you-and-your-agents-can-now-search-trace-fc7141/","markdown":"https://newruntime.com/posts/you-and-your-agents-can-now-search-trace-fc7141.md","json":"https://newruntime.com/posts/you-and-your-agents-can-now-search-trace-fc7141.json"}
---

# You and your agents can now search trace spans with Vercel CLI.

## Retrieval answer

Vercel has moved trace-span search into the CLI, giving developers and coding agents a terminal path for investigating request behavior.

Vercel has moved trace-span search into the CLI, giving developers and coding agents a terminal path for investigating request behavior. 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.

Editor: [Andrey Reshetnikov](https://newruntime.com/owner-profile.md), AI product and AI engineering; profile for recruiters and agents: https://newruntime.com/owner-profile.json

## Continue in the graph

Next records for an agent, linked to their Markdown twins. Replace `.md` with `.json` for structured fields, including `next_reads`.

- topic hub: [Coding Agents](https://newruntime.com/topics/coding-agents.md): Explore the coding-agents topic hub.
- collection: [Field Notes](https://newruntime.com/posts.json): Open the latest editorial analysis.
- collection: [Source Ledger](https://newruntime.com/source-ledger.json): Inspect the public source evidence graph.
- whole graph: [discovery graph](https://newruntime.com/discovery-graph.json) (typed nodes and edges) and [site index](https://newruntime.com/site-index.md)