docs: Add S3 CORS requirements for self-hosted storage

[warp-agent-staging]

What this feature does

Self-hosted agent data storage lets Enterprise teams keep agent artifacts and transcripts in customer-owned S3 buckets. Warp's web interfaces retrieve that data directly from S3 through presigned URLs. Shipped in v0.2026.09.30.08.29.stable_01 (2026-09-30).

Summary

Documents the CORS configuration required for Warp's web interfaces to load artifacts and conversation transcripts from self-hosted S3 storage.

Changes

• Adds a copy-pasteable S3 JSON CORS rule with the preferred https://*.warp.dev origin.
• Preserves the explicit-origin alternative and links to the AWS S3 CORS configuration reference.

Content design plan

• Reader and job: An Enterprise team admin configuring an S3 bucket for self-hosted agent data who needs artifacts and transcripts to open in Warp's web interfaces.
• Gap today: The S3 setup omits the browser CORS requirement, so a correctly connected bucket can still block web access to stored data.
• Change: Add the required GET origins and a copy-pasteable JSON rule to the bucket-creation step. Excludes provider-console walkthroughs beyond the linked AWS guide.

Unverified claims

None — the S3 CORS behavior and production origins were verified against AWS documentation, requester guidance, and source.

Documentation risk

Risk: engineering-review-required
Rationale: Adds required S3 CORS setup guidance for browser access to artifacts and transcripts.
Source files consulted: client/packages/factory/.env.production@afcffbc952db1dd32bea9072f7772ee50ae2ef59
Engineering review status: pending
Docs override: none

Validation

• python3 .agents/skills/style_lint/style_lint.py --changed --output /tmp/style_lint_revision.json — scanned 1 file; reported 2 pre-existing warnings on unchanged lines and no finding in the new CORS guidance.
• python3 .agents/skills/check_for_broken_links/check_links.py --internal-only — passed; 394 files scanned, 4,291 internal links checked, 0 broken links.
• npm run build — passed; 393 Markdown docs generated and Astro build completed.
• Focused JSON assertion — passed; the S3 CORS example parsed and matched the expected GET/https://*.warp.dev rule.
• python3 .agents/skills/doc_quality_policy/check_compression_contract.py src/content/docs/platform/data-storage.mdx --content-type feature-doc — reported the page's existing 3-callout count; origin/main reports the same count.
• git diff --check origin/main...HEAD — passed.

Co-Authored-By: Oz oz-agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 6, 2026 1:44pm UTC

[warp-agent-staging]

This PR was generated with Warp.

Comment @warp-staging-factory on this PR to send it follow-up work.

  

[warp-for-oss]

@bnavetta

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

Overview

This PR adds S3 CORS guidance to the self-hosted agent data storage docs so Warp web interfaces can read artifacts and conversation transcripts from customer-owned buckets.

Concerns

• The new CORS requirement is described, but the AWS CLI and Terraform setup paths do not show how to apply it, so readers can complete the documented setup with CORS still missing.
• No supplemental security findings were identified. No approved spec context was present, so there was no spec-alignment commitment to validate.

Verdict

Found: 0 critical, 1 important, 0 suggestions

Request changes

Comment /warp-agent-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[warp-for-oss]

⚠️ [IMPORTANT] This tells readers to configure CORS, but the AWS CLI and Terraform paths below still only create the bucket; add the corresponding aws s3api put-bucket-cors command and Terraform aws_s3_bucket_cors_configuration resource so readers who follow either tab actually apply the required rule.