Application security settings
Use independent random values for the signing, HMAC, and delivery settings. Store them in the deployment secret manager. If
GEO_OPERATION_TOKEN_SECRET is absent, the application creates apps/web/data/.operation-token-secret with mode 0600. That file must persist across restarts and instances, so an environment-managed secret is easier to operate in a replicated deployment.
Operator integrations
Configure the integrations used by the chosen workflows:
These are operator secrets. The worker resolves them from the process or operator root environment. Workspace credential storage is not consulted for OpenRouter, Exa, AgentMail, or PageSpeed.
Local operator mode
SetGEO_OPERATOR_MODE=local only for local development. Fallback access is accepted when:
- The environment is not production
- The request host is an exact loopback host
- The direct peer is loopback
Worker and metering boundary
The web application launches only allowlisted CLI jobs. A worker receives a signed operation token and calls metering endpoints over loopback to:- Heartbeat its lease
- Authorize the next provider call
- Record an idempotent cost event
- Seal its manifest
- Settle or release the reservation
Trusted proxy behavior
By default, the direct peer IP is the client IP. Forwarded IP headers are honored only whenGEO_TRUST_PROXY=1 and the direct proxy peer is loopback. This rule protects API key CIDR restrictions from spoofed forwarding headers.