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
docs(cloud): the GCS helper grants objectUser, not upload-only
Saurav Singh2ddb9c161068
diff --git a/docs/runtimes/claude-code-cloud-agents.mdx b/docs/runtimes/claude-code-cloud-agents.mdxindex 77e3d5ac..0715cdd6 100644--- a/docs/runtimes/claude-code-cloud-agents.mdx+++ b/docs/runtimes/claude-code-cloud-agents.mdx@@ -156,8 +156,9 @@ share screenshots or logs.<img src="/images/claude-code-on-the-web/beacon-cloud-setup-print-env.png" alt="Terminal showing beacon cloud gcs setup --apply --print-env output with bucket, prefix, and credentials environment variables." /></Frame>-The helper creates a dedicated uploader service account and grants it object-upload access to the selected bucket.+The helper creates a dedicated uploader service account and grants it+`roles/storage.objectUser` on the selected bucket, which can read, list,+overwrite, and delete objects in that bucket, not only upload them.### S3@@ -349,7 +350,7 @@ vendor=beaconproduct=endpoint-agentschema_version=1.0origin=cloud-harness.name=claude+harness.name=claude_coderun.provider=claude_code_webrun.run_id=cse_...```@@ -363,8 +364,9 @@ nothing and grants no dashboard access, and revoking the device underdevice key lives in an environment variable: a sandbox has no keychain and nosecrets file to hold it, unlike a laptop, where the key stays in a `0600` file.-The self-serve GCS flow above creates a dedicated service account scoped to-object uploads for one bucket. The S3 flow creates a dedicated IAM user scoped+The self-serve GCS flow above creates a dedicated service account with+`roles/storage.objectUser` on one bucket, which can read, list, overwrite, and+delete objects in it. The S3 flow creates a dedicated IAM user scopedto `s3:PutObject` under one prefix. All three flows store credentials in theClaude Code environment, so treat those environment variables as sensitivecredentials.diff --git a/docs/runtimes/cursor-cloud-agents.mdx b/docs/runtimes/cursor-cloud-agents.mdxindex e79901a3..093703d6 100644--- a/docs/runtimes/cursor-cloud-agents.mdx+++ b/docs/runtimes/cursor-cloud-agents.mdx@@ -145,8 +145,9 @@ share screenshots or logs.<img src="/images/cursor-cloud-agents/beacon-cloud-setup-print-env.png" alt="Terminal showing beacon cloud gcs setup --apply --print-env output with bucket, prefix, and credentials environment variables." /></Frame>-The helper creates a dedicated uploader service account and grants it object-upload access to the selected bucket.+The helper creates a dedicated uploader service account and grants it+`roles/storage.objectUser` on the selected bucket, which can read, list,+overwrite, and delete objects in that bucket, not only upload them.### S3@@ -387,9 +388,10 @@ run.provider=cursor_cloud## Security note-The self-serve flows create a dedicated GCS service account or AWS IAM user-scoped to object uploads, then store its credentials in the Cursor cloud-environment. This is useful for proof-of-concept testing, but treat those+The self-serve flows create a dedicated GCS service account with+`roles/storage.objectUser` on one bucket (read, list, overwrite, and delete) or+an AWS IAM user scoped to object uploads, then store its credentials in the+Cursor cloud environment. This is useful for proof-of-concept testing, but treat thoseenvironment variables as sensitive credentials.Store credential values as Cursor Runtime Secrets, avoid broad credentials,