Harness coverage
Oh My Pi Telemetry in Beacon
Beacon documents Oh My Pi endpoint telemetry through managed extension hooks.
August 23, 2026
What is Oh My Pi?
Oh My Pi coverage is listed in the runtime support matrix as a managed extension path with session, prompt, tool, approval, command, file, MCP, reasoning, and usage telemetry.
Collection path: Managed extension hooks
Authoritative date: August 23, 2026 from Documentation update in the Beacon CLI changelog.
How Beacon reads Oh My Pi
Beacon uses the extension-shaped collection model for Oh My Pi and normalizes the events into the same endpoint schema used by local coding harnesses.
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 approval decisions
- Operator commands, file reads, and edits with unified patches
- MCP tool activity, agent reasoning, and token usage
What you can do now
- Track Oh My Pi as its own supported harness.
- Review extension-based telemetry beside hook and OTLP runtimes.
- Use the runtime docs for current installation and status details.
Get started
- Review the Oh My Pi runtime documentation.
- Install Beacon endpoint components on the machine where the harness runs.
- Follow the documented extension hook setup for your Beacon release.