{"version":"2.1.260","anchor":"claude-rm-can-now-force-discard-unpushed-commits","canonical_anchor":"claude-rm-can-now-force-discard-unpushed-commits","heading":"claude rm can now force-discard unpushed commits","tier":"use","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/claude-rm-can-now-force-discard-unpushed-commits","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### `claude rm` can now force-discard unpushed commits\n\nclaude rm can now force-delete a worktree with unpushed commits using a new flag.\n\n`claude rm <id>` gains a `--discard-unpushed <commit>@<worktree-id>` option to delete a background session's worktree even when it has unpushed commits or uncommitted changes, provided the worktree is still at the commit last reported. When `claude rm` refuses to delete a worktree with unpushed work, it now reports the exact `<commit>@<worktree-id>` value to pass to this new flag.\n\n- Area: Sessions\n- Names: `claude rm`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}