CI Agent Telemetry

Command Overview

beacon ci wraps supported agent commands and agent-launching CI steps with ephemeral Beacon telemetry. It runs for a single CI job without installing a persistent endpoint service or modifying runner-wide harness configuration.

Command syntax

beacon ci [command]

Use beacon ci exec when the workflow runs an agent command directly. For multi-step CI workflows or third-party GitHub Actions that launch agents internally, use beacon ci start and beacon ci finish.

beacon ci is designed for ephemeral CI jobs. For managed endpoint rollout on laptops or workstations, use beacon endpoint install.

For artifact upload, object storage export, and downstream SIEM handoff patterns, see CI Telemetry Exports.

Wrap Agent Runs

beacon ci exec starts a temporary local collector, injects supported telemetry configuration into one child process, writes normalized endpoint events to a CI runtime log, then validates that matching events were captured.

Wrap one agent command

beacon ci exec -- <agent command>

For example, wrap a Claude Code prompt in a GitHub Actions step:

Wrap Claude Code

beacon ci exec -- claude -p "Review this pull request"

Wrap Agent Actions

Some workflows call a third-party action that launches the agent internally. In those cases, start a detached Beacon session before the action and finish it in a cleanup step.

Wrap a CI action that launches an agent

- name: Start Beacon telemetry
  uses: asymptote-labs/agent-beacon@v0.0.95
  with:
    mode: start
    harnesses: claude

- name: Run Claude Code Security Review
  uses: anthropics/claude-code-security-review@main
  with:
    claude-api-key: ${{ secrets.CLAUDE_API_KEY }}
    comment-pr: false
    upload-results: true
    claudecode-timeout: "10"

- name: Finish Beacon telemetry
  if: always()
  uses: asymptote-labs/agent-beacon@v0.0.95
  with:
    mode: finish
    min-events: "1"
    upload-artifact: "true"
    artifact-name: beacon-claude-security-review-runtime-log

See the Claude Code Security Review session workflow for the full GitHub Actions example.

Commands

beacon ci exec

Run a command with agent telemetry captured for the CI job.

beacon ci start

Start a detached telemetry session for later CI steps.

beacon ci finish

Stop, validate, and export a detached telemetry session.

beacon ci validate

Validate Beacon CI telemetry artifacts after a job step.

Artifact paths

By default, Beacon writes CI artifacts under $RUNNER_TEMP/beacon when RUNNER_TEMP is set. Otherwise it uses the system temp directory.

Artifact	Default path
Runtime log	`$RUNNER_TEMP/beacon/runtime.jsonl`
Collector config	`$RUNNER_TEMP/beacon/otelcol.yaml`
Collector spool	`$RUNNER_TEMP/beacon/spool/otlp.jsonl`

Use --log-path when your workflow needs a stable artifact path.

beacon ci exec

Run a single command with ephemeral CI telemetry.

beacon ci start

Start detached telemetry across workflow steps.

beacon ci finish

Stop and validate a detached telemetry session.

beacon ci validate

Validate an existing CI runtime log.

CI Telemetry Exports

Export CI runtime JSONL through workflow artifacts, S3, GCS, or downstream pipelines.