{"version":"2.1.273","anchor":"usage-command-result-gains-a-structured-payload","canonical_anchor":"usage-command-result-gains-a-structured-payload","heading":"\/usage results now include a structured usage_report","tier":"notice","area":"Usage","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/usage-command-result-gains-a-structured-payload","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### \/usage results now include a structured usage_report\n\nThe \/usage command's transcript message can now carry a structured usage_report alongside its text\n\n**What**\n\nWhen the `\/usage` slash command runs, the synthetic assistant message that delivers the result can now carry a structured `usage_report` object, in addition to the existing markdown text. It includes session totals, plan usage rows, and extra-usage spend, and sits alongside the existing `context_usage` and `local_command_run` fields on the message.\n\n**Why**\n\nThis lets remote clients render usage information as a proper card or widget instead of having to parse it back out of markdown text.\n\n- Area: Usage\n- Names: `\/usage`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}