Earkeep Download free

Set up Gemini CLI in Earkeep

Last updated: · Reviewed quarterly

Earkeep runs the agents you already use, inside the app, against the meeting in front of you. Gemini CLI is one of ten built in. Install it, sign in once, and it appears in the agent panel with your meeting already in hand.

Install the CLI

Earkeep does not install agents. It runs the one you already have, on your own account.

shell 
npm install -g @google/gemini-cli

Homebrew works too, if you would rather not install it globally through npm:

shell 
brew install gemini-cli

Check it landed with gemini --version. Google's own Gemini CLI repository is the reference for the other routes.

Sign in

Run gemini once and choose Sign in with Google, then follow the browser flow. That is the simplest route and needs no key.

If you would rather use a key, set it in your shell profile so that Earkeep inherits it. This matters: Earkeep launches agents through your login shell precisely so that the environment they get is the environment your terminal gets, and a key exported only in one open terminal window is not part of that.

shell 
export GEMINI_API_KEY="your-key-here"

Earkeep never stores or reads those credentials. They belong to the CLI and to your shell.

Confirm Earkeep sees it

  1. Open Earkeep and press Settings, at the bottom of the left rail.
  2. Go to Agents.
  3. The Gemini CLI card should read Installed with its version number.

Earkeep launches it in the protocol mode Gemini CLI provides:

shell 
npx -y @google/gemini-cli --experimental-acp

So this agent needs Node installed. Settings warns you once if npx is missing.

Use it on a meeting

  1. Open a saved meeting.
  2. In the agent panel, start a New session and pick Gemini CLI and a working directory.
  3. Type what you want, or start from one of the suggestion cards, which come from your own prompts in Settings → Templates.

Your other meetings come wired in. Earkeep offers its own MCP server to the session automatically, so the agent can search and read your saved meetings without you configuring anything.

If something goes wrong

"Not found", but it works in your terminal. Almost always the path. Earkeep probes through your login shell, so open a fresh terminal window and run gemini --version: if that fails too, the install did not finish wiring itself in.

"npx wasn't found." Install Node. Earkeep starts this agent through npx even when you installed the CLI with Homebrew.

It starts but complains about credentials. The key is probably exported in one terminal rather than in your shell profile. See the sign-in section above.

No signed-in badge appears. That is expected. Only two agents in the roster expose a reliable non-interactive check, and Gemini CLI is not one of them, so Earkeep treats it as ready once the binary is there.

The protocol mode is marked experimental. It is, by Google rather than by us, so it can change between releases. If a session stops starting after an upgrade, that is the first thing to suspect.

Related

Frequently asked questions

Do I need a Google Cloud project?

Not for the ordinary route. Signing in with a Google account is enough. A project is only needed for the Vertex AI and Code Assist paths, which Gemini CLI documents itself.

Why does Earkeep use npx when I installed with Homebrew?

Because npx fetches the protocol adapter regardless of how the CLI itself got onto your machine. It is the launch route, not the installation route.

Does this keep everything on my device?

Earkeep's part does: capture, transcription and storage never leave your machine. Gemini CLI calls Google's API, so a transcript you hand it is a transcript you have sent there.

Can I run more than one agent on the same meeting?

Yes. A meeting can hold several sessions, each with its own agent and working directory.

Where do the session logs go?

Beside the meeting, as plain files on your own disk, one per session.

The agent comes to the meeting

Download free for macOSAll how-tos

14-day full trial, no account required.