Skip to content

The cross-harness, self-improving memory layer for AI agents. Join our community: https://discord.com/invite/zdNChS2fBu

Expand cloud telemetry README guidance

shukieshah48de54fe2b21
diff --git a/README.md b/README.md
index 8ad373e6..df0c0a47 100644
--- a/README.md
+++ b/README.md
@@ -97,9 +97,12 @@ Claude Cowork, OpenClaw).
Beacon can capture Claude Code on the web sessions by installing ephemeral
project-level hooks inside the cloud sandbox and uploading the per-session
-`runtime.jsonl` snapshot to customer-managed Google Cloud Storage. Start with
-the self-serve walkthrough in
-[`examples/cloud-agents/claude-web-gcs.md`](examples/cloud-agents/claude-web-gcs.md).
+`runtime.jsonl` snapshot to customer-managed Google Cloud Storage. Use
+`beacon cloud gcs setup` to create a scoped GCS uploader service account and
+print the Claude web environment variables, then use
+`beacon cloud claude-web print-setup --version <tag>` as the Claude environment
+setup script. The setup script writes `.claude/settings.local.json` inside the
+cloud clone only, so generated hook configuration stays out of commits.
#### Knowledge Worker Agent Harnesses
diff --git a/cli/beacon/README.md b/cli/beacon/README.md
index 0f223945..ba82f788 100644
--- a/cli/beacon/README.md
+++ b/cli/beacon/README.md
@@ -51,17 +51,37 @@ customer-managed GCS:
--print-env
```
-Then generate the Claude web setup script for a Beacon release:
+Copy the printed `BEACON_CLOUD_GCS_BUCKET`,
+`BEACON_CLOUD_GCS_PREFIX`, and `BEACON_CLOUD_GCS_CREDENTIALS_B64`
+values into the Claude Code web environment. Also set:
+
+```bash
+BEACON_ORIGIN=cloud
+BEACON_RUN_PROVIDER=claude_code_web
+BEACON_RUN_EPHEMERAL=true
+BEACON_CLOUD_USER_ID_HASH=<stable-user-or-test-id>
+BEACON_CLOUD_UPLOAD_INTERVAL=60s
+```
+
+Then generate the setup script for a Beacon release and paste it into the
+Claude Code web environment setup field:
```bash
./beacon cloud claude-web print-setup --version vX.Y.Z
```
The setup script installs `beacon-hooks` into the cloud sandbox, writes
-`.claude/settings.local.json` inside the sandbox clone, and uploads the
-per-session `/tmp/beacon/runtime.jsonl` snapshot to GCS. See
-[`../../examples/cloud-agents/claude-web-gcs.md`](../../examples/cloud-agents/claude-web-gcs.md)
-for the end-to-end walkthrough.
+`.claude/settings.local.json` inside the sandbox clone, and uploads one
+browser-viewable per-session `/tmp/beacon/runtime.jsonl` snapshot to GCS at:
+
+```text
+<prefix>/provider=claude_code_web/user_id=<id>/run_id=<claude-session-id>/runtime.jsonl
+```
+
+Claude web network access must allow `oauth2.googleapis.com` and
+`storage.googleapis.com`. If you are testing unreleased Beacon changes, clone
+and build the feature branch in the setup script instead of using
+`print-setup --version`.
Add optional Falcon LogScale HEC forwarding during install or repair: