TickTick CLI

**Judgement:** Solid and feature-complete TickTick CLI well-suited for automation and AI agents once OAuth is configured, with good JSON support and batch operations. Best for users who already rely on TickTick and want programmable task/project management. **Strengths:** - Covers core task and project operations (create/list/update/complete/abandon) plus batch abandon via TickTick’s batch API. - Designed for agent use: consistent CLI interface, `--json` output, and recommendations to use project IDs and task IDs. - Handles OAuth2 with token refresh and basic rate-limit awareness; supports headless/manual auth flow. **Key Risks / Limitations:** - Initial OAuth app registration and authentication require manual steps and user involvement; not plug-and-play for new users. - Credentials and tokens are stored in plaintext on disk (even if with restrictive permissions), which is a local security risk if the host is compromised. - TickTick API rate limits (100 req/min, 300/5min) plus multi-call operations mean aggressive bulk operations can still hit limits. - Some advanced TickTick features (e.g., focus time, habits) are not supported by the underlying API and thus unavailable. **Recommended Scenarios:** - Power users and developers who already use TickTick and want to integrate it into automation, scripts, or AI workflows. - Agents that need to reliably manage tasks/projects with structured JSON I/O, particularly when using IDs to avoid ambiguity. - Systems that periodically sync or clean up TickTick data (e.g., batch abandoning old tasks) while staying within API limits. **Less Ideal For:** - Users unwilling or unable to perform the TickTick Developer app setup and OAuth flow. - Highly security-sensitive environments where storing OAuth credentials in plaintext on disk is not acceptable.