{"version":"2.1.271","anchor":"context-data-now-exposes-deferredloaded-flags-and-richer-b","canonical_anchor":"context-data-now-exposes-deferredloaded-flags-and-richer-b","heading":"\/context data now exposes deferred\/loaded flags and richer breakdown","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/context-data-now-exposes-deferredloaded-flags-and-richer-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### \/context data now exposes deferred\/loaded flags and richer breakdown\n\n\/context data sent to plugins now includes deferred and loaded status flags plus a richer breakdown\n\n**What**\n\nThe data that `\/context` (which visualizes current context window usage as a colored grid) hands off to a plugin's `contextData` call is now shaped into a more structured object. It includes:\n\n- categories, each with an `isDeferred` flag\n\n- grid rows and memory files\n\n- MCP tools, each with an `isLoaded` flag\n\n- agents\n\n- optionally slash commands, skills, the auto-compact threshold, and API usage\n\n**Why**\n\nThis gives plugins a more detailed and structured view of what's using up context, including whether a given category or tool is deferred or already loaded, rather than a flatter summary.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}