{"version":"2.1.260","anchor":"advisor-command-reports-a-consent-pending-telemetry-state","canonical_anchor":"advisor-command-reports-a-consent-pending-telemetry-state","heading":"\/advisor command reports a 'consent_pending' telemetry state and per-session-only setting","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/advisor-command-reports-a-consent-pending-telemetry-state","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### \/advisor command reports a 'consent_pending' telemetry state and per-session-only setting\n\n\/advisor now tracks a pending-consent state and can be set for just the current session.\n\nThe `\/advisor` command's telemetry now distinguishes four states: `off`, a valid advisor choice, `consent_pending` for models that require consent, and `invalid`, instead of just reporting the raw name and a remote flag. `\/advisor` can also now set the advisor for the current session only in certain contexts, with messaging telling the user to run `\/advisor` in the terminal to change their persistent default.\n\n- Area: Elsewhere\n- Names: `\/advisor`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}