Rethink task storage

[drmikecrowe]

Hi folks, I continue to see weird issues like the screenshot below. I've been thinking a lot about tasks and where they live, and I have 2 key thoughts:

• We need to store tasks by project, whether at an absolute path or local path. This would involve adding a "project_id" or some other key to each request similar to how https://github.com/ingpoc/Claude/blob/main/lib/mcp/tools/InitSessionTool.ts does it. This will segment tasks by project
• I did a design review (well, Claude did) of this, and one of the suggestions it had was semaphore locking of the json/yaml file. The more I work with a single file, the more I think that is the wrong strategy. I think that locking my be contributing to the screenshot below.
• Here's what I think we should also support, a folder based hierarchy:

flowchart LR
    tasks/ --> projectA/
    tasks/ --> projectB/
    projectA/ --> todo[todo/]
    projectA/ --> done[done/]
    projectA/ --> prompts.yaml
    projectB/ --> E[...]
    todo --> T2[task-002/]
    done --> T1[20250917035500-task-001/]
    T1 --> T1T[task.yaml]
    T1 --> T1S1[subtask-001.yaml]
    T1 --> T1S2[subtask-002.yaml]
    T2 --> T2T[task.yaml]
    T2 --> T2S1[subtask-001.yaml]
    T2 --> T2S2[subtask-002.yaml]

Loading

[mentatbot]

If you would like me to solve this issue, either tag me in a comment or check this box:

• Solve Issue

_{You can disable automatic comments on my settings page}