{"version":"2.1.236","anchor":"request-telemetry-records-whether-you-are-on-the-default-mod","canonical_anchor":"request-telemetry-records-whether-you-are-on-the-default-mod","heading":"Request telemetry records whether you are on the default model and effort","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/request-telemetry-records-whether-you-are-on-the-default-mod","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Request telemetry records whether you are on the default model and effort\n\nEach response now reports whether you were on the default model and effort, plus compression outcome.\n\n**What**\n\nEach assistant response now reports `is_default_model`, `default_model`, `is_default_effort` and `default_effort_level`, letting Anthropic separate traffic on the shipped defaults from explicitly chosen models. A helper resolves the model actually in use and compares it against the automatic model set and the configured default; when the comparison is ambiguous the fields are omitted rather than guessed. The same event also records `requestBodyCompression`, the gzip outcome for that request. No gate, and nothing visible in the app.\n\n**Evidence**\n\n`...(D !== void 0 && { is_default_model: D }),`, `defaultEffortLevel`, `default_effort_level`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}