Allow multiple keys in .env, and allow google cli instance to select one not in use yet, keep track of which are in-use.

[SkybuckFlying]

This idea would allow multiple gemini-cli instances running in parallel, each using a different google gemini api key to do different tasks on a code base (in parallel/at the same time).

[Manamama]

Run it with changed env.
export GEMINI_API_KEY= ... && gemini , as alias. You then call these aliases in parallel.

[SkybuckFlying]

I am not sure what you mean :).

But I plan on running multiple instances of gemini cli all in their own folder, so one .env per folder.

Then use gitea and git and git clone to clone project and postgresql and mailEnable and then hopefully the AIs can work in parallel on same project without race conditions :)

[Manamama]

Functionally, I mean the same. Different environments. Any method should do (.env files, actual env variables as per my tip above in the command line, local JSONs with the same changed keys...). Good luck with orchestration! (Myself I just use MCPs for it, a very recent (today's) sample result thereof, and that on a modest mobile 📲 is here: gracemann365/epiphany-cli-awaitFunding#1)