{"version":"2.1.257","anchor":"context-usage-rpc-now-accepts-a-detail-parameter","canonical_anchor":"context-usage-rpc-now-accepts-a-detail-parameter","heading":"Context-usage RPC now accepts a detail parameter","tier":"internal","area":"Context Usage","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/context-usage-rpc-now-accepts-a-detail-parameter","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### Context-usage RPC now accepts a detail parameter\n\nThe bridge's context-usage handler forwards a detail argument, so remote clients can ask for coarser reporting.\n\nThe bridge's `onGetContextUsage` handler now accepts an optional `detail` argument and forwards it through to context usage collection, allowing more granular usage reporting requests from a remote client.\n\n- Area: Context Usage\n- Names: `detail`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}