{"version":"2.1.317","anchor":"onboarding-guide-tool-delete-semantics-clarified","canonical_anchor":"onboarding-guide-tool-delete-semantics-clarified","heading":"Deleting a team onboarding guide now needs its short code","tier":"notice","area":"Team Onboarding","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/onboarding-guide-tool-delete-semantics-clarified","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Deleting a team onboarding guide now needs its short code\n\nThe onboarding guide tool no longer deletes your org's newest guide when no `short_code` is given; it lists your guides and asks which one\n\n**Unclear.** It is unclear whether the tool itself now behaves this way or only its description changed.\n\n**What**\n\nClaude Code has a tool for sharing and managing team onboarding guides. Each guide has a short code, called `short_code`, that identifies it. The tool's delete mode has changed:\n\n- Delete without a `short_code` no longer removes the org's current guide. Nothing is deleted. The tool lists your guides, and Claude is told to ask you which one to delete and then call again with its `short_code`.\n\n- The description of `short_code` now says delete requires it.\n\n- When the server finds no guide with that code, the tool says it was already deleted, or the code is wrong.\n\n- Delete calls now show as `delete <short_code>`, and the code is included in the tool's input to the automatic safety check, so it is visible which guide is being removed.\n\n**Why**\n\nBefore, a delete with no code quietly removed whichever guide was current. Now a guide is only deleted when it is named, which makes deleting the wrong one by accident much less likely.\n\n- Area: Team Onboarding\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}