Problem
There is no documented way to reopen a completed task via gws tasks. The Google Tasks API supports setting status: "needsAction" to reopen a task, but the CLI does not expose this.
Additionally, I observed a behavior where calling gws tasks update <list-id> <task-id> --due ... --notes ... (without explicitly invoking complete) appears to have toggled the task's status to completed. I cannot reproduce a deliberate complete call in my command history that would explain it. Documenting this here in case it is a known issue or quirk worth investigating.
What I tried
gws tasks update <list-id> <task-id> --title "..." → returns success but task status remains completed.
gws tasks update <list-id> <task-id> --due "..." → same.
- There is no
gws tasks reopen or --status flag visible in gws tasks update --help.
Workaround today: delete the closed task and create a new one with the same content (loses task ID and any external references).
Suggested fixes
- Most useful: add a
gws tasks reopen <list-id> <task-id> command (mirror of gws tasks complete) that sets status: "needsAction" via the Tasks API.
- Alternatively, expose
--status needsAction|completed on gws tasks update.
- Document whether
gws tasks update is supposed to preserve the existing status field, and investigate the case where it appeared to flip a task to completed without an explicit complete invocation.
Environment
- macOS Darwin 25.3.0
- gws version: please run
gws version if reproducing
- Date observed: 2026-05-07
Problem
There is no documented way to reopen a completed task via
gws tasks. The Google Tasks API supports settingstatus: "needsAction"to reopen a task, but the CLI does not expose this.Additionally, I observed a behavior where calling
gws tasks update <list-id> <task-id> --due ... --notes ...(without explicitly invokingcomplete) appears to have toggled the task's status tocompleted. I cannot reproduce a deliberatecompletecall in my command history that would explain it. Documenting this here in case it is a known issue or quirk worth investigating.What I tried
gws tasks update <list-id> <task-id> --title "..."→ returns success but task status remainscompleted.gws tasks update <list-id> <task-id> --due "..."→ same.gws tasks reopenor--statusflag visible ingws tasks update --help.Workaround today: delete the closed task and create a new one with the same content (loses task ID and any external references).
Suggested fixes
gws tasks reopen <list-id> <task-id>command (mirror ofgws tasks complete) that setsstatus: "needsAction"via the Tasks API.--status needsAction|completedongws tasks update.gws tasks updateis supposed to preserve the existing status field, and investigate the case where it appeared to flip a task tocompletedwithout an explicit complete invocation.Environment
gws versionif reproducing