Cursor Cloud Agents

Capture Cursor cloud agent telemetry and forward cloud-agent runtime logs to customer-managed Google Cloud Storage

Integration Overview

Use this integration to capture Cursor cloud-agent activity and upload each session log to your own Google Cloud Storage bucket. It is meant for testing cloud-agent telemetry without running a hosted Asymptote backend.

This flow depends on the Beacon CLI. You run beacon cloud commands from your workstation to create the GCS upload path and generate the setup script that runs inside the Cursor cloud sandbox.

If you’re interested in leveraging this telemetry ingest across your enterprise, Asymptote Managed is designed for production cloud-agent telemetry ingest at scale.

Overview

Cursor Cloud Agents run in Cursor’s cloud environment, so Beacon cannot use the long-running endpoint agent that local installs use. Instead, the setup script installs Beacon hooks inside the sandbox. During a cloud-agent session, those hooks write /tmp/beacon/runtime.jsonl; at the end of the session, Beacon uploads that file to GCS.

The setup has three parts:

1. Create a dedicated GCS bucket and uploader service account with Beacon.
2. Add Beacon cloud telemetry environment variables to the Cursor cloud environment.
3. Run a Beacon-generated setup script inside the Cursor cloud environment.

Each Cursor cloud agent session writes one readable JSONL object:

gs://<bucket>/<prefix>/provider=cursor_cloud/user_id=<user_id>/run_id=<cursor_session_id>/runtime.jsonl

Prerequisites

• Beacon CLI v0.0.52 or later.
• gcloud installed and authenticated to the Google Cloud project you will use for telemetry storage.
• A Google Cloud project where you can create buckets, service accounts, IAM bindings, and service account keys.
• Cursor Cloud Agent access for the repository you want to test.
• A Cursor cloud environment with outbound access to:
  • oauth2.googleapis.com
  • storage.googleapis.com
  • github.com

Install or upgrade Beacon before you start:

brew tap asymptote-labs/tap
brew install beacon
brew upgrade beacon
beacon version

Authenticate gcloud and select your project:

gcloud auth login
gcloud config set project <your-gcp-project>

1. Create the GCS Upload Path

From your workstation, choose a bucket and prefix:

export GCP_PROJECT="your-gcp-project"
export BEACON_TEST_BUCKET="your-beacon-cloud-agent-traces"
export BEACON_CLOUD_GCS_PREFIX="agent-traces/customer=my-team"

Review the GCP changes Beacon will make:

beacon cloud gcs setup \
  --project "$GCP_PROJECT" \
  --bucket "$BEACON_TEST_BUCKET" \
  --location us-central1 \
  --prefix "$BEACON_CLOUD_GCS_PREFIX" \
  --service-account beacon-cloud-trace-uploader \
  --print

Apply the setup and print the cloud telemetry environment variables:

beacon cloud gcs setup \
  --project "$GCP_PROJECT" \
  --bucket "$BEACON_TEST_BUCKET" \
  --location us-central1 \
  --prefix "$BEACON_CLOUD_GCS_PREFIX" \
  --service-account beacon-cloud-trace-uploader \
  --apply \
  --print-env

Copy the printed values. Redact BEACON_CLOUD_GCS_CREDENTIALS_B64 anywhere you share screenshots or logs.

The helper creates a dedicated uploader service account and grants it object upload access to the selected bucket.

2. Configure Cursor Cloud Agents

Open your Cursor Cloud Agent environment for the repository.

Add these environment variables:

BEACON_ORIGIN=cloud
BEACON_RUN_PROVIDER=cursor_cloud
BEACON_RUN_EPHEMERAL=true
BEACON_CLOUD_USER_ID_HASH=<stable-user-or-test-id>
BEACON_CLOUD_GCS_BUCKET=<bucket-from-setup>
BEACON_CLOUD_GCS_PREFIX=<prefix-from-setup>
BEACON_CLOUD_GCS_CREDENTIALS_B64=<base64-service-account-json>

If your Cursor cloud environment restricts outbound network access, allow:

oauth2.googleapis.com
storage.googleapis.com
github.com

3. Add the Setup Script

Generate the setup script for your Beacon release:

beacon cloud cursor print-setup --version v0.0.52

Paste the generated script into the Cursor cloud environment setup step. The script:

• installs beacon and beacon-hooks in /tmp/beacon/bin,
• finds the cloud sandbox repository root from BEACON_CLOUD_REPO_DIR, CURSOR_PROJECT_DIR, or the current directory,
• merges Beacon hook commands into .cursor/hooks.json,
• excludes generated Cursor hook settings from git commits.

If you are testing unreleased Beacon changes from a branch, build beacon and beacon-hooks from that branch in the setup script instead of using print-setup --version.

4. Run a Cloud Agent Task

Start a Cursor cloud agent task that uses tools. For example:

Read the README, run pwd && ls, create a tiny temporary markdown note under /tmp or in the repo, then summarize what you did.

Beacon captures Cursor cloud hook activity such as tool use, shell execution, file reads and edits, subagent lifecycle events, and compaction events where Cursor exposes hook payloads.

5. Verify GCS Upload

List the uploaded session objects:

gcloud storage ls --recursive "gs://${BEACON_TEST_BUCKET}/${BEACON_CLOUD_GCS_PREFIX}/"

You should see a path like:

provider=cursor_cloud/user_id=<user_id>/run_id=<run_id>/runtime.jsonl

Inspect the log:

gcloud storage cat "gs://${BEACON_TEST_BUCKET}/${BEACON_CLOUD_GCS_PREFIX}/provider=cursor_cloud/user_id=<user_id>/run_id=<run_id>/runtime.jsonl" | head

Expected fields include:

vendor=beacon
product=endpoint-agent
schema_version=1.0
origin=cloud
harness.name=cursor
run.provider=cursor_cloud

Security Note

The self-serve GCS flow above creates a dedicated service account scoped to object uploads for one bucket, then stores its credentials in the Cursor cloud environment. This is useful for proof-of-concept testing, but treat that environment variable as a sensitive credential.

Avoid broad credentials and review access before using this flow with sensitive telemetry.

Troubleshooting

The bucket is empty

Confirm the Cursor setup script ran and generated hooks:

ls -la .cursor
sed -n '1,160p' .cursor/hooks.json

Confirm hooks wrote telemetry:

ls -l /tmp/beacon/runtime.jsonl
head /tmp/beacon/runtime.jsonl

If runtime.jsonl exists but GCS is empty, check network access and GCS credentials. The cloud sandbox must reach both oauth2.googleapis.com and storage.googleapis.com.

Cursor tries to commit hook settings

The setup script appends .cursor/hooks.json to .git/info/exclude in the cloud sandbox. Confirm the exclude file exists in the sandbox clone:

tail -n 20 .git/info/exclude

Related

Cursor runtime support

Review local Cursor telemetry through Beacon-managed hooks.

Google Cloud Storage forwarding

Review local endpoint GCS forwarding for persistent endpoint deployments.

Asymptote Managed

Use managed secure ingest for production enterprise cloud-agent telemetry.

Agent Beacon on GitHub

Request new cloud-agent destinations or contribute support.