{"version":"2.1.271","anchor":"json-text-response-body-classification-message-reworded","canonical_anchor":"json-text-response-body-classification-message-reworded","heading":"\"json-text\" response-body classification message reworded","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/json-text-response-body-classification-message-reworded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### \"json-text\" response-body classification message reworded\n\nThe message for a \"json-text\" response body now says the JSON failed to parse, not that its content-type was wrong\n\n**What**\n\nWhen Claude Code labels a response body as \"json-text\", the explanation shown for that label now says the body looks like JSON but does not parse, rather than describing a mismatch between the content and its declared content-type.\n\n**Why**\n\nThis makes the message more accurate: the issue being flagged is that the text couldn't actually be parsed as JSON, not that its content-type header was wrong.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5"}