Add files as Read Only to the context.

[adarshchbs]

This feature request is inspired by Aider. Where you can add files in Read only mode.

Currently Roo does not know which files are read only and proposes edits on those files. The user may reject these edits but it adds extra history in the model context.

Also, since Roo tends to read files multiple times during the edits which in general is good. But this step is unnecessary for Read only files. With this option being available unnecessary stuffing can be avoided.

[Martech-WorkShop]

Also coming from Aider, Roo is far superior in so many aspects... but I also do miss the ability to add specific files to the context as read only.

My main use case is to be able to add files that are relevant to the task at hand but are (for whatever reason) not to be modified during this session.

• An example would be a file from a different repo that you do not own, manage or have capabilities to modify.
• Adding an external specific library, module, etc. to the context. (standard library External public library, etc.)
• A file someone else is working on.
• Any file you don't have write access to.

The main purpose being the LLM to account for that fact and not try to modify the external file in order to complete a task, hence forcing it to modify or add the code in the existing files or new ones.

Maybe there is already a way, I guess you could simply explain this to the architect or task LLM, however the feature would make it more practical.
To take it to the next level, you would be ale to define read-only files for the current session or for the entire project (repo?).