Add an internal task/action list (which works globally) to be able to manage large context windows

[fev4]

Context windows are limited. You normally have to start over and over again when the project or files are too large, this forces devs to provide the same context over and over again. If Roo Code could keep track of what has done, what is missing and the files it has already edited, it would be able to plan ahead and execute step by step.

I've managed to fix a bit of this by having a custom prompt along the lines of:

plan ahead and keep a task list of your activities in file a called scratchpad.md (markdown format) where `- [ ] <task-description>` is used for pending tasks and `- [x] <task-description>` for completed tasks, you should always update this file after taking action and refer to it when continuing to take action, no matter how small or big your objective is, the task should always contain the file being edited and a very small summary of the changes done

This scratchpad.md file would be gitignored, but I feel like this should live inside Cline, where I get to chose if the next task should use the scratchpad.md or not with an easy to access toggle, in addition to the ability to edit the scratchpad to add or remove tasks.

Why shouldn't this live inside a Configuration Profile?
If this were to be inside a profile config, it would be cumbersome to edit, as the number of options inside a config wouldn't be related to the work being done. As I see it, profile configs and the scratchpad are two different axes that, although at some point could join, they are not aiming for the same goal, one is very much attached to API Provider configs, and the other to the work being done. In fact there could be different scratchpad configs depending on the API Provider.

Thoughts?

[ront85]

Fantastic idea! I am working on a large code base and find the exact same issues. This would enhance the developmen experience drastically. Also a place where you can define the global project stratergy and technology the app uses, its it doesnt get too of target would be nice.

[mdlmarkham]

Could one of the the memory MCP tools be used for this rather than creating another markdown file? Would that possibly require fewer tokens?

[fev4]

I think the global strategy and codebase nitpicks should go in .clinerules just like before

[vijaykrishna00]

https://github.com/GreatScottyMac/roo-code-memory-bank

i found this and seem to be helpful to me
we can implement an improved version of this by default