# Gemini CLI and the Gemini app

Gemini CLI works fully with 0bridge. The Gemini app is untested. Last checked 2026-10-01.

## Gemini CLI (level: full)

```
npm install -g 0bridge
0b setup
```

`0b setup` adds the 0bridge endpoint to Gemini CLI's settings with the other tools it finds. Restart Gemini CLI after, and sign in from it if it asks.

- **History:** with `0b history on`, Gemini CLI conversations are collected from its local chat files. Gemini CLI has no turn-end hook we can use, so they upload on the 15-minute background job rather than as a turn ends.
- **Resume into Gemini CLI:** `0b resume 0b:k3f9x2 --tool gemini` starts Gemini CLI with the handoff as its first message. See [Resume anywhere](/docs/resume).
- **Resume out of Gemini CLI:** sessions are collected like the others, so Claude Code, Codex or a chat app can continue them.
- **Agent control:** Gemini is the least settled of the agents `0b agent` can start. It speaks a protocol (ACP) that Gemini CLI marks experimental, we haven't verified it end to end, and it only runs if Gemini CLI is installed. Treat it as best effort.

## The Gemini app (level: untested)

We know of no way to add a custom MCP server to the Gemini app, and we haven't tried. If the app gains one, the endpoint is `https://0bridge.dev/mcp`. Until we've seen it work, this page says untested.

If you use Gemini through the CLI and another tool in the app, 0bridge's resume still lets you carry a session from one to the other: see [Switching between AI tools](/docs/switching).