docsGemini CLIWindows

Windows Setup

Special Offer - Use Vibe Coding API at approximately 0.35x of the original price, exclusively for programming tools!

This guide will help you configure Gemini CLI to use Fizzly API on Windows.

Requirements

  • Windows 10 or later
  • Node.js 22+ installed
  • Fizzly API key (Get your key)

Installation Steps

Step 1: Check Environment

Open CMD or PowerShell and check installed global packages:

npm list -g --depth=0

Check npm global packages

If you don’t have Node.js installed, download the LTS version from nodejs.org.

Step 2: Install Gemini CLI

Install Gemini CLI globally using npm:

npm i -g @google/gemini-cli@latest

Install CLI tools

⚠️

If you encounter network issues, you can use a mirror registry:

npm i -g @google/gemini-cli@latest --registry=https://registry.npmmirror.com

Step 3: First Run (Very Important!)

This step is crucial! Running Gemini CLI for the first time will automatically create the configuration folder in your user directory.

gemini

You’ll see the welcome screen:

Gemini CLI first run

Press Ctrl+C to exit. This will create the configuration folder at %USERPROFILE%\.gemini.

Configure API

Step 1: Get API Key

Log in to Fizzly Console and create a new API key.

⚠️

Important: To enjoy the special discounted pricing for programming tools, make sure to select the vibe coding group when creating your API key. This group’s API is exclusively for use with Claude Code, Codex CLI, Gemini CLI, and similar programming tools.

API Key

Step 2: Open Configuration Directory

Press Win + R to open the Run dialog, enter the following and press Enter:

%userprofile%\.gemini

Open .gemini directory

You’ll see the configuration files in the directory:

.gemini directory structure

Step 3: Edit Configuration File

In the .gemini directory, create or edit the .env file with the following content:

.env
GOOGLE_GEMINI_BASE_URL=https://api.fizzlyapi.com
GEMINI_API_KEY=your-fizzly-api-key
GEMINI_MODEL=gemini-2.5-pro

.env configuration

⚠️

Replace your-fizzly-api-key with your actual API key from the Fizzly Console.

Step 4: Verify Configuration

After saving the file, restart Gemini CLI:

gemini

If configured successfully, you’ll see Gemini CLI running normally:

Gemini CLI running successfully

Alternative Configuration Methods

Open PowerShell and run:

# Temporary setting (current session only)
$env:GOOGLE_GEMINI_BASE_URL = "https://api.fizzlyapi.com"
$env:GEMINI_API_KEY = "your-fizzly-api-key"
$env:GEMINI_MODEL = "gemini-2.5-pro"

For permanent configuration, add to PowerShell profile:

# Open profile (create if doesn't exist)
if (!(Test-Path -Path $PROFILE)) { New-Item -ItemType File -Path $PROFILE -Force }
notepad $PROFILE
 
# Add the following content:
$env:GOOGLE_GEMINI_BASE_URL = "https://api.fizzlyapi.com"
$env:GEMINI_API_KEY = "your-fizzly-api-key"
$env:GEMINI_MODEL = "gemini-2.5-pro"
⚠️

After editing the profile, restart PowerShell for changes to take effect.

Supported Models

All Google Gemini models are supported. See Gemini CLI Models.

Basic Usage

# Start interactive mode
gemini
 
# Start in current project directory
cd your-project
gemini
 
# Run single command
gemini "Write a Python quicksort function"
 
# Use specific model
gemini --model gemini-2.5-flash
 
# Show help
gemini --help

Troubleshooting

1. “gemini” command not found

Cause: Gemini CLI is not installed or not in PATH.

Solution:

# Reinstall Gemini CLI
npm install -g @google/gemini-cli
 
# Check npm global install path
npm config get prefix
 
# Verify installation
npm list -g --depth=0 | findstr gemini

2. “GEMINI_API_KEY not set” error

Cause: Environment variable or configuration file not properly set.

Solution:

First check the configuration file:

# View configuration file content
type %USERPROFILE%\.gemini\.env

If the file doesn’t exist or is incorrect, follow the “Configure API” steps above.

3. Connection timeout

Cause: Network issues or firewall blocking.

Solution:

  1. Check your network connection
  2. Verify API URL is correct: https://api.fizzlyapi.com
  3. Check Windows Firewall settings
  4. If using enterprise network, you may need to configure proxy

4. Authentication failed (401)

Cause: Invalid or expired API key.

Solution:

  1. Verify your API key in Fizzly Console
  2. Ensure the key is not deleted or disabled
  3. Re-copy and paste the key (avoid extra spaces)

5. Insufficient balance (403)

Cause: Account balance depleted.

Solution:

  1. Check balance in Fizzly Console
  2. Top up your account in Billing → Recharge
  3. Retry after balance is updated

6. PowerShell execution policy restriction

Cause: Windows restricts script execution by default.

Solution:

# Run PowerShell as Administrator and execute:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser

Need more help? Check the FAQ page.

Next Steps

OverviewmacOS