Bug Fixes

• check-rules: check-rules update now accepts PrometheusRule CRD files (#110)
  Previously, check-rules update -f failed with "no check rule ID provided" when given a PrometheusRule CRD file,
  because it did not detect the kind and route to the PrometheusRule parser. Both apply and check-rules create
  already handled this correctly.
• dashboards: dashboards update now accepts PersesDashboard CRD files (#111)
  Previously, dashboards update -f did not detect PersesDashboard CRD files, so the CRD-specific conversion
  (v1alpha1/v1alpha2 normalization, ID extraction from labels, annotation mapping) was skipped.
  Both apply and dashboards create already handled this correctly.

New Components

• agent-mode: Add agent mode for AI coding agents (#68)
  When active, agent mode defaults output to JSON, returns errors as JSON on
  stderr, emits --help as structured JSON, skips confirmation prompts, and
  disables colored output. Agent mode is activated via --agent-mode, the
  DASH0_AGENT_MODE environment variable, or auto-detection of known AI agent
  environment variables (CLAUDE_CODE, MCP_SESSION_ID, CURSOR_SESSION_ID, etc.).

Bug Fixes

• dashboards: Clear dashboard ID from the request body before update calls to avoid server-side rejection (#101)
  When updating a dashboard whose user-defined ID is a UUID, the server rejects the request if the
  same ID appears in both the URL path parameter and the request body. The CLI now strips the ID from
  the body before sending the update, since it is already passed as the URL path parameter.
• dashboards: Fix PersesDashboard annotations (folder-path, sharing, source) being silently dropped during conversion (#103)
  User-settable annotations (dash0.com/folder-path, dash0.com/sharing, dash0.com/source) on PersesDashboard CRDs
  were not carried over when converting to a Dashboard definition, affecting both apply and dashboards create.

Enhancements

• query: --filter now accepts JSON filter criteria copied from the Dash0 UI (#96)
  The --filter flag on logs query and spans query now accepts JSON arrays and objects
  as produced by the Dash0 UI "copy filter criteria" feature, in addition to the
  existing text-based filter syntax. JSON and text filters can be mixed freely.

Bug Fixes

• apply: Preserve user-settable annotations and permissions on asset round-trips (#99)
  dash0.com/folder-path, dash0.com/source, and dash0.com/sharing annotations were silently dropped during apply, <asset> create and <asset> update.
  spec.permissions on views and synthetic checks was also stripped.

Enhancements

• apply: Migrate asset create/update from Import APIs to standard CRUD APIs (#90)
  The apply command and individual asset create/update subcommands now use the standard
  Create and Update APIs instead of the Import APIs, which are intended for one-time migrations.

Bug Fixes

• apply: When an asset definition includes a user-defined ID, apply now always upserts, making repeated applies idempotent and preventing duplicate assets from being created. (#94)

Enhancements

• output: The update and apply commands now show a unified diff of changes (#66)
• dashboards: <asset> list -o yaml and -o json now output full asset definitions instead of summary list items (#67)
  YAML output is a multi-document stream (separated by ---) that can be piped directly to dash0 apply -f -.
  JSON output is an array of full asset definitions.
  This applies to all four asset types: dashboards, check-rules, views, and synthetic-checks.

Enhancements

• dashboards: Accept PersesDashboard CRD files in apply and dashboards create (#85)
  PersesDashboard CRDs (perses.dev/v1alpha1 and perses.dev/v1alpha2) are now accepted as input.

Enhancements

• logs, spans, traces: Add explorer deep link URL as the first line of output for logs query, spans query, and traces get (#71)
  The URL is printed after the table output and links to the corresponding Dash0 explorer view.

Bug Fixes

• synthetic-checks, views: Display the human-readable name instead of the CRD name for synthetic checks and views (#80)
  The get, create, and update commands for synthetic checks and views now read from
  spec.display.name instead of metadata.name, consistent with dashboards.

Enhancements

• errors: Include API response body in error messages when the backend does not return a structured error (#75)
  Previously, errors like 400 Bad Request only showed the HTTP status code and trace ID.
  Now, the full response body is displayed so that users can see the reason for the failure.
• dashboards: Make the <id> argument of dash0 <asset> update optional (#76)
  When the <id> argument is omitted, the ID is extracted from the file content.
  This applies to all asset types: dashboards, check rules, synthetic checks, and views.

Bug Fixes

• dashboards: Fix dashboards update overwriting dash0Extensions.id with the origin string (#77)
  Unify ID and name extraction between apply and per-asset CRUD commands by
  delegating to shared Extract* functions in internal/asset/.
• dashboards: Stop force-setting origin in asset update commands (#78)
  The synthetic-checks update, views update, and check-rules update commands
  were force-setting the origin to "dash0-cli", causing 400 errors when updating
  assets originally created with a different origin.