A config that you can export. #1679
Replies: 5 comments
-
I agree - I think it would be helpful to enable some kind of settings portability. I'll explore this a bit. |
Beta Was this translation helpful? Give feedback.
-
This! @cte And the ability to read from a custom location. That way you could store all configs in a repo and they can be easily shared across teams. Having it in a repo solves the history concern brought up by OP. |
Beta Was this translation helpful? Give feedback.
-
@cte it's have sync option for context, should we support them too ? |
Beta Was this translation helpful? Give feedback.
-
💯 - I stopped trying to keep my 2 PC configs in sync and just remote into my home PC from work, to do coding that's all synced in Git 😆. |
Beta Was this translation helpful? Give feedback.
-
i need that bc i frequently reset my arch linux, and it's a nightmare to reconfig roo code :C |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
It would be great if you would have a config that stores all of your custom prompts, models that you have added (not including API keys) and maybe history (but probably we can live without that). When you switch PC's and OS's it's not really convenient to set up everything from scratch. What I mean is I have a working OS (in my case linux) at the office and at home, but I also have another OS to do other stuff (windows in my case) and I had to setup the Roo-Code a lot of times. I am also experimenting with other code editors like Cursor, and each time I have to set it all up again and again. Also history is not linked to any account so it's lost when you switch and so on... so it would be nice to have your settings exported to a file (JSON for example) and get it imported in an instance of Roo-Code.
So that's my two cents, maybe that will be implemented some day and it will make me a happier person. Thank you for your attention.
Beta Was this translation helpful? Give feedback.
All reactions