.env.example

# agent-socket — deployment credentials
#
# Copy this file to `.env` (gitignored) and fill in the values, then
# the `scripts/deploy.sh` script can run non-interactively. Only needed
# if you're DEPLOYING the relay yourself. Not required for local dev,
# harness tests, the SDK, the CLI, or the chrome extension.
#
# Get a Cloudflare API token at:
#   https://dash.cloudflare.com/profile/api-tokens
#
# Minimum required scopes:
#   - Workers Scripts: Edit
#   - Account Settings: Read
#   - User Details: Read
#   - Zone: Edit  (for the agentsocket.dev / aisocket.dev custom domains)
#
# The account_id itself lives in `relay/wrangler.jsonc` — that's the single
# source of truth for which CF account the relay deploys to. You do NOT need
# CLOUDFLARE_ACCOUNT_ID in your env; wrangler reads it from the config.

CLOUDFLARE_API_TOKEN=

# Optional safety check. If set, scripts/deploy.sh will refuse to run unless
# wrangler.jsonc's account_id matches this value. Prevents accidentally
# editing wrangler.jsonc to a wrong account-id and shipping it. Forks should
# set this to their own account-id (matching what's in wrangler.jsonc) once
# they've done their first deploy.
# EXPECTED_ACCOUNT_ID=