{"version":"2.1.232","anchor":"structured-context-usage-alongside-the-context-table","canonical_anchor":"structured-context-usage-alongside-the-context-table","heading":"Structured context_usage alongside the \/context table","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/structured-context-usage-alongside-the-context-table","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Structured `context_usage` alongside the \/context table\n\nThe streaming schema carries an optional `context_usage` field so tools skip parsing the markdown table.\n\n**What**\n\nThe streaming message schema adds an optional `context_usage` field carrying a machine-readable twin of the \/context breakdown, so tools consuming the stream no longer have to parse the markdown table.\n\n**Details**\n\n- It sits at the wrapper level, as a sibling of `message.content` on the synthetic assistant message that delivers the table.\n- Deliberately not replayed back to the model.\n- The markdown table remains canonical for clients that do not receive the field.\n\n**Evidence**\n\n`Structured twin of the \/context report, carried on the synthetic assistant message that delivers the markdown table.`\n\n- Area: SDK\n- Names: `context_usage`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}