Harness coverage
Factory Droid Telemetry in Beacon
Beacon discovers Factory Droid, validates its OTLP endpoint, and can install hooks for richer prompt, tool, file, and lifecycle telemetry.
May 15, 2026
What is Factory Droid?
Factory Droid support arrived with discovery, OTLP validation, endpoint hooks, and the first broader agent harness support matrix.
Collection path: OTLP HTTP plus optional hooks
Authoritative date: May 15, 2026 from v0.0.5 in the Beacon CLI changelog.
How Beacon reads Factory Droid
Beacon validates Factory Droid launch environment for OTLP collection and can manage hook settings while preserving non-Beacon hooks.
The result is normalized into Beacon's endpoint event schema so security teams can investigate activity by harness, repository, session, user, model, command, file, tool, MCP server, or approval context where the runtime exposes those fields.
Telemetry coverage
- Runtime discovery and OTLP endpoint validation
- Prompt and session events
- Write, edit, and create tool usage
- Stop and session-end telemetry through hooks
What you can do now
- Confirm Factory Droid is pointed at the local Beacon collector.
- Install optional hooks for richer lifecycle coverage.
- Keep existing Factory hook groups intact during install and uninstall.
Get started
- Configure OTEL_TELEMETRY_ENDPOINT=http://127.0.0.1:4318 in Factory Droid launch environment.
- Run beacon endpoint discover or status to validate telemetry state.
- Optionally run beacon endpoint hooks install --harness factory.