Open-source tree sync 02d9359435d0 → 5da6962e4adb (still product 0.2.112): /privacy opens Settings instead of taking opt-in/out args, and MCP servers gain CLI enable/disable.
Changelog
[changed] /privacy no longer accepts opt-in / opt-out arguments; it opens Settings on Coding data, retention, and training, where you choose Opt in or Opt out (takes no arguments).
[new] grok mcp enable and grok mcp disable persist personal on/off state for local/TOML, compat-sourced, plugin, and legacy managed MCP servers without restarting.
[changed] On team accounts or when Zero Data Retention is on, the coding-data row shows ZDR or · Admin Managed instead of opening the chooser; only team admins can change sharing when allowed.
[changed] grok mcp list marks disabled servers with (disabled) alongside project-scoped (project) labels.
[changed] In-product legal links point at the privacy policy and terms of service pages separately.
Agent & tools
/privacy — opens the Settings row for coding-data sharing; does not touch [features] telemetry, trace_upload, or external OTEL.
MCP CLI — grok mcp enable <name> / grok mcp disable <name> write user-scope state (disabled_mcp_servers / [mcp_servers.<name>].enabled). Enable can clear a sticky project enabled = false; disable does not rewrite project configs. Unknown names exit 1. Gateway connectors remain TUI/Space-only via /mcps.
Docs
Authentication, Configuration, and Monitoring usage — describe coding-data sharing as the Settings row /privacy opens, separate from telemetry knobs.
