> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claude-mem.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Gemini Provider

> Use Google's Gemini API as an alternative to Claude for observation extraction

# Gemini Provider

Claude-mem supports Google's Gemini API as an alternative to the Claude Agent SDK for extracting observations from your sessions. Memory runs off-plan on your Gemini key, so observation extraction never shares your Claude plan usage.

<Warning>
  **Rate limits without billing**: Gemini applies model-specific limits to projects without billing. Enable billing on your Google Cloud project for higher limits, and review Google's current quota and billing terms before doing so.
</Warning>

## Why Use Gemini?

* **Runs off-plan**: Observation extraction happens on your Gemini key, not your Claude plan
* **Same quality**: Gemini extracts observations using the same XML format as Claude
* **Errors throw clearly**: 429s, 5xx, and network failures throw — leaving messages pending so they can be retried
* **Hot-swappable**: Switch providers without restarting the worker

## Getting an API Key

1. Go to the [Google AI Studio API Key page](https://aistudio.google.com/app/apikey)
2. Sign in with your Google account
3. Accept the Terms of Service and privacy policies
4. Click the **Create API key** button
5. Choose a Google Cloud project or create a new one
6. Copy and securely store the generated API key

<Tip>
  **No billing required** to get started. Enabling billing can unlock higher rate limits; review Google's current quota and billing terms first.
</Tip>

## Configuration

### Settings

| Setting | Values | Default | Description |
| - | - | - | - |
| `CLAUDE_MEM_PROVIDER` | `claude`, `codex`, `gemini`, `openrouter`, `openai-compatible` | `claude` | AI provider for observation extraction |
| `CLAUDE_MEM_GEMINI_API_KEY` | string | — | Your Gemini API key |
| `CLAUDE_MEM_GEMINI_API_KEYS` | newline- or comma-separated keys | — | Extra keys to rotate through when one is rate-limited or spent ([Multi-Key Rotation](/usage/multi-key-rotation)) |
| `CLAUDE_MEM_GEMINI_MODEL` | `gemini-flash-latest`, `gemini-flash-lite-latest`, `gemini-3.5-flash`, `gemini-3.1-flash-lite`, `gemini-3-flash-preview` | `gemini-flash-latest` | Gemini model to use |
| `CLAUDE_MEM_GEMINI_RATE_LIMITING_ENABLED` | `true`, `false` | `true` | Pace requests to the model's no-billing RPM. Set `false` once billing is enabled on Google Cloud |

### Using the Settings UI

1. Open the worker URL printed on startup
2. Click the **gear icon** to open Settings
3. Under **AI Provider**, select **Gemini**
4. Enter your Gemini API key
5. Optionally select a different model

Settings are applied immediately—no restart required.

### Manual Configuration

Edit `~/.claude-mem/settings.json`:

```json theme={null}
{
  "CLAUDE_MEM_PROVIDER": "gemini",
  "CLAUDE_MEM_GEMINI_API_KEY": "your-api-key-here",
  "CLAUDE_MEM_GEMINI_MODEL": "gemini-flash-latest",
  "CLAUDE_MEM_GEMINI_RATE_LIMITING_ENABLED": "true"
}
```

Alternatively, set the API key via environment variable:

```bash theme={null}
export GEMINI_API_KEY="your-api-key-here"
```

The settings file takes precedence over the environment variable.

## Available Models

| Model | RPM without billing | Notes |
| - | - | - |
| `gemini-flash-latest` | 10 | **Default.** Google alias that always tracks the current GA Flash model |
| `gemini-flash-lite-latest` | 15 | Google alias that always tracks the current GA Flash-Lite model |
| `gemini-3.5-flash` | 10 | Pinned GA Flash model |
| `gemini-3.1-flash-lite` | 15 | Pinned GA Flash-Lite model |
| `gemini-3-flash-preview` | 5 | Preview model, lower rate limit |

<Note>
  The older `gemini-2.5-*` and `gemini-2.0-*` model IDs were removed: Google returns `404 NOT_FOUND` ("no longer available to new users") for these when called with a freshly created API key. The `-latest` aliases are recommended because they never go stale as Google rotates GA models.
</Note>

## Provider Switching

You can switch between Claude and Gemini at any time:

* **No restart required**: Changes take effect on the next observation
* **Conversation history preserved**: When switching mid-session, the new provider sees the full conversation context
* **Seamless transition**: Both providers use the same observation format

### Switching via UI

1. Open Settings in the viewer
2. Change the **AI Provider** dropdown
3. The next observation will use the new provider

### Switching via Settings File

```json theme={null}
{
  "CLAUDE_MEM_PROVIDER": "gemini"
}
```

## Error Behavior

When Gemini refuses a request, queued observations stay pending; what happens next depends on the refusal:

* **Per-minute throttle** (a 429 whose quota is per minute): claude-mem waits the delay Google names and resumes. If the throttle keeps refusing, Gemini is held for 90 seconds.
* **Spent daily (or weekly, monthly) quota** (a 429 naming a per-day quota): Gemini is held for 30 minutes, then one request checks whether the quota has reset.
* **Region not served** ("User location is not supported"): capture pauses with the work kept, and the next session start says to switch providers. Gemini is re-checked once every 30 minutes. Extra keys are not tried, since every key gets the same answer.
* **Invalid or revoked key**: with extra keys configured, the next key is tried; otherwise the same pause, and the notice says to fix the key.
* **Server errors and network faults**: paused with the work kept, then resumed automatically on a backoff.
* **Other malformed requests** (HTTP 400): that session's pending observations are dropped. A request too long for the model's window retires the conversation instead and keeps them.

To keep capturing while Gemini is held, configure a [quota fallback](/usage/quota-fallback) (opt-in, off by default). Extra keys rotate within Gemini ([Multi-Key Rotation](/usage/multi-key-rotation)). To switch providers for good, change `CLAUDE_MEM_PROVIDER`.

## Troubleshooting

### "Gemini API key not configured"

Either:

* Set `CLAUDE_MEM_GEMINI_API_KEY` in `~/.claude-mem/settings.json`, or
* Set the `GEMINI_API_KEY` environment variable

### Rate Limiting

Google applies different rate limits depending on whether billing is enabled:

**Without billing (API key only):**

| Model | RPM | TPM |
| - | - | - |
| gemini-flash-latest / gemini-3.5-flash | 10 | 250K |
| gemini-flash-lite-latest / gemini-3.1-flash-lite | 15 | 250K |
| gemini-3-flash-preview | 5 | 250K |

Claude-mem enforces these limits automatically with built-in delays between requests. Processing may be slower but stays within limits.

**With billing enabled:**

| Model | RPM | TPM |
| - | - | - |
| gemini-flash-lite-latest / gemini-3.1-flash-lite | 4,000 | 4M |
| gemini-flash-latest / gemini-3.5-flash | 1,000 | 1M |
| gemini-3-flash-preview | 1,000 | 1M |

<Tip>
  **Higher throughput**: Enabling billing can unlock much higher rate limits. Review your Google Cloud quota and billing settings first. Claude-mem can then use the higher configured limits instead of its conservative no-billing throttle.
</Tip>

If you hit rate limits:

* The pending observations stay queued and resume when the limit resets (see [Error Behavior](#error-behavior))
* Or configure a [quota fallback](/usage/quota-fallback), or switch back to Claude as your primary provider

### Observation Quality

If observations seem lower quality with Gemini:

* Note that Claude typically produces slightly higher quality observations
* Consider using Gemini to keep memory off-plan and Claude for important projects

## Next Steps

* [Configuration](/configuration) - Full settings reference
* [Getting Started](/usage/getting-started) - Basic usage guide
* [Troubleshooting](/troubleshooting) - Common issues

## Multiple keys

`CLAUDE_MEM_GEMINI_API_KEYS` accepts additional keys (newline- or comma-separated) alongside
`CLAUDE_MEM_GEMINI_API_KEY`. When a key hits a rate limit, spends its quota, or is rejected as
invalid, Gemini requests rotate to the next key instead of failing for the
rest of the window. See [Multi-Key Rotation](/usage/multi-key-rotation).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.