Harness coverage
Claude Code Cloud Agent Telemetry in Beacon
Beacon captures Claude Code cloud sessions from inside the cloud sandbox and uploads per-session runtime logs to customer-managed storage.
June 10, 2026
What is Claude Code Cloud Agents?
Cloud agent telemetry lets teams observe provider-managed sessions that do not run on a developer laptop.
Collection path: Cloud sandbox hooks with direct GCS or S3 upload
Authoritative date: June 10, 2026 from v0.0.51 in the Beacon CLI changelog.
How Beacon reads Claude Code Cloud Agents
Beacon cloud helpers generate setup scripts and hook configuration for the Claude cloud sandbox. Hooks write /tmp/beacon/runtime.jsonl and upload a session object to GCS or S3.
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, prompt, tool, command, file, and lifecycle telemetry where hook payloads expose it
- Per-session runtime JSONL in customer-managed object storage
- Cloud run IDs aligned with provider session IDs
- Standalone beacon-hooks packaging for sandbox use
What you can do now
- Prototype Claude Code cloud telemetry without deploying Managed.
- Store session logs in customer-controlled GCS or S3 buckets.
- Trace cloud-agent work back to prompts, tools, commands, and files.
Get started
- Use beacon cloud claude-web print-setup to generate the sandbox setup script.
- Use beacon cloud claude-web print-hooks to generate hook settings.
- Configure upload credentials and validate the object in customer-managed storage.