vercel ci logs displays and follows task logs for a run
Introduced 2026-10-01 · score 0.99
HOW TO USE IT
When debugging a Vercel CI run, use `vercel ci logs <run-id>` to inspect task logs; add the documented filters or `--follow` to stream a running task. If the run fails before any tasks start, retrieve its setup logs.
vercel ci logs <run-id>vercel ci logs <run-id> --failed --task <task> --level <level>vercel ci logs <run-id> --followWHY THIS HELPS
Inspect or follow task logs while debugging a Vercel CI run.
REQUIREMENTS AND LIMITATIONS
- Version: 62.1.0
- <run-id> (required): Vercel CI run to inspect.
- --failed: Filter task logs to failed tasks.
- --task <task>: Filter logs by task.
- --level <level>: Filter logs by level.
- --follow: Stream logs for a running task.
- Follow mode performs a final full-snapshot read without the stream timestamp cursor when a task completes, reconnects healthy stream timeouts, handles JSON snapshot responses, respects stdout backpressure, preserves JSONL errors, and bounds interrupted or invalid response retries.
- For completed retried tasks, empty logs produce a stderr warning when no level filter is applied; valid quiet, cached, or skipped tasks do not fail. JSON mode emits a structured stderr warning and reserves stdout for log records.
- Human output distinguishes runs without failures yet from completed runs; empty `--failed` JSON results include `run.finished`.
- Commands resolve the latest attempt from the attempts endpoint instead of relying on list-row ordering.
- Reconnects replay retained logs and deduplicate by timestamp, level, message, and occurrence count, preserving repeated identical lines and older late arrivals in append-only history.
- Replay stops explicitly at its 8 MiB estimated-state or 50,000 distinct-record limit instead of silently evicting records; the final snapshot recovers retained logs suppressed within the active stream.
- Without server record IDs, an ingestion cursor, and a completion watermark, logs ingested after the final snapshot are not guaranteed; the final read drains logs available at that point, not future ingestion.
FIRST-PARTY EVIDENCE
Check the installed version and the source before using it. Entry JSON