CLIDE CLIDE's monitoring: its activity log and OpenTelemetry endpoint. CLIDE Monitoring CLIDE with Settings → Monitoring Write the activity log Enabled: CLIDE writes one JSON line per event to its log file, and the person can't turn it off. Disabled: it writes none, and the person can't turn it on. Not configured: the person chooses in Settings → Monitoring. The log is %LOCALAPPDATA%\CLIDE\Logs\monitor.jsonl unless a folder is set below. Folder for the activity log The folder CLIDE writes monitor.jsonl in, instead of %LOCALAPPDATA%\CLIDE\Logs: a full path, such as one your log collector already reads. Environment variables aren't expanded. Send events to an OpenTelemetry endpoint An http or https address of an OpenTelemetry collector or service (OTLP over HTTP, JSON). CLIDE sends every event to its /v1/logs and each run to its /v1/traces. A key goes in the headers below, never in the address. Headers for the OpenTelemetry endpoint Headers CLIDE sends with every request to the endpoint, for a service that wants a key: the value name is the header's name (x-api-key), the value its value. Record values Enabled: what people type or choose in a tool's form, the file paths runs read and write, and full web addresses are recorded as they are. Disabled: they're recorded as [REDACTED], counted, or by host only. Not configured: the person chooses (off unless they turn it on). Environment variables, what runs print, what tools make and what people ask an AI agent are never recorded. Folder Address Headers (name, then value)