google_tasks
Google Tasks
Everything runs through hatch_gws_cli tasks <resource> <method>. The two resources are tasklists and tasks, so a task command names tasks twice — hatch_gws_cli tasks tasks list (service tasks, resource tasks, method list). Parameters go in a --params JSON object, and creates and edits add a --json request body. The flows below give the exact command for each job, so use them verbatim; run hatch_gws_cli tasks <resource> --help for a command's flags, and hatch_gws_cli schema tasks.tasks.insert (and so on) for a method's --params/--json shape.
A task's due is a date given as an RFC3339 timestamp like 2026-04-16T00:00:00Z, but Google Tasks uses only the date — there is no time of day and no reminders. The default task list is @default.
Connecting
Tasks needs a one-time connect before commands return data. Run hatch_gws_cli tasks status. If it is not connected, post the exact connect_url it returns as [Connect Google Tasks](<connect_url>) and wait for the user to tap it. Don't invent a URL, send the user to Settings, or ask for credentials.
To disconnect, run hatch_gws_cli tasks disconnect and post its disconnect_url as [Disconnect Google Tasks](<disconnect_url>).
If a command reports an auth failure or not-connected, rerun status and follow the link it returns. If status is unavailable, say Google Tasks isn't available on this device and stop. Auth flows only through status and disconnect, with no hand-authored credential files or raw gws auth.