{"version":"2.1.287","anchor":"context-in-hosted-workers-omits-message-breakdown","canonical_anchor":"context-in-hosted-workers-omits-message-breakdown","heading":"\/context shows less detail in hosted worker sessions","tier":"notice","area":"Slash Commands","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/context-in-hosted-workers-omits-message-breakdown","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### \/context shows less detail in hosted worker sessions\n\nIn hosted worker sessions, \/context now leaves out the message breakdown, built-in and system tool lists, and system prompt sections\n\n**Unclear.** It is not clear which sessions count as hosted workers.\n\n**What**\n\n`\/context` shows how much of the conversation's working space (the context window) is in use. When the session is a hosted worker, meaning Claude Code is running on a hosted machine rather than on your own computer, the context-usage result now leaves out several parts:\n\n- the message breakdown (`messageBreakdown`)\n\n- the deferred built-in tools (`deferredBuiltinTools`)\n\n- the system tools (`systemTools`)\n\n- the system prompt sections (`systemPromptSections`)\n\nSessions that are not hosted workers are not affected.\n\n**Why**\n\nIf you use Claude Code in a hosted or remote session, `\/context` will show a shorter breakdown than you get locally, so these details will not appear there.\n\n- Area: Slash Commands\n- Names: `\/context`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5"}