Old tasks deleting without pressing the delete trash bin

[m-check1B]

Which version of the app are you using?

v3.7.8

Which API Provider are you using?

OpenRouter

Which Model are you using?

any

What happened?

After going back to work, let say after restart or simply next time, listing in to the correct directory, then pressing the tas I want to revive - that task very often delete itself not revives. When pressed on the body of the task panel not on the trash icon. There is a bug that somehow misidentifies the pressing on the task banner for pressing on the bin. Happens very often but not every time. Sometimes the task is revived.

Steps to reproduce

After going back to work, let say after restart or simply next time, listing in to the correct directory, then pressing the tas I want to revive - that task very often delete itself not revives. When pressed on the body of the task panel not on the trash icon. There is a bug that somehow misidentifies the pressing on the task banner for pressing on the bin. Happens very often but not every time. Sometimes the task is revived.

Relevant API REQUEST output

Additional context

No response

[hannesrudolph]

Did you happen to uninstall the plugin, restart vscode, and then reinstall the plugin to find this a problem?

Do you have any further steps to repro?

[hannesrudolph]

I suspect that somehow the <globalStoragePath>/tasks/<taskId> for the specific task is getting deleted.

Roo deletes tasks automatically when you click it and the /tasks/ cannot be found. The following image is the code of this functionality from ClineProvider.ts

Also, when you uninstall the plugin, restart vscode, and reinstall the plugin, the task list is still stored in global state but the tasks in /tasks/ are all gone. This will give the person the false sense that their task list is still intact when it is not and when they click on tasks they will vanish/delete using the above functionality highlighted in ClineProvider.ts

1. When plugin is installed should the task history be cleared? I am not sure best practice. If so we should implement that. Perhaps the list of tasks should be only temporarily stored in the global state and repopulate based on the contents of /tasks/ during plugin initialization.
2. Should we be implementing more graceful handling when someone clicks the missing task instead of just having it vanish from the list with no feedback?
   @mrubens