.env.example

# AgentEnv environment variables. A reference: agent-env reads the process
# environment and never loads this file, so export what you need yourself
# (direnv, `set -a; . ./.env; set +a`, your shell profile, your supervisor).

# The config file agent-env reads. Everything stage-shaped lives in it —
# store coordinates, model, task steps, providers.
# AGENT_ENV_CONFIG=/path/to/config.toml

# Stage: read by an installed platform plugin, if any, to pick which of its
# bundled per-stage files AGENT_ENV_CONFIG lands on; agent-env itself reads
# nothing here. A bare install has no stages — set AGENT_ENV_CONFIG.
AGENT_ENV_ENVIRONMENT=dev

# Control-plane document store backend:
# - "local" (or unset): stdlib SQLite at ~/.local/state/agent-env/document_store/documents.db (no external infra)
# - MongoDB: configure a [stores.document] table in config.toml (no built-in coordinates)
# AGENT_ENV_DOCUMENT_STORE=local

# Object (blob) store backend:
# - "local" (or unset): local filesystem at ~/.local/state/agent-env/object_store/ (no external infra)
# - a hosted backend (S3, Cloud Storage): configure a [stores.object] table in config.toml (no built-in coordinates)
# AGENT_ENV_OBJECT_STORE=local

# Image (registry) store backend:
# - "local" (or unset): local OCI registry, e.g. registry:2 at localhost:5000 (no external infra)
# - a hosted registry (ECR): configure a [stores.image] table in config.toml (no built-in coordinates)
# AGENT_ENV_IMAGE_STORE=local

# Secret store backend (what secret: references in config resolve through):
# - "local" (or unset): process env vars, or a flat YAML/JSON file via [stores.secret] in config.toml
# - a hosted secret manager (AWS Secrets Manager, Google Cloud Secret Manager): configure a [stores.secret] table (no built-in coordinates)
# AGENT_ENV_SECRET_STORE=local