agents.config.json location

[madaerodog]

Hey, could we have a in home folder called .nanocode that contains the default agents.config.json ?
Now its cumbersome to have it in the start folder through various projects.
I could try to work out a pull request and do it myself just wanted to know if you its a good idea.
Its also the pattern all the other coding tools are using.

best,
Constantin

[will-lamerton]

Hey @madaerodog - I like this idea a lot and it makes sense. Day-to-day, I use different providers and API keys per project because of different clients etc, so, having granular control is important. But, I agree, if this isn't a problem for an individual this could be cumbersome.

Maybe you could create a default config that Nanocoder uses but, if it detects an agents.config.json file in the working directory you're running it in, it'll use that instead?

Feel free to put together a pull request for it - we would love to have you involved! If not, I can triage - let me know :)

[spinualexandru]

I would also come up with a hierarchical suggestion:

1. $PWD/agents.config.json
2. $XDG_CONFIG_HOME/.nanocoder/agents.config.json (or $HOME/.nanocoder/agents.config.json as Constantin suggested)

Loading Hierarchy:

• Project-Level Configuration: will first check for an agents.config.json file in the current working directory ($PWD). If this file exists, it will be the only configuration loaded. No global configuration will be used. This ensures that a project's settings are completely isolated and private by default.
• If there is no agents.config.json, first ask the user if they want to create one and save the answer per project ( similar to how we store trustedDirectories )
• Global Fallback: If and only if a local configuration file is not found, the tool will then check for a global configuration file at $XDG_CONFIG_HOME/.nanocoder/agents.config.json. This acts as a convenient fallback for users who want to apply a single set of settings across all projects that don't have their own specific configuration.

Behavioral Nuances:

• No Merging: To prevent confusion and unexpected behavior, we will not merge the contents of the global and local configuration files. The local file, when present, will completely override the global one. This simplifies the mental model for the
• Explicit Overrides: We will not use "magic" behavior or prompts asking the user if they want to load a different configuration. Instead, we'll offer clear command-line flags for explicit control.

New Command-Line Flags:

To give users even more control, we will introduce two new flags:

--use-global-config: Forces Nanocoder to use the global configuration, even if a local one exists. This is for users who want to explicitly apply their global settings to a specific project.

--no-global-config: Prevents the tool from ever loading the global configuration. This is a "strict privacy" mode that ensures only the current directory's configuration is considered.

Would love to hear your thoughts!

[will-lamerton]

@spinualexandru I think this is a great idea. I will work on a spec now and post here.

@madaerodog Let me know if this is a pull request you still want to work on?

[will-lamerton]

Hey @madaerodog, @spinualexandru,

A spec like this? (attached)

global-config-file-spec.md

Let me know your thoughts and feel free to make adjustments :)

[madaerodog]

@spinualexandru I think this is a great idea. I will work on a spec now and post here.

@madaerodog Let me know if this is a pull request you still want to work on?

I am trying although kinda swamped with some projects atm!

[will-lamerton]

Hey @madaerodog - not a problem. Happy to take this on soon if you're swamped :)