Devin Cloud Agent Telemetry in Beacon | Asymptote

What is Devin Cloud Agents?

Devin Cloud support is centrally collected. One run can pull every user session from the Devin API, normalize events, and optionally upload per-session snapshots.

Collection path: Org-wide API pull with optional GCS upload

Authoritative date: June 15, 2026 from v0.0.67 in the Beacon CLI changelog.

How Beacon reads Devin Cloud Agents

beacon cloud devin pull fetches Devin Cloud sessions, deduplicates by Devin event id, writes normalized endpoint events with provider=devin_cloud, and optionally uploads per-session JSONL to GCS.

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

• Message-level session lifecycle and prompts
• Agent messages and status
• Pull request and ACU usage metadata
• Per-user attribution through Devin user ids

What you can do now

• Collect autonomous Devin Cloud activity without per-user sandbox setup.
• Run one-time sweeps, scheduled jobs, or near-real-time watch mode.
• Backfill with full resync when needed.

Coverage note

The Devin API does not expose per-tool or per-command events for autonomous sessions.

Get started

1. Create a Devin organization service key.
2. Run beacon cloud devin pull for a one-time sweep or --watch for continuous polling.
3. Configure optional GCS upload for per-session snapshots.

Source references

• Runtime docs
• Source reference