Setup to review other folder changes

[kamilhawdziejuk]

Hi,

please correct me if I am wrong but currently we are able to generate code review for the exact same repository only (this is how I see getGitRoot or getDiffCommand are defined to be run in a local folder). And If I change anything there to work on a different repository I am getting error:
Cannot start clients: MCP config not loaded
and then
AI_ToolExecutionError Error executing tool read_file: ENOENT: no such file or directory, open
etc..

Is this somehow configurable to make it happen? Or what bear minimum needs to be changed to make this tool work on running on some other repo ("C:/Sources/project")? Or it is not there yet and is rather a feature request?

Thank You - this is a great tool!
Kamil

[mattzcarey]

Could you explain your usecase a little bit more.

We had something like this for reviewing GitHub PRs locally previously but it wasn't a well used feature.

[kamilhawdziejuk]

Thank you for the responsiveness!

I wanted to use this tool to generate feedback to the opened Pull Request. Ideally by passing a link to a Pull Request as a parameter (to be exact I am working with Bitbucket server currently but 'git diff' is giving similar code difference between branches so it does not matter much which server is used). So the usecase is to use this tool, and integrate it with other code repository (and for simplicity it can be just a repository in a different folder on the same disk) for which we can generate a feedback to a particular PR.

Wondering if this is a big change and where to start to achieve it.

Kamil

[mattzcarey]

I'm sure we could accept a --cwd flag.

I would have a look at src/common/git some of that stuff is pretty old tho. It could definitely be cleaned up into the platform providers I made.