Earkeep Download free

Set up Kimi CLI in Earkeep

Last updated: · Reviewed quarterly

Earkeep runs the agents you already use, inside the app, against the meeting in front of you. Kimi CLI, from Moonshot AI, is one of ten built in. It is the one Python tool in the roster, so its installation looks different from the rest.

Install it

Kimi CLI is distributed as a Python tool and installed with uv, which manages the Python it runs on for you. If you do not have uv, install it first:

shell 
brew install uv

Then install Kimi CLI. Pinning the Python version is what its own documentation recommends, and it saves you from whatever Python happens to be on the machine:

shell 
uv tool install --python 3.13 kimi-cli

Check it landed:

shell 
kimi --version

Moonshot's Kimi CLI getting-started guide is the reference, including the supported Python range.

Log in

Start kimi in a terminal and send /login at its prompt. It asks which platform to use and takes you through the sign-in, or accepts an API key if you would rather use one.

Do this before trying to use it from Earkeep. Kimi CLI is not one of the two agents that can report their sign-in state, so the app cannot tell you it is missing: an unauthenticated agent looks installed and then fails when a session starts.

Earkeep never sees those credentials. They belong to the CLI.

Confirm Earkeep sees it

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

Earkeep starts it in the protocol server mode Kimi CLI provides:

shell 
kimi acp

Kimi CLI documents that mode for editor integrations, so the same command is what an editor would use. Nothing about it is specific to Earkeep.

Use it on a meeting

  1. Open a saved meeting.
  2. In the agent panel, start a New session and pick Kimi 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. A tool installed with uv lands in ~/.local/bin, and Earkeep probes through your login shell, so it is visible only if your shell profile adds that directory to PATH. Open a fresh terminal window and run kimi --version to check. uv tool update-shell fixes it if not.

The session starts and immediately ends. You have most likely not logged in yet. Run kimi acp in a terminal on its own: if it exits there, send /login from a plain kimi session first.

Related

Frequently asked questions

Do I need Python?

Not one you manage yourself. Installing with uv gets the right Python for you, which is why the command above pins a version.

Do I need Node?

No. Kimi CLI ships its own protocol server, so unlike the npx-backed agents it needs nothing from the Node ecosystem.

Does this keep everything on my device?

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

Why is there no signed-in badge?

Only two agents in the roster expose a reliable non-interactive way to check. For the rest, a wrong "not signed in" would be worse than none, so Earkeep shows nothing.

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.