bug: cannot update subtask status #65

New issue

Closed

opened 2025-10-14 15:40:17 -06:00 by navan · 0 comments

navan commented

2025-10-14 15:40:17 -06:00

Owner

Originally created by @carosellaja1 on 9/25/2025

Description

Upon updating to 0.27.0 i encountered this issue, then reverted to 0.26.0 and i could set subtask statuses again. The issue is still present in the new 0.27.1 release.

Claude code and cursor agent both seem to be unable to update subtask statuses as well. the command fails when cursor agent attempts. Claude code seems to think it successfully changes the subtask status but running task-master show 21 shows me all the subtasks are still marked pending.

Steps to Reproduce

Install task-master-ai@0.27.1 globally
Add tasks, analyze-complexity (with research), expand the subtasks, then attempt to individually change the subtask statuses. Can attempt via CLI, claude code, or via mcp with any IDE integrated agent.

Expected Behavior

Subtask should have its status set to the new status, and show that status in task-master list or show commands output

Actual Behavior

Taskmaster throws an error, does not update status. (Claude Code: Taskmaster seems to return that it successfully ran the tool call, but it does not update the status)

Screenshots or Logs

Here is my console input:

$ task-master set-status --id=21.1 --status=done

Console output:

|_   _|_ _ ___| | __ |  \/  | __ _ ___| |_ ___ _ __ 
   | |/ _` / __| |/ / | |\/| |/ _` / __| __/ _ \ '__|
   | | (_| \__ \   <  | |  | | (_| \__ \ ||  __/ |   
   |_|\__,_|___/_|\_\ |_|  |_|\__,_|___/\__\___|_|   
                                                     
by https://x.com/eyaltoledano
╭────────────────────────────────────────────╮
│                                            │
│   Version: 0.27.1   Project: Task Master   │
│                                            │
╰────────────────────────────────────────────╯

Failed to update task 21.1: Subtask status updates not yet supported in API storage

Environment

Task Master version: 0.27.1
Node.js version: 22.18.0
Operating system: Ubuntu
IDE (if applicable): Cursor

Additional Context

This issue is not present in 0.26.0 release, only in 0.27.0 and 0.27.1

*Originally created by @carosellaja1 on 9/25/2025* ### Description Upon updating to 0.27.0 i encountered this issue, then reverted to 0.26.0 and i could set subtask statuses again. The issue is still present in the new 0.27.1 release. Claude code and cursor agent both seem to be unable to update subtask statuses as well. the command fails when cursor agent attempts. Claude code seems to think it successfully changes the subtask status but running task-master show 21 shows me all the subtasks are still marked pending. ### Steps to Reproduce 1. Install task-master-ai@0.27.1 globally 2. Add tasks, analyze-complexity (with research), expand the subtasks, then attempt to individually change the subtask statuses. Can attempt via CLI, claude code, or via mcp with any IDE integrated agent. ### Expected Behavior Subtask should have its status set to the new status, and show that status in task-master list or show commands output ### Actual Behavior Taskmaster throws an error, does not update status. (Claude Code: Taskmaster seems to return that it successfully ran the tool call, but it does not update the status) ### Screenshots or Logs Here is my console input: ```bash $ task-master set-status --id=21.1 --status=done ``` Console output: ```bash |_ _|_ _ ___| | __ | \/ | __ _ ___| |_ ___ _ __ | |/ _` / __| |/ / | |\/| |/ _` / __| __/ _ \ '__| | | (_| \__ \ < | | | | (_| \__ \ || __/ | |_|\__,_|___/_|\_\ |_| |_|\__,_|___/\__\___|_| by https://x.com/eyaltoledano ╭────────────────────────────────────────────╮ │ │ │ Version: 0.27.1 Project: Task Master │ │ │ ╰────────────────────────────────────────────╯ Failed to update task 21.1: Subtask status updates not yet supported in API storage ``` ### Environment - Task Master version: 0.27.1 - Node.js version: 22.18.0 - Operating system: Ubuntu - IDE (if applicable): Cursor ### Additional Context This issue is not present in 0.26.0 release, only in 0.27.0 and 0.27.1