Settings location for CLI

[tompropst]

I'm struggling to find where settings files should be located when using the CLI. I am trying to use something like pipx or uv to install pr-agent into an isolated environment. When I run pr-agent, it appears to miss my settings (.secrets.toml and configuration.toml) no matter where I locate them.

I've verified that my settings work by passing them as environment variables to the docker container.

Can someone point me to information on how the CLI searches for and loads settings from TOML file(s)?

[DanaFineTLV]

Hi @tompropst , thank you so much for adding those questions.
We are restructuring the project, and starting from next week, community maintainers will be involved. I apologize for the delay in my response.
If you're interested in actively participating in the project maintenance, please reach out to me via email at dana.f@qodo.ai or on LinkedIn - https://www.linkedin.com/in/fine-dana/

[IsmaelMartinez]

The CLI does not search the working directory. Settings files are resolved relative to the installed package, so under pipx or uv they must sit in <venv>/lib/python3.x/site-packages/pr_agent/settings/, which is why copies elsewhere were ignored. For an isolated install the supported route is to keep your own TOML anywhere and pass --extra_config_url=/path/to/your.toml (or set PR_AGENT_EXTRA_CONFIG_URL); it accepts a bare filesystem path as well as http and file URLs, and is merged beneath the repo config. Secrets are better supplied as environment variables using the <TABLE>__<KEY> convention, for example OPENAI__KEY and GITHUB__USER_TOKEN, which is the same mechanism your working Docker setup used. One correction worth noting: the precedence block in the configuration options guide shows PR_AGENT__SECTION__KEY, which does not work; the prefix-free <TABLE>__<KEY> form is correct, and that documentation line needs fixing.