gemini-cli 0.11.x and 0.12 preview don't include "--proxy" argument command parameter !!!

[arminhallouche]

What happened?

from gemini-cli 0.11.x and 0.12 preview don't include "--proxy" argument command parameter !!!

In our corporate, we use "--proxy" argument parameter to use the right proxy.
We have multiple entries proxy urls in our corporate network, and can't put it on Environnement Variable.

What did you expect to happen?

when we use

gemini --proxy http://url-proxy:3232
we expect have gemini gui started

But from the 0.11.0 version we have this error :

Unknown argument: proxy
Usage: gemini [options] [command]

Gemini CLI - Launch an interactive CLI, use -p/--prompt for non-interactive mode

Commands:
  gemini [query..]             Launch Gemini CLI                                                                                                                                                                                                                                                                                                 [default]
  gemini mcp                   Manage MCP servers
  gemini extensions <command>  Manage Gemini CLI extensions.

Positionals:
  query  Positional prompt. Defaults to one-shot; use -i/--prompt-interactive for interactive.

Options:
  -d, --debug                     Run in debug mode?                                                                                                                                                                                                                                                                            [boolean] [default: false]
  -m, --model                     Model                                                                                                                                                                                                                                                                                                           [string]
  -p, --prompt                    Prompt. Appended to input on stdin (if any).                                                                                                                                                                    [deprecated: Use the positional prompt instead. This flag will be removed in a future version.] [string]
  -i, --prompt-interactive        Execute the provided prompt and continue in interactive mode                                                                                                                                                                                                                                                    [string]
  -s, --sandbox                   Run in sandbox?                                                                                                                                                                                                                                                                                                [boolean]
  -y, --yolo                      Automatically accept all actions (aka YOLO mode, see https://www.youtube.com/watch?v=xvFZjo5PgG0 for more details)?                                                                                                                                                                           [boolean] [default: false]
      --approval-mode             Set the approval mode: default (prompt for approval), auto_edit (auto-approve edit tools), yolo (auto-approve all tools)                                                                                                                                              [string] [choices: "default", "auto_edit", "yolo"]
      --experimental-acp          Starts the agent in ACP mode                                                                                                                                                                                                                                                                                   [boolean]
      --allowed-mcp-server-names  Allowed MCP server names                                                                                                                                                                                                                                                                                         [array]
      --allowed-tools             Tools that are allowed to run without confirmation                                                                                                                                                                                                                                                               [array]
  -e, --extensions                A list of extensions to use. If not provided, all extensions are used.                                                                                                                                                                                                                                           [array]
  -l, --list-extensions           List all available extensions and exit.                                                                                                                                                                                                                                                                        [boolean]
      --include-directories       Additional directories to include in the workspace (comma-separated or multiple --include-directories)                                                                                                                                                                                                           [array]
      --screen-reader             Enable screen reader mode for accessibility.                                                                                                                                                                                                                                                                   [boolean]
  -o, --output-format             The format of the CLI output.                                                                                                                                                                                                                                          [string] [choices: "text", "json", "stream-json"]
  -v, --version                   Show version number                                                                                                                                                                                                                                                                                            [boolean]
  -h, --help                      Show help

And Gemini don"t started !

Client information

• CLI Version: 0.11.2
• Operating System: win32 v22.15.0

Login information

No response

Anything else we need to know?

No response

[pkropachev]

It looks like --proxy option was deprecated, but corresponding parameters for proxy haven't been introduced in ~/.gemini/settings.json.

As temporary solution I've created function alias in zsh:

function gemini-cli() {
    HTTPS_PROXY="http://my.proxy.com:8080" \
    gemini "$@"
}

I suppose something similar can be done in Windows.

[arminhallouche]

Thanks @IceChestnut for implementing proxy support via settings.json in PR #12473 — this is a very welcome addition!
Just to confirm: with this change, is it now possible to configure a proxy persistently without relying on environment variables or CLI flags like --proxy? If so, could you share an example of how the proxy should be defined in ~/.gemini/settings.json (e.g., format, supported protocols)?
Also, will this configuration apply to all outbound requests made by the CLI, including model calls and MCP server integrations?
Thanks again for the update — this will greatly simplify usage in enterprise environments with dynamic proxy setups.

[arminhallouche]

It looks like --proxy option was deprecated, but corresponding parameters for proxy haven't been introduced in ~/.gemini/settings.json.

As temporary solution I've created function alias in zsh:

function gemini-cli() {
HTTPS_PROXY="http://my.proxy.com:8080"
gemini "$@"
}
I suppose something similar can be done in Windows.

Thanks for the response @pkropachev ,
I attempted to launch Gemini using PowerShell, but encountered several errors related to API calls.
After reviewing the code, I noticed that some API requests are retrieving the proxy URL from the system environment variables rather than using the values explicitly set within the PowerShell session.

[sfw134]

It looks like --proxy option was deprecated, but corresponding parameters for proxy haven't been introduced in ~/.gemini/settings.json.

As temporary solution I've created function alias in zsh:

function gemini-cli() {
HTTPS_PROXY="http://my.proxy.com:8080"
gemini "$@"
}
I suppose something similar can be done in Windows.

Good solution! In Windows, open your terminal, execute command "set HTTPS_PROXY=http://my.proxy.com:8080" first and then execute command "gemini".

[arminhallouche]

It looks like --proxy option was deprecated, but corresponding parameters for proxy haven't been introduced in ~/.gemini/settings.json.
As temporary solution I've created function alias in zsh:
function gemini-cli() {
HTTPS_PROXY="http://my.proxy.com:8080"
gemini "$@"
}
I suppose something similar can be done in Windows.

Good solution! In Windows, open your terminal, execute command "set HTTPS_PROXY=http://my.proxy.com:8080" first and then execute command "gemini".

Yes, if you have only one proxy URL in your organization.
For example, if there is some commande in your prompt to retrieve data from URL that need to use the second proxy url of your organization, that will timout.

[scidomino]

Yes. HTTPS_PROXY is the standard way to address this issue so we took out the home-grown proxy flag.

[arminhallouche]

Yes. HTTPS_PROXY is the standard way to address this issue so we took out the home-grown proxy flag.

Hello @scidomino,

I see that you closed the ticket and there is @IceChestnut that developped a feature that is working !
#12473

Can you reopen please the ticket ?

Explanations : The HTTPS_PROXY can't be used in our organisation. We have multiple proxy. Depends on which url we use the PAC file redirect as on the right url proxy.

Example : For google urls the proxy use urlProxy1 and for microsoft urls, we use urlProxy2 and for SAP it use urlProxy3
If we put in our PC, HTTPS_PROXY: urlProxy1 => microsoft, outlook, sharepoint, SAP etc... will don't work anymore !
If you suggest to put them in NoProxy, still not working, because they need their propre urls.

I test the pull of @IceChestnut in our organization et it's amazing ! it's working perfectely !!!

Thanks- in advance !

[scidomino]

@arminhallouche: You can already set the proxy just for gemini today in a variety of ways:

1. You can simply set the env var inline when you execute gemini:

• linux/macos: $HTTPS_PROXY=foo gemini
• windows: cmd /C "set HTTPS_PROXY=foo && gemini" (there are other ways to do this for powershell)

2. You can declare it in your ~/.gemini/.env file which will get automatically picked up when run.

Does that work for you?

[arminhallouche]

@arminhallouche: You can already set the proxy just for gemini today in a variety of ways:

1. You can simply set the env var inline when you execute gemini:

• linux/macos: $HTTPS_PROXY=foo gemini
• windows: cmd /C "set HTTPS_PROXY=foo && gemini" (there are other ways to do this for powershell)

2. You can declare it in your ~/.gemini/.env file which will get automatically picked up when run.

Does that work for you?

Hello @scidomino,

Yes I tried to put like you said :
$env:HTTP_PROXY=urlProxy1
$env:HTTPS_PROXY=urlProxy1
gemini
Yes Gemini response to the prompt, But when gemini executes commands to fetch data from SharePoint or Outlook, it's not working !

For the second, we are in windows, the variable can't be setted like linux or mac

Thanks in advance for replying !

[scidomino]

.env files are cross platform and should work on windows.

Let me know if that works. If not we can open a separate bug to fix propagation.

[arminhallouche]

.env files are cross platform and should work on windows.

Let me know if that works. If not we can open a separate bug to fix propagation.

Hello @scidomino ,

I just test with .env file, and it's working perfectely, gemini can retrieve data correctely !

I add the explanation for the other users :

To put the https_proxy for gemini (windows, linux or mac), just create a file named .env (without extension) inside the .gemini folder and put this inside :

HTTP_PROXY="http://proxy_url:8888"
http_proxy="http://proxy_url:8888"

HTTPS_PROXY="http://proxy_url:8888"
https_proxy="http://proxy_url:8888"

Thanks a lot to @scidomino and @IceChestnut !

You can keep this ticket closed !