starred/planning-with-files

Fork 0

mirror of https://github.com/OthmanAdi/planning-with-files.git synced 2026-04-26 08:26:01 +03:00

[GH-ISSUE #58] Is this still relevant after Claude did Tasks instead of TODOs? #39

New issue

Closed

opened 2026-03-03 18:50:11 +03:00 by kerem · 4 comments

kerem commented

2026-03-03 18:50:11 +03:00

Owner

Originally created by @gam-phon on GitHub (Jan 25, 2026).
Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/58

Thanks for your great library.

I have a quick question and sorry for asking this. Is this still relevant after Claude did Tasks instead of TODOs?

Article: We’re turning Todos into Tasks in Claude Code

Originally created by @gam-phon on GitHub (Jan 25, 2026). Original GitHub issue: https://github.com/OthmanAdi/planning-with-files/issues/58 Thanks for your great library. I have a quick question and sorry for asking this. Is this still relevant after Claude did Tasks instead of TODOs? [Article: We’re turning Todos into Tasks in Claude Code](https://x.com/trq212/status/2014480496013803643)

kerem closed this issue

2026-03-03 18:50:11 +03:00

kerem commented

2026-03-03 18:50:12 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 26, 2026):

Hi @gam-phon, great question!

Short Answer: Yes, planning-with-files is still 100% relevant.

Why They're Different

Feature	Claude Tasks (new)	planning-with-files
Storage	In-memory (session-based)	Persistent files on disk
Survives /clear	❌ No	✅ Yes
Cross-IDE	Claude Code only	10+ IDEs (Cursor, Gemini, Kiro, etc.)
Purpose	Track current todos	External working memory

The Key Difference

Claude Tasks (formerly TodoWrite) is for tracking what Claude plans to do in the current session. When the session ends or context fills up, it's gone.

planning-with-files is about persistent external memory — the Manus principle of "filesystem as working memory on disk." Your task_plan.md, findings.md, and progress.md survive across:

Session restarts
Context window clears (/clear)
IDE switches
Team handoffs

When to Use Each

Tasks: Quick tracking within a single session
planning-with-files: Multi-day projects, research tasks, anything you can't afford to lose

They complement each other — Tasks for short-term, planning-with-files for long-term persistence.

Thanks for asking! This clarifies the value proposition for others too.

Ahmad

@OthmanAdi commented on GitHub (Jan 26, 2026): Hi @gam-phon, great question! ## Short Answer: Yes, planning-with-files is still 100% relevant. ## Why They're Different | Feature | Claude Tasks (new) | planning-with-files | |---------|-------------------|---------------------| | **Storage** | In-memory (session-based) | **Persistent files on disk** | | **Survives /clear** | ❌ No | ✅ Yes | | **Cross-IDE** | Claude Code only | 10+ IDEs (Cursor, Gemini, Kiro, etc.) | | **Purpose** | Track current todos | **External working memory** | ## The Key Difference Claude Tasks (formerly TodoWrite) is for tracking what Claude plans to do **in the current session**. When the session ends or context fills up, it's gone. planning-with-files is about **persistent external memory** — the Manus principle of "filesystem as working memory on disk." Your `task_plan.md`, `findings.md`, and `progress.md` survive across: - Session restarts - Context window clears (`/clear`) - IDE switches - Team handoffs ## When to Use Each - **Tasks**: Quick tracking within a single session - **planning-with-files**: Multi-day projects, research tasks, anything you can't afford to lose They complement each other — Tasks for short-term, planning-with-files for long-term persistence. Thanks for asking! This clarifies the value proposition for others too. --- Ahmad

kerem commented

2026-03-03 18:50:12 +03:00

Author

Owner

@gam-phon commented on GitHub (Jan 26, 2026):

Hello Ahmed, nice to meet you. I am Yaser.

I think you use AI to generate the response ^_^ everyone is going this right now.

I think the comparing is wrong. It is doing this with Claude TODO not Claude Tasks. The new Tasks persist in Claude/tasks folder and work across many sessions and subagents and work after clear as well.

@gam-phon commented on GitHub (Jan 26, 2026): Hello Ahmed, nice to meet you. I am Yaser. I think you use AI to generate the response ^_^ everyone is going this right now. I think the comparing is wrong. It is doing this with Claude TODO not Claude Tasks. The new Tasks persist in Claude/tasks folder and work across many sessions and subagents and work after clear as well.

kerem commented

2026-03-03 18:50:12 +03:00

Author

Owner

@OthmanAdi commented on GitHub (Jan 26, 2026):

Hey Yaser, you were right - I owe you an apology.

That previous response was AI-generated and the comparison was wrong. You caught it.

Claude Tasks (the new Jan 2026 update) DO persist in ~/.claude/tasks/ as JSON files. They survive /clear, work across sessions, and even sync between sub-agents. I was comparing to the old TodoWrite which was memory-based - that's outdated info now.

So what's actually different now?

Claude Tasks:

Stored in Claude's folder (~/.claude/tasks/)
JSON format (not easy to read/edit)
Dependencies built-in (Task B waits for Task A)
Claude Code only

planning-with-files:

Stored in YOUR project directory
Markdown files you can actually read and edit
Committable to git
Works across 11+ IDEs (Cursor, Kiro, Gemini, Continue, etc.)

I'm actually working on a Tasks version that combines the best of both - stay tuned.

planning-with-files makes more sense if you:

Want visible markdown files in your project
Use multiple IDEs
Want to commit your planning to git
Like having a findings.md for research notes

Thanks for pushing back on this. Appreciate the honesty.

@gam-phon

@OthmanAdi commented on GitHub (Jan 26, 2026): Hey Yaser, you were right - I owe you an apology. That previous response was AI-generated and the comparison was wrong. You caught it. Claude Tasks (the new Jan 2026 update) DO persist in ~/.claude/tasks/ as JSON files. They survive /clear, work across sessions, and even sync between sub-agents. I was comparing to the old TodoWrite which was memory-based - that's outdated info now. So what's actually different now? **Claude Tasks:** - Stored in Claude's folder (~/.claude/tasks/) - JSON format (not easy to read/edit) - Dependencies built-in (Task B waits for Task A) - Claude Code only **planning-with-files:** - Stored in YOUR project directory - Markdown files you can actually read and edit - Committable to git - Works across 11+ IDEs (Cursor, Kiro, Gemini, Continue, etc.) I'm actually working on a Tasks version that combines the best of both - stay tuned. planning-with-files makes more sense if you: - Want visible markdown files in your project - Use multiple IDEs - Want to commit your planning to git - Like having a findings.md for research notes Thanks for pushing back on this. Appreciate the honesty. @gam-phon

kerem commented

2026-03-03 18:50:12 +03:00

Author

Owner

@rohanpatriot commented on GitHub (Jan 26, 2026):

Just to add to the conversation.

Tasks serve a different purpose than planning with files.

Tasks are for process and work management. Planning is breaking down the work, researching, best practices to get to the point tasks can be identified. It also serves as memory/context retrieval.

Using tasks alone is the equivalent of building a feature without a spec. Majority of the time you will end up in the wrong spot for big changes.

You could use plan mode + tasks to accomplish some of this but the plan context is not easy to look back on and the model will resort to git changes for past context.

@rohanpatriot commented on GitHub (Jan 26, 2026): Just to add to the conversation. Tasks serve a different purpose than planning with files. Tasks are for process and work management. Planning is breaking down the work, researching, best practices to get to the point tasks can be identified. It also serves as memory/context retrieval. Using tasks alone is the equivalent of building a feature without a spec. Majority of the time you will end up in the wrong spot for big changes. You could use plan mode + tasks to accomplish some of this but the plan context is not easy to look back on and the model will resort to git changes for past context.

No labels

bug

pull-request

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/planning-with-files#39

No description provided.

Rows
Columns