Harness coverage
Pi Telemetry Coverage in Beacon
Beacon documents Pi endpoint telemetry as a managed extension path with prompts, tools, commands, file changes, reasoning, and usage.
August 23, 2026
What is Pi?
Pi coverage is extension-shaped rather than OTLP-shaped. The changelog first records Pi discovery in v1.2.2, then corrects the runtime facts in the support matrix on August 23.
Collection path: Managed extension hooks
Authoritative date: August 23, 2026 from Documentation update in the Beacon CLI changelog.
How Beacon reads Pi
Beacon recognizes Pi, normalizes Pi spellings onto pi_cli, resolves the managed extension path, and documents extension-based telemetry. The changelog explicitly says the August 21 release was discovery-only.
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
- Session lifecycle and prompts
- Tool lifecycle and operator commands
- File reads and edits with unified patches
- Agent reasoning and token usage where available
What you can do now
- Track Pi as a distinct harness instead of merging it into another runtime.
- Use the Pi runtime docs for the current extension path and telemetry matrix.
- Avoid treating discovery-only changelog entries as hook-event support.
Coverage note
The August 21 changelog entry is discovery-only and says no Pi hook events are collected in that release.
Get started
- Review the current Pi runtime documentation.
- Use beacon endpoint discover to confirm Pi detection and managed extension state.
- Follow the runtime docs for installation once extension collection is available in your Beacon release.