Support for forked docker images or custom CLIs

[zahin-mohammad]

For organizations that have forked aider, it would be very beneficial to be able to use a separate docker repository. Instead of specifying just tag, maybe the full qualifier for the repository would be possible?

Likewise, instead of just specifying the path, maybe allowing specifying the command itself will be useful (custom args, environment variables, etc).

[p-wegner]

Sure, for docker having the image name configurable would allow your forked image to be used. I'm not sure if docker run supports custom docker registries, but even if it doesn't, pulling it manually once should work in any case https://docs.docker.com/reference/cli/docker/image/pull/#pull-from-a-different-registry
I'll try to include this in the next release.

Regarding the native aider execution without docker, I'm not sure what's missing for your usecase. You can define "default additional args"
that will be appended to every aider executeable call. For the env you could either use aiders option as a custom arg https://aider.chat/docs/config/options.html#--set-env-env_var_namevalue or define env variables in any of the .env locations https://aider.chat/docs/config/dotenv.html that aider supports. It's not the most convenient way to define them, but i assume this won't be done/changed often. Can you elaborate how you would like to use this configuration option?