OpenCode Agent Traces in Beacon

What is OpenCode?

OpenCode is an agentic coding environment that runs close to a developer's repository and can invoke tools, inspect files, request approvals, and produce code changes as part of a session.

That makes it useful to engineers and important to security teams. A single session can contain prompt text, model usage, command execution, file edits, web activity, and MCP tool calls.

How Beacon reads OpenCode

Beacon reads OpenCode through a managed plugin. The plugin emits ordered runtime telemetry into Beacon's local pipeline, where events are normalized beside the rest of the endpoint agent activity.

Under the hood, Beacon understands the parts of an OpenCode session that matter during review and investigation:

• Prompts, assistant text, reasoning, model usage, and cost.
• Tool invocation, tool results, tool failures, command execution, file activity, web activity, and MCP activity.
• Approval decisions and session lifecycle events, so the trace preserves both what happened and when it happened.

Delivery is fail-open, ordered, time-bounded, locally redacted and truncated, and collision-safe during install. Beacon observes the agent without turning the developer workflow into a service dependency.

What you can do now

With this update, teams can:

• Capture OpenCode activity in the same runtime log as other Beacon-supported agents.
• Review command, file, approval, web, and MCP activity from one correlated session record.
• Forward OpenCode traces through the same customer-managed shippers used for endpoint telemetry.