Skip to main content

​
Command Overview

beacon ci validate checks that the runtime log exists, parses as Beacon JSONL, and contains at least the required number of matching harness events.
Command syntax
beacon ci validate
Use validation after a job step when telemetry collection and agent execution are managed separately.

​
Flags

FlagDescription
--harness <harness>Required harness to validate. Defaults to claude
--log-path <path>CI runtime JSONL log path. Defaults to $RUNNER_TEMP/beacon/runtime.jsonl or the system temp path
--jsonPrint validation results as JSON
--min-events <count>Minimum matching events required. Defaults to 1

​
Examples

Validate the default CI artifact path:
Validate the default CI artifact path
beacon ci validate
Validate a custom runtime log:
Validate a custom runtime log
beacon ci validate --log-path "$RUNNER_TEMP/beacon/runtime.jsonl"
Require at least three Claude events:
Require at least three Claude events
beacon ci validate --min-events 3
Print machine-readable validation results:
Print machine-readable validation results
beacon ci validate --json

beacon ci

Review CI artifact paths and command group behavior.

beacon ci exec

Run a single command with ephemeral CI telemetry.

beacon ci finish

Stop and validate a detached telemetry session.