Cline Runtime Support in Beacon

What is Cline?

Cline is an AI coding agent that can run from multiple hosts: as a VS Code extension, as a JetBrains plugin, and from the command line. The agent core is shared, but the surfaces where developers use it are different.

For enterprise telemetry, that distinction matters. Security teams need the activity to resolve to one runtime identity without asking every developer which host they used for a task.

How Beacon reads Cline

Beacon installs a managed plugin at ~/.cline/plugins/beacon.ts. Cline auto-discovers plugin files, so one install covers the Cline hosts on the machine without requiring a registry command.

The plugin collects prompts, task lifecycle and errors, tool lifecycle and results, commands with exit codes, file reads and edits with diffs, MCP activity, and per-task token usage and cost.

Beacon does not configure Cline's own OpenTelemetry export or hosted prompt storage. The activity stays on Beacon's local path and is normalized into the same runtime schema used by the rest of the endpoint.

What you can do now

With this update, teams can:

• Install Cline telemetry once and cover Cline usage across IDE and CLI hosts.
• See Cline in beacon endpoint discover, agent inventory, and the local dashboard.
• Distinguish Cline activity under the canonical cline harness name for dashboards, detections, and SIEM queries.