Releases: triptechtravel/clickup-cli
Releases · triptechtravel/clickup-cli
v0.11.0
v0.10.2
v0.10.1
v0.10.0
v0.9.2
v0.9.1
v0.9.0
What's New
Task discovery improvements
task recentnow filters out tasks from archived folders- New
--sprintflag ontask recentto show only sprint folder tasks clickup sprint currentadded to quick-actions footers for better discoverability
Search improvements
- New
--exactflag ontask searchto suppress fuzzy matches - Clear separator message when showing fuzzy results: "No exact matches. Showing fuzzy results (use --exact to suppress):"
- Sprint hint in no-results output
Status validation in create/edit
task create --statusnow validates against the list's space statuses using fuzzy matchingtask edit --statusnow validates against the task's space statuses using fuzzy matching- Shows a warning when fuzzy-matched (e.g.,
Status "prog" matched to "in progress") - Returns an error with available statuses if no match found
Refactoring
- Extracted
matchStatusto sharedcmdutil.MatchStatusandcmdutil.ValidateStatus - New
cmdutil.FetchSpaceStatusesfor reusable space status fetching
Full Changelog: v0.8.1...v0.9.0
v0.8.1
Fix: Real @mentions in comments
clickup comment add now resolves @username to real ClickUp @mentions that trigger notifications.
What changed
- @mention resolution: When your comment body contains
@username, the CLI looks up workspace members (same asclickup member list) and replaces plain-text@references with ClickUp's structured tag format. This means teammates actually get notified. - Case-insensitive matching:
@isaac,@Isaac, and@ISAACall resolve to the same person. - Greedy matching: Longer usernames are matched first to avoid partial matches (e.g., "Isaac Rowntree" matches before "Isaac").
- Word-boundary aware:
@isaacwon't accidentally match a member named "isaacs". - Graceful fallback: If no
@is present, or usernames can't be resolved, comments are sent as plain text (same as before). - Feedback on stderr: The CLI prints
Mentioning @usernamefor each resolved mention so you can verify.
Discoverability
All quick-actions footers that reference comment add now hint at @mention support:
Comment: clickup comment add abc123 "@user text" (supports @mentions)
Example
# Mention teammates — they'll get a real ClickUp notification
clickup comment add abc123 "Hey @Isaac can you review this?"
# Multiple mentions
clickup comment add abc123 "@Alice @Bob this is ready for QA"Full Changelog: v0.8.0...v0.8.1
v0.8.0
What's New
Quick-actions footers on every command
Every command that produces output now prints a contextual "Quick actions" footer showing what you can do next — making the CLI fully discoverable without needing --help.
Examples:
- After
clickup task view: suggests edit, status set, comment add, link pr - After
clickup task create: suggests view, edit, link pr, comment - After
clickup link pr: suggests view, sync, status set - After
clickup auth login: suggests space select, task recent, inbox
--json/--jq support on all mutation commands
task create and task edit now support --json and --jq flags, so every command that produces meaningful output can return structured JSON for scripting and AI agents.
# Create a task and get the ID back
clickup task create --list-id 12345 --name "Fix bug" --json --jq '.id'
# Edit and get the updated task
clickup task edit CU-abc123 --status "done" --jsonCommands with new footers (20 commands)
| Category | Commands |
|---|---|
| Task | view, list, search, recent, activity, create, edit |
| Time | time log, time list |
| Comment | list, add |
| Sprint | current, list |
| Link | pr, sync |
| Status | set, list |
| Other | space list, member list, field list, inbox, auth login |
Docs
- Updated commands.md with new --json/--jq flags for create and edit
- Added general discoverability note about footers and JSON support
- Regenerated 52 reference pages