Skip to main content

​
Overview

beacon cloud prints setup helpers for provider-managed cloud agent environments. The first supported flow captures Claude Code cloud agent telemetry and uploads the cloud session’s runtime.jsonl to customer-managed Google Cloud Storage. For the complete walkthrough, see Claude Code Cloud Agents.

​
claude-web print-setup

Print a Claude Code cloud environment setup script for a Beacon release: 
beacon cloud claude-web print-setup --version v0.0.51
Paste the generated script into the Claude Code cloud environment setup field. It installs beacon and beacon-hooks into /tmp/beacon/bin, discovers the cloud sandbox repository root, and writes .claude/settings.local.json inside the sandbox clone.

​
claude-web print-hooks

Print the Claude hook settings used by the setup script: 
beacon cloud claude-web print-hooks \
  --binary-path /tmp/beacon/bin/beacon-hooks \
  --log-path /tmp/beacon/runtime.jsonl
This command is mostly useful for debugging or custom setup scripts.

​
gcs setup

Create or print self-serve GCS setup commands for cloud-agent telemetry: 
beacon cloud gcs setup \
  --project "$GCP_PROJECT" \
  --bucket "$BEACON_CLOUD_GCS_BUCKET" \
  --prefix "$BEACON_CLOUD_GCS_PREFIX" \
  --service-account beacon-cloud-trace-uploader \
  --apply \
  --print-env
The helper creates or validates a bucket, creates a dedicated uploader service account, grants object upload access, creates a service-account key, and prints the BEACON_CLOUD_GCS_* environment variables for Claude Code cloud agents.
This self-serve flow passes a scoped Google service-account key into the Claude Code cloud environment. Use it for proof-of-concept testing and prototyping. For production enterprise deployments, use Asymptote Managed or contact Asymptote about secure forwarding in customer-managed infrastructure.

Claude Code Cloud Agents

Configure Claude Code cloud agent telemetry and GCS upload end to end.

Google Cloud Storage forwarding

Review local endpoint GCS forwarding for persistent endpoint deployments.