Add an internal task/action list (which works globally) to be able to manage large context windows #448
fev4
started this conversation in
Feature Requests
Replies: 1 comment 2 replies
-
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. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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:
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 thescratchpad.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?
Beta Was this translation helpful? Give feedback.
All reactions