The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu
Go agent-ai-cliagent-harnessesagent-securitybrowser-extensionciclaude-codecloudcodexcursordetection-engineeringjevknowledge-basememorymobile-device-managementobservabilitysecuritysecurity-information-and-event-managementsecurity-toolstelemetrytraces
Document Cursor Cloud object storage flow
shukieshahd7483857cbf2
diff --git a/.cursor/start.sh b/.cursor/start.shindex 3578b488..23d74aeb 100755--- a/.cursor/start.sh+++ b/.cursor/start.sh@@ -7,13 +7,15 @@ BEACON_LOG_PATH="${BEACON_CLOUD_LOG_PATH:-$BEACON_HOME/runtime.jsonl}"mkdir -p "$(dirname "$BEACON_LOG_PATH")"BEACON_CLOUD_UPLOAD_NORMALIZED="$(printf '%s' "${BEACON_CLOUD_UPLOAD:-gcs}" | tr '[:upper:]' '[:lower:]')"+BEACON_CLOUD_S3_REGION_EFFECTIVE="${BEACON_CLOUD_S3_REGION:-${AWS_REGION:-${AWS_DEFAULT_REGION:-}}}"case "$BEACON_CLOUD_UPLOAD_NORMALIZED" ins3)if [ -n "${BEACON_CLOUD_S3_BUCKET:-}" ] &&+ [ -n "$BEACON_CLOUD_S3_REGION_EFFECTIVE" ] &&[ -n "${AWS_ACCESS_KEY_ID:-}" ] &&[ -n "${AWS_SECRET_ACCESS_KEY:-}" ]; then- echo "Beacon Cloud S3 forwarding is configured for bucket: $BEACON_CLOUD_S3_BUCKET"+ echo "Beacon Cloud S3 forwarding is configured for bucket: $BEACON_CLOUD_S3_BUCKET in region: $BEACON_CLOUD_S3_REGION_EFFECTIVE"elseecho "Beacon Cloud S3 forwarding is not active; set the S3 bucket, region, and AWS credentials to enable uploads."fidiff --git a/README.md b/README.mdindex 6f616419..8249d5fe 100644--- a/README.md+++ b/README.md@@ -111,8 +111,8 @@ CI, and cloud surfaces.| --- | --- | --- || [Anthropic](https://docs.asymptotelabs.ai/sdk/integrations-anthropic) | OpenLLMetry instrumentation through `@asymptote/sdk` | Supported Anthropic model call spans, errors, and OpenTelemetry attributes || [Claude Agent SDK](https://docs.asymptotelabs.ai/sdk/integrations-claude-agent-sdk) | Query wrapper through `Observe.wrapClaudeAgentQuery()` | Query root spans with Beacon-compatible prompt attributes |-| [Claude Code Cloud Agents](https://docs.asymptotelabs.ai/claude-code-cloud-agents) | Cloud sandbox hooks with GCS upload | Session, prompt, tool, command, file, and lifecycle telemetry where Claude Code cloud hook payloads expose it |-| [Cursor Cloud Agents](https://docs.asymptotelabs.ai/cursor-cloud-agents) | Cloud sandbox hooks with GCS upload | Tool, shell command, file, subagent, and compaction telemetry where Cursor cloud hook payloads expose it |+| [Claude Code Cloud Agents](https://docs.asymptotelabs.ai/claude-code-cloud-agents) | Cloud sandbox hooks with direct GCS or S3 upload | Session, prompt, tool, command, file, and lifecycle telemetry where Claude Code cloud hook payloads expose it |+| [Cursor Cloud Agents](https://docs.asymptotelabs.ai/cursor-cloud-agents) | Cloud sandbox hooks with direct GCS or S3 upload | Follow-up prompts, tool, shell command, file, subagent, and compaction telemetry after project hooks become active || [Devin Cloud Agents](https://docs.asymptotelabs.ai/devin-cloud-agents) | Org-wide API poll via `beacon cloud devin pull`, with GCS upload | Session, prompt, agent message, status, pull request, and ACU usage telemetry the Devin sessions API exposes (message-level; the autonomous agent runs no in-sandbox hooks) || [OpenAI](https://docs.asymptotelabs.ai/sdk/integrations-openai) | OpenLLMetry instrumentation through `@asymptote/sdk` | Supported OpenAI model call spans, errors, and OpenTelemetry attributes || [Vercel AI SDK](https://docs.asymptotelabs.ai/sdk/integrations-vercel-ai-sdk) | Tracer handoff through `experimental_telemetry` | AI SDK model call and tool spans where telemetry is enabled |@@ -147,8 +147,8 @@ management (SIEM), log aggregation, and object storage destinations.| Destination | Support path || --- | --- |-| [AWS S3](https://docs.asymptotelabs.ai/cli/siem-forwarding-s3) | Vector content pack over local runtime and inventory JSONL using customer-managed AWS credentials |-| [Google Cloud Storage](https://docs.asymptotelabs.ai/cli/siem-forwarding-gcs) | Vector content pack and packaged macOS helpers over runtime and inventory JSONL using customer-managed Google credentials |+| [AWS S3](https://docs.asymptotelabs.ai/cli/siem-forwarding-s3) | Vector over endpoint JSONL, CI upload, or direct compressed snapshots from supported cloud agents |+| [Google Cloud Storage](https://docs.asymptotelabs.ai/cli/siem-forwarding-gcs) | Vector and packaged macOS helpers over endpoint JSONL, CI upload, or direct compressed snapshots from supported cloud agents |#### Localdiff --git a/cli/beacon/README.md b/cli/beacon/README.mdindex ad9501bd..7a476149 100644--- a/cli/beacon/README.md+++ b/cli/beacon/README.md@@ -71,15 +71,16 @@ For Cursor Cloud Agents, keep the repository-owned setup in `.cursor/`:```text.cursor/environment.json+.cursor/hooks.json.cursor/install.sh.cursor/start.sh```The install script builds the current branch by default, or downloads a release-when `BEACON_VERSION` is set, then merges Beacon commands into-`.cursor/hooks.json` during environment setup. It defaults to safe hook coverage-while testing forwarding and skips shell/edit-specific hooks; set-`BEACON_CURSOR_CLOUD_FULL_HOOKS=1` to enable the full Cursor Cloud hook set.+when `BEACON_VERSION` is set. Generate `.cursor/hooks.json` with+`beacon cloud cursor print-hooks`, then commit it before starting a cloud agent;+the environment update script must not create hooks after Cursor has already+loaded the project configuration.For Claude Code on the web, generate the setup script for a Beacon release andpaste it into the provider's cloud setup field:@@ -91,7 +92,7 @@ paste it into the provider's cloud setup field:The setup script installs `beacon-hooks` into the cloud sandbox and uploads agzip-compressed `/tmp/beacon/runtime.jsonl` snapshot to object storage. Claude web writes`.claude/settings.local.json` inside the sandbox clone. Cursor cloud uses-`.cursor/environment.json` to install Beacon and generate project-level+`.cursor/environment.json` to install Beacon and committed project-level`.cursor/hooks.json` because Cursor cloud only runs repository project hooks.```text@@ -99,12 +100,13 @@ gzip-compressed `/tmp/beacon/runtime.jsonl` snapshot to object storage. Claude w<prefix>/runtime/date=YYYY-MM-DD/<timestamp>-cursor_cloud-<generated-or-explicit-run-id>.jsonl.gz```-Cloud network access must allow `oauth2.googleapis.com` and-`storage.googleapis.com`. Cursor cloud currently supports command hooks for tool-activity, shell execution, file reads and edits, subagents, and compaction-events; it does not currently run session start, session end, prompt submit, or-stop hooks in cloud agents. If you are testing unreleased Beacon changes, clone-and build the feature branch in the setup script instead of using+Cloud network access must allow the selected destination: both+`oauth2.googleapis.com` and `storage.googleapis.com` for GCS, or+`s3.<region>.amazonaws.com` for S3. Cursor cloud project hooks capture follow-up+prompts, tool activity, shell execution, file reads and edits, subagents, and+compaction after the writable environment becomes available. Early bootstrap+turns can precede project-hook activation. If you are testing unreleased Beacon+changes, build the feature branch in the setup script instead of using`print-setup --version`.Add optional Falcon LogScale HEC forwarding during install or repair:diff --git a/docs/architecture/architecture.mdx b/docs/architecture/architecture.mdxindex 43164908..fca26fba 100644--- a/docs/architecture/architecture.mdx+++ b/docs/architecture/architecture.mdx@@ -27,7 +27,12 @@ The endpoint architecture is local-first: local endpoint telemetry can be inspec4. Beacon writes the event to the active `runtime.jsonl` file.5. Operators inspect local activity in the dashboard or forward the JSONL stream to their security stack.-For CI and cloud-agent setup paths, see the [runtime surface overview](/runtimes), [`beacon ci`](/cli/ci), [`beacon cloud`](/cli/cloud), and [Asymptote Observe SDK](/sdk).+For CI and cloud-agent setup paths, see the [runtime surface overview](/runtimes),+[`beacon ci`](/cli/ci), [`beacon cloud`](/cli/cloud), and+[Asymptote Observe SDK](/sdk). Provider-managed cloud agents run+`beacon-hooks` inside the sandbox, write `/tmp/beacon/runtime.jsonl`, and can+upload compressed per-run snapshots directly to customer-managed GCS or S3+without the persistent endpoint collector or Vector.## Architecture Detailsdiff --git a/docs/changelog/cli.mdx b/docs/changelog/cli.mdxindex c383ba86..e633a194 100644--- a/docs/changelog/cli.mdx+++ b/docs/changelog/cli.mdx@@ -11,6 +11,20 @@ Stay up to date with the latest changes to the Agent Beacon CLI.## July 2026+### Unreleased++- **Cursor Cloud prompt telemetry** · Committed `beforeSubmitPrompt` project+ hooks now retain observed follow-up prompts and immediately refresh the+ per-run object-storage snapshot, including prompt-only turns after hooks+ become active.+- **Cursor Cloud S3 walkthrough** · Expanded the self-serve Cursor Cloud flow+ with direct, SigV4-signed uploads to customer-managed S3, static Runtime+ Secret credentials, regional egress requirements, and end-to-end prompt+ verification.+- **Repository environment reliability** · Updated the committed Cursor+ environment to use the current schema, build and embed `beacon-hooks` before+ the CLI, select a compatible Go toolchain, and report GCS or S3 startup state.+### v1.0.3 · July 14, 2026- **Detailed Claude Code tool telemetry** · Endpoint-managed and CI Claude Code sessions now enable `OTEL_LOG_TOOL_DETAILS=1`, preserving Bash commands, file paths, URLs, search patterns, and MCP server/tool arguments in exported OpenTelemetry events.diff --git a/docs/cli/cloud-cursor-print-setup.mdx b/docs/cli/cloud-cursor-print-setup.mdxindex 68b8d342..e3f4eca0 100644--- a/docs/cli/cloud-cursor-print-setup.mdx+++ b/docs/cli/cloud-cursor-print-setup.mdx@@ -33,9 +33,15 @@ for the current platform support list.Print setup for a specific Beacon release:```bash title="Print setup for a specific Beacon release"-beacon cloud cursor print-setup --version v0.0.95+beacon cloud cursor print-setup --version vX.Y.Z```+Replace `vX.Y.Z` with the desired release tag. Cursor Cloud prompt capture+requires a release containing the committed `beforeSubmitPrompt` hook and+immediate upload behavior. Until that release exists, build the branch+containing the change in the cloud environment instead of downloading an older+release.+## Related<Columns cols={2}>@@ -46,6 +52,6 @@ beacon cloud cursor print-setup --version v0.0.95Print project-level Cursor hook settings for a cloud sandbox.</Card><Card title="Cursor Cloud Agents" icon="cloud" href="/runtimes/cursor-cloud-agents">- Configure Cursor cloud agent telemetry and GCS upload end to end.+ Configure Cursor cloud agent telemetry and GCS or S3 upload end to end.</Card></Columns>diff --git a/docs/cli/cloud-s3-setup.mdx b/docs/cli/cloud-s3-setup.mdxindex 12a45df3..97f14d7e 100644--- a/docs/cli/cloud-s3-setup.mdx+++ b/docs/cli/cloud-s3-setup.mdx@@ -14,8 +14,9 @@ beacon cloud s3 setupThe helper creates or validates a bucket, blocks public access, creates adedicated IAM user, grants prefix-scoped `s3:PutObject`, creates one access key,-and prints the `BEACON_CLOUD_S3_*` plus AWS credential environment variables for-cloud agents.+and prints `BEACON_CLOUD_UPLOAD=s3`, `BEACON_CLOUD_S3_BUCKET`,+`BEACON_CLOUD_S3_PREFIX`, `BEACON_CLOUD_S3_REGION`, `AWS_ACCESS_KEY_ID`, and+`AWS_SECRET_ACCESS_KEY` for cloud agents.<Warning>This self-serve flow passes scoped AWS access keys into the provider-managed@@ -67,6 +68,9 @@ complete.<Card title="Claude Code Cloud Agents" icon="cloud" href="/runtimes/claude-code-cloud-agents">Configure Claude Code cloud agent telemetry and S3 upload end to end.</Card>+ <Card title="Cursor Cloud Agents" icon="cloud" href="/runtimes/cursor-cloud-agents">+ Configure Cursor cloud agent telemetry and S3 upload end to end.+ </Card><Card title="Log forwarding" icon="database" href="/log-forwarding">Review local endpoint S3 forwarding for persistent endpoint deployments.</Card>diff --git a/docs/cli/cloud.mdx b/docs/cli/cloud.mdxindex e83f5d1e..95210859 100644--- a/docs/cli/cloud.mdx+++ b/docs/cli/cloud.mdx@@ -53,9 +53,9 @@ IAM user, grants prefix-scoped `s3:PutObject`, creates one access key, andprints the `BEACON_CLOUD_S3_*` and AWS credential variables.<Warning>- This self-serve flow passes a scoped Google service-account key into the- provider-managed cloud agent environment. Use it for proof-of-concept testing- and prototyping. For production enterprise deployments, use+ These self-serve flows pass a scoped Google service-account key or AWS access+ key into the provider-managed cloud agent environment. Use them for+ proof-of-concept testing and prototyping. For production enterprise deployments, use[Asymptote Managed](/deployment/managed) or contact Asymptote about secureforwarding in customer-managed infrastructure.</Warning>@@ -73,9 +73,9 @@ prints the `BEACON_CLOUD_S3_*` and AWS credential variables.Configure Claude Code cloud agent telemetry and object-storage upload end to end.</Card><Card title="Cursor Cloud Agents" icon="cloud" href="/runtimes/cursor-cloud-agents">- Configure Cursor cloud agent telemetry and GCS upload end to end.+ Configure Cursor cloud agent telemetry and GCS or S3 upload end to end.</Card><Card title="Log forwarding" icon="database" href="/log-forwarding">- Review local endpoint GCS forwarding for persistent endpoint deployments.+ Compare direct cloud-agent uploads with local endpoint object-storage forwarding.</Card></Columns>diff --git a/docs/concepts/core-concepts.mdx b/docs/concepts/core-concepts.mdxindex 8e0f8355..ce1518e1 100644--- a/docs/concepts/core-concepts.mdx+++ b/docs/concepts/core-concepts.mdx@@ -41,7 +41,12 @@ An **agent harness** is the runtime or integration that produced an event. It ca## Cloud-Agent Telemetry-**Cloud-agent telemetry** is activity captured from provider-managed cloud agent sandboxes. Beacon cloud helpers print hook and storage setup so cloud sessions can produce Beacon-compatible `runtime.jsonl` artifacts, currently with self-serve Google Cloud Storage upload paths for supported cloud agents.+**Cloud-agent telemetry** is activity captured from provider-managed cloud agent+sandboxes. Beacon cloud helpers print hook and storage setup so cloud sessions+can produce Beacon-compatible `runtime.jsonl` artifacts and upload compressed+per-run snapshots directly to customer-managed Google Cloud Storage or Amazon+S3. Cursor Cloud project hooks capture supported events after the writable+environment becomes available, so early bootstrap turns may precede telemetry.## Observe SDKdiff --git a/docs/log-forwarding/index.mdx b/docs/log-forwarding/index.mdxindex 01354749..434ad122 100644--- a/docs/log-forwarding/index.mdx+++ b/docs/log-forwarding/index.mdx@@ -13,9 +13,10 @@ For [ephemeral CI jobs](/concepts/core-concepts#ci-telemetry), see [CI TelemetryFor [provider-managed cloud agents](/concepts/core-concepts#cloud-agent-telemetry), see[Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) or-[Cursor Cloud Agents](/runtimes/cursor-cloud-agents). Cloud agents currently support-Google Cloud Storage as the self-serve artifact destination; AWS S3 and SIEM-destinations are planned.+[Cursor Cloud Agents](/runtimes/cursor-cloud-agents). Supported cloud-agent+hooks can upload compressed per-run JSONL snapshots directly to+customer-managed Google Cloud Storage or Amazon S3. This direct sandbox upload+does not use the persistent endpoint's Vector forwarder.## Runtime log pathsdiff --git a/docs/runtimes/cursor-cloud-agents.mdx b/docs/runtimes/cursor-cloud-agents.mdxindex 74f37f81..981a6469 100644--- a/docs/runtimes/cursor-cloud-agents.mdx+++ b/docs/runtimes/cursor-cloud-agents.mdx@@ -6,13 +6,13 @@ description: "Capture Cursor cloud agent telemetry and forward cloud-agent runti## Integration OverviewUse this integration to capture Cursor cloud-agent activity and upload each-session log to your own Google Cloud Storage or Amazon S3 bucket. It is meant for testing-cloud-agent telemetry without running a hosted Asymptote backend.+session log to your own Google Cloud Storage or Amazon S3 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, generate project hooks to commit to-your repository, and generate the setup script that installs Beacon binaries in-the Cursor cloud sandbox.+workstation to create the object-storage upload path, generate project hooks to+commit to your repository, and generate the setup script that installs Beacon+binaries in the Cursor cloud sandbox.<Info>If you're interested in leveraging this telemetry ingest across your@@ -27,7 +27,7 @@ long-running endpoint agent that local installs use. Instead, commitproject-level Cursor hooks to `.cursor/hooks.json` and use the setup script toinstall Beacon binaries in the sandbox. During a cloud-agent session, thosehooks write `/tmp/beacon/runtime.jsonl`; Beacon refreshes the corresponding GCS-object as supported Cursor hook events run.+or S3 object as supported Cursor hook events run.```mermaidflowchart LR@@ -62,11 +62,13 @@ that value instead.## Prerequisites-- Beacon CLI `v0.0.56` or later.+- Beacon CLI `v1.0.3` or later for direct S3 upload. Cursor Cloud prompt capture+ requires the branch containing this change until a release includes it.- For GCS: `gcloud` installed and authenticated to a project where you cancreate buckets, service accounts, IAM bindings, and service account keys.- For S3: AWS CLI installed and authenticated to an account where you cancreate buckets, IAM users, inline policies, and access keys.+- `jq` on the verification workstation.- Cursor Cloud Agent access for the repository you want to test.- A Cursor cloud environment with outbound access to:- `oauth2.googleapis.com`@@ -180,6 +182,9 @@ beacon cloud s3 setup \The helper creates a dedicated IAM user and grants it `s3:PutObject` only underthe selected bucket prefix.+Copy the printed values. Treat `AWS_ACCESS_KEY_ID` and+`AWS_SECRET_ACCESS_KEY` as sensitive and redact them from screenshots and logs.+## 2. Configure Cursor Cloud AgentsOpen your Cursor Cloud Agent environment for the repository.@@ -213,7 +218,7 @@ AWS_SECRET_ACCESS_KEY=<secret-access-key-from-setup>```<Frame caption="Configure network access and Beacon runtime secrets for Cursor Cloud Agents.">- <img src="/images/cursor-cloud-agents/cursor-cloud-agent-config.png" alt="Cursor Cloud Agents settings showing network allowlist entries and Beacon runtime secrets for GCS upload." />+ <img src="/images/cursor-cloud-agents/cursor-cloud-agent-config.png" alt="Cursor Cloud Agents settings showing network allowlist entries and Beacon runtime secrets for object-storage upload." /></Frame>If your Cursor cloud environment restricts outbound network access, allow:@@ -254,9 +259,13 @@ git pushGenerate the setup script for your Beacon release:```bash-beacon cloud cursor print-setup --version v0.0.95+beacon cloud cursor print-setup --version vX.Y.Z```+Replace `vX.Y.Z` with a release tag that contains Cursor Cloud prompt capture.+Until that release exists, use the source-build path below; `v1.0.3` supports+direct S3 upload but predates the prompt hook.+Paste the generated script into the Cursor cloud environment setup step. Thescript:@@ -276,21 +285,34 @@ script:## 5. Run a Cloud Agent Task-Start a Cursor cloud agent task that uses tools. For example:+Start a Cursor cloud agent task that uses tools so the environment becomes+writable and project hooks become active. For example:```text-Read the README, run pwd && ls, create a tiny temporary markdown note under /tmp or in the repo, then summarize what you did.+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.+Beacon captures observed prompt submissions, tool use, shell execution, file+reads and edits, subagent lifecycle events, and compaction events where Cursor+exposes hook payloads.++Then submit a prompt-only follow-up with a unique marker:++```text+BEACON_PROMPT_SMOKE_<unique-id>++Do not inspect files or run tools. Reply exactly: PROMPT CAPTURE TEST COMPLETE+```<Note>Beacon captures prompt text through Cursor Cloud's `beforeSubmitPrompt`project hook and uploads that event immediately. Commit `.cursor/hooks.json`before starting the run so the prompt hook is available when the cloud- environment starts. `sessionStart` and `sessionEnd` remain unavailable. See+ environment starts. Cursor can perform early read-only or bootstrap work+ before project hooks become active, so the initial launch prompt may be+ absent; follow-up prompts are captured once hooks are running.+ `sessionStart` and `sessionEnd` remain unavailable. See[Cursor's Cloud Agent hook support matrix](https://cursor.com/docs/hooks#cloud-agent-support)for the current platform support list.</Note>@@ -331,6 +353,25 @@ For S3:aws s3 cp "s3://${BEACON_TEST_BUCKET}/${BEACON_CLOUD_S3_PREFIX}/runtime/date=<date>/<object>.jsonl.gz" - | gzip -dc | head```+For GCS, verify prompt capture with the unique marker from the follow-up:++```bash+gcloud storage cat "gs://${BEACON_TEST_BUCKET}/${BEACON_CLOUD_GCS_PREFIX}/runtime/date=<date>/<object>.jsonl.gz" \+ | gzip -dc \+ | jq -c 'select(.event.action == "prompt.submitted") | {prompt: .prompt.text, run: .run}'+```++For S3:++```bash+aws s3 cp "s3://${BEACON_TEST_BUCKET}/${BEACON_CLOUD_S3_PREFIX}/runtime/date=<date>/<object>.jsonl.gz" - \+ | gzip -dc \+ | jq -c 'select(.event.action == "prompt.submitted") | {prompt: .prompt.text, run: .run}'+```++The last prompt can be the final record in the object. That proves Beacon+uploaded the prompt immediately rather than waiting for a later tool event.+Expected fields include:```text@@ -349,8 +390,9 @@ scoped to object uploads, then store its credentials in the Cursor cloudenvironment. This is useful for proof-of-concept testing, but treat thoseenvironment variables as sensitive credentials.-Avoid broad credentials and review access before using this flow with sensitive-telemetry.+Store credential values as Cursor Runtime Secrets, avoid broad credentials,+rotate test keys after use, and review access before using this flow with+sensitive telemetry.## Troubleshooting@@ -400,7 +442,7 @@ git diff -- .cursor/hooks.jsonReview local Cursor telemetry through Beacon-managed hooks.</Card><Card title="Log forwarding" icon="database" href="/log-forwarding">- Review local endpoint GCS forwarding for persistent endpoint deployments.+ Compare direct cloud-agent uploads with local endpoint object-storage forwarding.</Card><Card title="Asymptote Managed" icon="cloud" href="/deployment/managed">Use managed secure ingest for production enterprise cloud-agent telemetry.diff --git a/docs/runtimes/cursor.mdx b/docs/runtimes/cursor.mdxindex 1292e5a8..06ae5a11 100644--- a/docs/runtimes/cursor.mdx+++ b/docs/runtimes/cursor.mdx@@ -47,7 +47,7 @@ beacon endpoint hooks install --harness cursor --level project| Area | Support ||------|---------|-| Prompt telemetry | Supported for local and cloud Cursor through `beforeSubmitPrompt` hooks. Cursor Cloud requires the project hook to be committed before the run starts; Beacon uploads the prompt event immediately. See [Cursor's Cloud Agent hook support matrix](https://cursor.com/docs/hooks#cloud-agent-support). |+| Prompt telemetry | Supported for local and cloud Cursor through `beforeSubmitPrompt` hooks. Cursor Cloud requires the project hook to be committed before the run starts and uploads observed prompts immediately; the initial launch prompt can precede hook activation during bootstrap. See [Cursor's Cloud Agent hook support matrix](https://cursor.com/docs/hooks#cloud-agent-support). || Command, tool, and file telemetry | Supported for tool, shell command, MCP-like, approval, and file edit payloads where Cursor exposes them; Cursor Cloud support is limited to Cursor's [cloud-supported command hooks](https://cursor.com/docs/hooks#cloud-agent-support). || Agent reasoning telemetry | Supported for local Cursor through `afterAgentThought` hooks. Each completed thinking block is recorded as an `agent.reasoning` event carrying the reasoning text in the OpenTelemetry GenAI output-messages shape (`gen_ai.output.messages` with a `reasoning` part), plus a `content` marker with the original text's hash and byte count. Reasoning is only available for models/modes where Cursor exposes visible thinking text. || Repository and branch context | Events include the workspace path as `repository`, and `branch` is resolved from the workspace's local git checkout (`.git/HEAD`) when Cursor does not supply one; disable local git resolution with `BEACON_DISABLE_GIT_METADATA=1`. |@@ -70,6 +70,6 @@ Hook events include metadata such as file path, operation, language, diff hash,Install, inspect, and uninstall runtime hook integrations.</Card><Card title="Cursor Cloud Agents" icon="cloud" href="/runtimes/cursor-cloud-agents">- Capture Cursor cloud agent telemetry with sandbox-local hooks and GCS upload.+ Capture Cursor cloud agent telemetry with sandbox-local hooks and direct GCS or S3 upload.</Card></Columns>diff --git a/docs/runtimes/index.mdx b/docs/runtimes/index.mdxindex ef207045..5ab95378 100644--- a/docs/runtimes/index.mdx+++ b/docs/runtimes/index.mdx@@ -50,8 +50,8 @@ These integrations are grouped by where the agent runs and how telemetry is coll| Cloud surface | Collection path | Telemetry coverage ||---------------|-----------------|--------------------|-| [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) | Cloud sandbox hooks with GCS upload | Session, prompt, tool, command, file, and lifecycle telemetry where Claude Code cloud hook payloads expose it |-| [Cursor Cloud Agents](/runtimes/cursor-cloud-agents) | Cloud sandbox hooks with GCS upload | Tool, shell command, file, subagent, and compaction telemetry where Cursor cloud hook payloads expose it |+| [Claude Code Cloud Agents](/runtimes/claude-code-cloud-agents) | Cloud sandbox hooks with direct GCS or S3 upload | Session, prompt, tool, command, file, and lifecycle telemetry where Claude Code cloud hook payloads expose it |+| [Cursor Cloud Agents](/runtimes/cursor-cloud-agents) | Cloud sandbox hooks with direct GCS or S3 upload | Follow-up prompts, tool, shell command, file, subagent, and compaction telemetry after project hooks become active || [Anthropic](/sdk/integrations-anthropic) | OpenLLMetry instrumentation through `@asymptote/sdk` | Supported Anthropic model call spans, errors, and OpenTelemetry attributes || [Claude Agent SDK](/sdk/integrations-claude-agent-sdk) | Query wrapper through `Observe.wrapClaudeAgentQuery()` | Query root spans with Beacon-compatible prompt attributes || [OpenAI](/sdk/integrations-openai) | OpenLLMetry instrumentation through `@asymptote/sdk` | Supported OpenAI model call spans, errors, and OpenTelemetry attributes |diff --git a/docs/security/data-flow-threat-model.mdx b/docs/security/data-flow-threat-model.mdxindex a6f47e28..b18c2cd2 100644--- a/docs/security/data-flow-threat-model.mdx+++ b/docs/security/data-flow-threat-model.mdx@@ -37,13 +37,19 @@ flowchart LR| Network exposure of collectors | Default OTLP receivers bind to `127.0.0.1` rather than an externally reachable interface || Over-collection of prompt or diff content | Scope supported runtimes and hook deployment deliberately before rollout, and review destination access for retained local telemetry || Secret leakage in retained content | Beacon applies redaction, sanitization, truncation, and event-size limits before writing supported content fields |-| SIEM credential exposure in endpoint config | File-based destinations tail local JSONL; Beacon does not store Elastic, Datadog, Sumo Logic, Rapid7, Microsoft Sentinel, AWS, or Google Cloud credentials. Splunk HEC and Falcon LogScale HEC tokens are stored in local collector configuration only when those optional destinations are enabled |+| Destination credential exposure | Persistent endpoint file-based destinations tail local JSONL, so Beacon endpoint configuration does not store Elastic, Datadog, Sumo Logic, Rapid7, Microsoft Sentinel, AWS, or Google Cloud credentials. Optional Splunk and Falcon tokens live in collector configuration. Self-serve cloud-agent uploads are a separate proof-of-concept path: scoped GCS or AWS credentials are injected into the provider-managed sandbox as runtime secrets and must be rotated and access-reviewed. || Removal uncertainty | Endpoint uninstall removes managed service and configuration state, with explicit `--keep-logs` and `--keep-config` exceptions |## Current BoundariesBeacon focuses on supported agent harness telemetry and local endpoint configuration context. It does not provide kernel or process monitoring, shell history collection, cloud audit ingestion, browser or SaaS telemetry, credential-use attribution, Datadog API export from Beacon, Sumo Logic API export from Beacon, Rapid7 API export from Beacon, or automatic mutation of Factory Droid shell profiles.+Provider-managed cloud agents use a separate ephemeral boundary from the local+endpoint. Their hook adapter writes sandbox-local JSONL and can send compressed+snapshots directly to customer-managed object storage. Upload failures are+fail-open so telemetry delivery cannot block the agent task; verify the remote+object rather than treating a successful agent run as proof of delivery.+## Related<Columns cols={2}>diff --git a/docs/security/retention-redaction.mdx b/docs/security/retention-redaction.mdxindex dbb0af38..72353a77 100644--- a/docs/security/retention-redaction.mdx+++ b/docs/security/retention-redaction.mdx@@ -67,7 +67,15 @@ Command events can include normalized tool and command context, with truncation## Forwarding Implications-Content handling is applied before events are written to `runtime.jsonl`. File-based destinations such as Wazuh, Elastic/Filebeat, Datadog Agent custom log collection, Sumo Logic forwarding, Rapid7 forwarding, Microsoft Sentinel forwarding, AWS S3 Vector forwarding, Google Cloud Storage Vector forwarding, and customer-managed shippers read the resulting local JSONL. Splunk HEC and Falcon LogScale HEC forwarding receive the same normalized collector output according to the configured endpoint pipeline.+Content handling is applied before events are written to `runtime.jsonl`.+File-based destinations such as Wazuh, Elastic/Filebeat, Datadog Agent custom+log collection, Sumo Logic forwarding, Rapid7 forwarding, Microsoft Sentinel+forwarding, AWS S3 Vector forwarding, Google Cloud Storage Vector forwarding,+and customer-managed shippers read the resulting local JSONL. Supported cloud+agents upload a compressed snapshot of their sandbox-local JSONL directly to+customer-managed GCS or S3. Splunk HEC and Falcon LogScale HEC forwarding+receive the same normalized collector output according to the configured+endpoint pipeline.Review runtime scope, artifact access, destination permissions, and downstream retention before rollout so retained content matches your approved telemetry policy.