Sentry (Optional)

Sentry support is optional in tx-agent-kit and is intended for error reporting only.

• If a DSN is not configured, Sentry does not initialize.
• Tracing is disabled in all runtime initializers (tracesSampleRate: 0).
• Env reads remain centralized in each runtime env module.

Runtime Env Variables

Local Development

Add optional keys to your local .env:

NEXT_PUBLIC_SENTRY_DSN=
WORKER_SENTRY_DSN=
EXPO_PUBLIC_SENTRY_DSN=

You can keep these empty for local development. The runtime initializers are no-ops when the value is blank.

1Password Templates

For staged environments, store DSNs in 1Password and reference them from env templates when needed:

# deploy/env/staging.env.template
# WORKER_SENTRY_DSN=op://<project-vault>/staging/WORKER_SENTRY_DSN

Web and mobile deployments are managed outside the compose stack; configure their DSNs in each platform/runtime environment with the same variable names listed above.

Runtime Wiring

• Web initializes Sentry in AppProviders using apps/web/lib/sentry.ts.
• Worker initializes and flushes Sentry in apps/worker/src/index.ts using apps/worker/src/observability/sentry.ts.
• Mobile initializes Sentry in apps/mobile/app/_layout.tsx using apps/mobile/lib/sentry.ts.

All three initializers are idempotent and safe to call multiple times.

Local Development with Spotlight

For local error visibility without a Sentry account, enable Sentry Spotlight. Set SENTRY_SPOTLIGHT=true in your .env and run the Spotlight sidecar — all three layers forward errors and traces to http://localhost:8969.