Devin Desktop Telemetry in Beacon | Asymptote
What is Devin Desktop?
Devin Desktop coverage extends Beacon beyond the Devin CLI into desktop-hosted agent activity exposed through compatible hooks.
Collection path: Cascade/Windsurf hooks
Authoritative date: June 4, 2026 from v0.0.39 in the Beacon CLI changelog.
How Beacon reads Devin Desktop
Beacon uses the same hook adapter model to normalize Devin Desktop prompt, command, MCP tool, file read, and file write payloads where Desktop exposes Cascade hook events.
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
- Prompt activity
- Command execution
- MCP tool activity
- File read and file write telemetry
What you can do now
- Capture Devin Desktop activity beside Devin CLI sessions.
- Use the same endpoint runtime log and forwarding path.
- Compare desktop and CLI activity through separate harness identity.
Get started
- Install Beacon endpoint components.
- Follow the Devin Desktop runtime docs for hook setup.
- Verify events in local dashboard or runtime.jsonl.