OpenCode Telemetry in Beacon | Asymptote
What is OpenCode?
OpenCode support started as managed plugin discovery and hook delivery, then expanded into full correlated traces in v1.0.4.
Collection path: Managed plugin hooks
Authoritative date: May 18, 2026 from v0.0.10 in the Beacon CLI changelog.
How Beacon reads OpenCode
Beacon installs an owned plugin at the user or project OpenCode plugin path. The plugin forwards supported OpenCode events through the local hook adapter into runtime.jsonl.
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
- Chat messages and session events
- Command execution and permission activity
- Diff and file activity
- Errors and full correlated agent traces in newer releases
What you can do now
- Capture OpenCode activity without requiring a separate daemon.
- Review prompts, tools, commands, permissions, files, and errors in one timeline.
- Forward OpenCode telemetry through existing Beacon destinations.
Get started
- Install or update Beacon on the endpoint running OpenCode.
- Run beacon endpoint hooks install --harness opencode.
- Check the local dashboard or runtime log for OpenCode events.