vercel traces config ls lists project sampling rules

Introduced 2026-08-22 · score 0.95

HOW TO USE IT

When inspecting trace sampling rules, run `vercel traces config ls` from the linked project directory; add `--project <name-or-id>` and optionally `--scope <team>` to select a project explicitly. Add `--json` to output the rules as JSON.

WHY THIS HELPS

Inspect a project's trace sampling configuration from its linked directory or a selected scope.

REQUIREMENTS AND LIMITATIONS

• Version: 59.5.0
• --json: Output the rules as JSON.
• --project <name-or-id>: Select a project; defaults to the linked project.
• --scope <team>: Run the CLI command in the specified scope.
• Prerequisite: Vercel CLI must be authenticated to access project resources.
• Prerequisite: Project sampling rules are managed for the linked project or the project specified with `--project`.
• The project is taken from the linked directory, or from `--project` looked up in the scope selected by `--scope`; both resolve to ids before the request.
• A `--scope` that disagrees with the linked project is reported instead of applied.
• A project with no rules prints an empty state and the command that adds one.
• Non-interactive runs print an agent envelope with the project, a message, and suggested next commands; API refusals are reported on stdout with a machine-readable reason.

FIRST-PARTY EVIDENCE

• https://github.com/vercel/vercel/blob/main/packages/cli/CHANGELOG.md#5950
• https://vercel.com/docs/cli/traces
• https://vercel.com/docs/cli/global-options
• https://vercel.com/docs/cli

Check the installed version and the source before using it. Entry JSON

Report a problem with this card