Skip to main content
Use configuration to control where events are sent, what content is recorded, and how safely the SDK delivers events in production.

When to use this

Use this page when you need to:
  • Send events to Lynx Cloud or a local backend
  • Attach workspace, agent, version, or environment metadata
  • Avoid sending raw prompts or responses
  • Tune delivery timeouts, queues, and circuit breaker behavior

Basic setup

endpoint defaults to https://api.lynxops.co. Use a custom endpoint only for local development or self-hosted deployments.

Issue reporting

Issue reporting is disabled until issueReporting.enabled is explicitly set to true. Runtime configuration can provide prompts and firewall policies, but it does not enable issue reporting by itself.

Capture options

Capture modes

Delivery options

Environment variables

The default lynx export reads configuration from environment variables.

Security note

Depending on your settings, Lynx may receive prompts, tool arguments, and model responses. Avoid sending secrets, credentials, access tokens, or private keys. The SDK masks common sensitive keys, but you should still avoid passing secrets into prompts or tool payloads. Use metadata-only, captureInput: false, or captureOutput: false when raw content should not be sent.

Next steps