Repository navigation
Safer retries for writes
Transient gateway errors (502/503/504) are now retried only for reads (GET/HEAD). A failed POST/PUT/PATCH/DELETE is no longer replayed automatically, because the server may have applied it already and a replay can create duplicates. Explicit 429 rate-limit rejections are still retried with backoff. Check the remote state before you repeat a failed write. Thanks @laurenz-seifried (#170).
Attachment uploads now go through the same path: they wait for the rate limiter, retry on 429, and are not replayed after a gateway error. Gateway retries of reads no longer log as "Rate limited".
cup attach <taskId> ./report.pdfcup auth exits 1 on failure in JSON mode
cup auth --json (and CU_OUTPUT=json cup auth) now exits with code 1 when authentication fails. stdout still contains the JSON result with authenticated: false (#170).
cup auth --json || echo "token invalid"Smaller, easier-to-find agent skill
SKILL.mddrops table column padding: 107 KB -> 33 KB of agent context with the same content.- The skill description now also triggers on ClickUp Docs, Chat, views, webhooks, export, and workspace structure (spaces, folders, lists, templates).
- Documents
cup views --space/--folder/--workspace,cup attach-get --output, andcup skill --path/--print.
cup skill # refresh the installed skillDependencies
vitest 5 (with vite as an explicit dev dependency), eslint 10.12, typescript-eslint 8.71, prettier 3.9.9, dotenv 18, chalk 6.0.1, @inquirer/prompts 8.7.2, tsx, @types/node.
1511 unit tests.
Full Changelog: v1.46.1...v1.46.2