Devin CLI Telemetry in Beacon | Asymptote

What is Devin CLI?

Devin CLI support gives Beacon a hook-based path for observing sessions, prompts, tools, permissions, approvals, and file telemetry.

Collection path: Native hooks

Authoritative date: May 20, 2026 from v0.0.15 in the Beacon CLI changelog.

How Beacon reads Devin CLI

Beacon manages user-level Devin hooks in ~/.config/devin/config.json or project-level hooks in ./.devin/hooks.v1.json while preserving unrelated settings.

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 start and session end
• Prompt submission
• Pre-tool and post-tool activity
• Permission requests, approvals, stop events, and file telemetry

What you can do now

• Install Devin hooks at user or project level.
• Review Devin approvals and file activity in endpoint timelines.
• Uninstall Beacon hooks without disturbing non-Beacon Devin settings.

Get started

1. Run beacon endpoint hooks install --harness devin.
2. Use --level project when a repository-local hook file is desired.
3. Run beacon endpoint hooks status --harness devin to verify collection.

Source references

• Runtime docs
• Source reference