Dotfiles/config files hierarchy #648
druellan
started this conversation in
1. Feature requests
Replies: 1 comment
-
I can see Cline implemented a UI for this specific feature: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi! As I learn my way into how to use the AI in my day-to-day basis, I'm starting to feel the pressure about how to manage the different configurations, rules and random config files I need for the assistant to be accurate to each project, and on my system in general.
More or less, I've found that I need my files at:
For 1. It is already solved using
.kilocode/rules
folder.For 2. Using the "Custom Instructions for All Modes" setting, not ideal, but it works.
For 3. Probably porting Cline solution, that creates a
Cline/Rules
folder in the default "documents" locationAnd also for MCP servers: I need MCPs that are project-specific, but other I use on all projects. So, the situation is very similar:
For MCP Settings:
For 1. Already solved using a
.kilocode/mcp.json
.For 2. Unsure, probably leverage on
kilo-code.customStoragePath
option.For 3. The "global MCP settings" is actually global for all profiles, so, it works!
For local MCP hosting
kilo-code.customStoragePath
option, but currently I don't feel the need of having this one.Cline/MCP
folder in the default "documents" location.(*)So. hoping this is useful to start a discussion and improve the software, I'm still learning, so, might be the case I'm missing something. Let me know!
(*) I know this can be solved just creating a folder anywhere and just pointing the config file to that folder, but, I feel Kilo can have its own solution for that.
Beta Was this translation helpful? Give feedback.
All reactions