{"version":"2.1.287","anchor":"cowork-skills-and-explain-usage-enabled-in-more-contexts","canonical_anchor":"cowork-skills-and-explain-usage-enabled-in-more-contexts","heading":"Cowork setup and \/explain-usage no longer limited to the remote Cowork entry point","tier":"notice","area":"Cowork","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287\/e\/cowork-skills-and-explain-usage-enabled-in-more-contexts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.287","markdown":"### Cowork setup and \/explain-usage no longer limited to the remote Cowork entry point\n\nThe Cowork guided setup and \/explain-usage were available only when Claude Code started as remote Cowork; they now follow a different check\n\n**Unclear.** It is not clear what the new check tests, so where these commands now appear is unknown.\n\n**What**\n\nThe `setup-cowork` command and its matching skill (a packaged set of instructions Claude can use), described as a guided setup to pick a role, install a plugin, try a skill and connect tools, used to be turned on only when the `CLAUDE_CODE_ENTRYPOINT` environment variable was `remote_cowork`. They now depend on a different check instead.\n\n`\/explain-usage` uses the same check. In one of the cases it covers, it now builds its prompt from the messages in the current session rather than from the saved transcript file.\n\n**Why**\n\nThese commands may now show up in places other than a remote Cowork session.\n\n- Area: Cowork\n- Names: `setup-cowork`, `\/explain-usage`, `CLAUDE_CODE_ENTRYPOINT`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5"}