| name | reclaim-tasks |
| description | Manage tasks in Reclaim.ai calendar scheduling app. Use when creating, updating, listing, completing, or deleting Reclaim tasks, or working with calendar scheduling, task priorities, time blocking, or task duration management. Use when this capability is needed. |
| metadata | {"author":"benjaminjackson"} |
Reclaim Tasks
Manage CRUD operations for tasks in Reclaim.ai using the reclaim CLI.
Installation Check
IMPORTANT: If a reclaim command fails with a "binary not found" or "command not found" error:
- Check if the CLI is installed:
which reclaim
- If not installed, install it automatically:
gem install reclaim
-
If automatic installation fails, inform the user that they need to install Ruby first, then run gem install reclaim.
-
After installation, verify it works:
reclaim --help
Do not preemptively check for installation - only perform these steps when a command actually fails.
Mandatory Confirmation Workflow
CRITICAL: For ALL write operations (create, update, complete, delete), you MUST:
- Parse the user's request and construct the
reclaim command
- Use the AskUserQuestion tool to show the command and get confirmation
- Only execute the command after user approval
Read operations (list, get, list-schemes) can execute immediately without confirmation.
Quick Command Reference
Read Operations (no confirmation needed)
reclaim
reclaim list active
reclaim list completed
reclaim list overdue
reclaim get TASK_ID
reclaim list-schemes
Write Operations (REQUIRE confirmation)
reclaim create --title "TITLE" [OPTIONS]
reclaim update TASK_ID [OPTIONS]
reclaim complete TASK_ID
reclaim delete TASK_ID
Common Options
--title TITLE - Task title--due DATE - Due date (YYYY-MM-DD or YYYY-MM-DDTHH:MM:SS, or "none" to clear)--priority P1|P2|P3|P4 - Task priority--duration HOURS - Duration in hours (0.25 = 15min, 1.5 = 90min)--split [CHUNK_SIZE] - Allow task splitting (optional min chunk size)--defer DATE - Start after this date (or "none" to clear)--start DATE - Specific start time (or "none" to clear)--time-scheme SCHEME - Time scheme ID or alias (work, personal, etc.)--notes TEXT - Task notes/description
Example Workflow with Confirmation
User request: "Create a task called 'Write proposal' due Friday, P1 priority, 3 hours"
Your response:
- Construct command:
reclaim create --title "Write proposal" --due 2025-11-07 --priority P1 --duration 3
- Use AskUserQuestion to confirm:
Ready to create this Reclaim task:
Command: reclaim create --title "Write proposal" --due 2025-11-07 --priority P1 --duration 3
This will create a P1 task with 3 hours duration due on 2025-11-07.
Proceed?
- After approval, execute the command
Additional Resources
Date Formats
- Standard:
YYYY-MM-DD (e.g., 2025-11-07)
- With time:
YYYY-MM-DDTHH:MM:SS (e.g., 2025-11-07T14:30:00)
- Clear date:
none, clear, or null
Priority Levels
P1 - Highest priorityP2 - High priorityP3 - Medium priorityP4 - Low priority
Time Scheme Aliases
work, working hours, business hours → Work time schemespersonal, off hours, private → Personal time schemes
Understanding Task Status
CRITICAL: The reclaim list active output shows status COMPLETE with checkmarks (✓) for tasks that are
done scheduling (past their assigned time blocks), NOT tasks that are marked as "done".
- Status: COMPLETE in API (✓ symbol) = Task's scheduled time is in the past
- Status: SCHEDULED (○ symbol) = Task's scheduled time is in the future
A task is only truly "done" after you run reclaim complete TASK_ID. Until then, all tasks in
the active list are open work items, regardless of checkmarks or "COMPLETE" status in the API
response.
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
