You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(telemetry): materialize resolved telemetry.enabled in /api/v1/config (#681)
Telemetry is opt-out (default enabled), but DefaultConfig leaves the
Telemetry field nil and Enabled is a pointer with omitempty. On a fresh
install the /api/v1/config response omitted the telemetry key entirely,
so the web UI (SettingField !!modelValue) and macOS (?? false) coerced
the missing bool to false and displayed telemetry as DISABLED — even
though Config.IsTelemetryEnabled() and the CLI correctly reported it
enabled.
Fix at the contract/response boundary: mirror IsTelemetryEnabled() into
a copy of the config before marshaling so telemetry.enabled is always
present, without mutating the shared config or changing the Go
default-true logic. One server-side fix covers both UI clients.
Related #MCP-2477
0 commit comments