Conversation
Add `tw thread delete <thread-ref>` command with ownership validation, `--yes` confirmation flag, and `--dry-run`/`--json` support. Closes #130 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
doistbot
left a comment
There was a problem hiding this comment.
This PR introduces the tw thread delete command complete with confirmation safeguards, dry-run capabilities, and ownership validation, which is a great addition to our thread management tools. The careful approach to handling early spinner exits and verifying permissions ensures a safe foundation for destructive actions. A few adjustments have been flagged regarding the ordering of validation checks—specifically moving the dry-run check before network calls and prioritizing the public channel guard—along with refining the --json flag's behavior during preview and unconfirmed states to guarantee reliable scriptability.
- Move assertChannelIsPublic before ownership check for consistency - Error with non-zero exit when --json used without --yes Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
## [2.23.0](v2.22.1...v2.23.0) (2026-04-03) ### Features * add thread deletion support ([#133](#133)) ([eed878c](eed878c))
|
🎉 This PR is included in version 2.23.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Summary
tw thread delete <thread-ref>command with--yesconfirmation,--dry-run, and--jsonflagsprocess.exitCode = 1+ return (notprocess.exit(1)) to avoid leaving the early spinner stuckCloses #130
Test plan
npm run type-checkpassesnpm test)npm run lint)npm run check:skill-sync)tw thread delete <own-thread-url>shows confirmation prompttw thread delete <own-thread-url> --yesdeletes the threadtw thread delete <other-user-thread-url> --yesshows ownership error🤖 Generated with Claude Code