Set up Claude Code in Earkeep

Last updated: · Reviewed quarterly

Earkeep runs the agents you already use, inside the app, against the meeting in front of you. Claude Code is one of ten built in. Install its command-line tool, sign in once in your terminal, 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, using your own account and your own subscription, which is the reason there is no inference cost baked into the price of the app.

Install Claude Code from your terminal:

shell
curl -fsSL https://claude.ai/install.sh | bash

Check it landed:

shell
claude --version

Anthropic's own Claude Code documentation covers the other installation routes and the editor extensions.

Sign in

Run claude once in a terminal and follow the sign-in it offers. Claude Code is one of only two agents in the roster that can tell Earkeep whether you are signed in, so if you skip this step the app will say so rather than leave you guessing:

shell
claude auth status

Earkeep never sees those credentials. They belong to the CLI, in your own home directory, and the app only ever asks the CLI whether they are there.

Confirm Earkeep sees it

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

Earkeep launches it over the Agent Client Protocol using Anthropic's own adapter, which it fetches through npx:

shell
npx -y @agentclientprotocol/claude-agent-acp

So this agent needs Node installed as well as the Claude Code CLI. 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 Claude Code 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. That is the difference between this and connecting Claude Code from your terminal, where you add the server yourself.

A meeting can hold several sessions at once, and each one is written beside the meeting as a plain file, so what an agent did is as durable as the transcript it did it to.

If something goes wrong

"Not found", but it works in your terminal. This is almost always the path. Earkeep probes for agents through your login shell so that what your terminal can see, it can see too, but a CLI installed into a directory your shell profile never adds to PATH is invisible to both. Open a fresh terminal window and run claude --version: if that fails too, the install did not finish wiring itself in.

"Installed but not signed in." Run claude in a terminal and sign in, then reopen Settings.

"npx wasn't found." Install Node. Earkeep starts this agent through its ACP adapter, and that adapter is fetched with npx.

The session starts and then ends. The panel shows a notice with a New session button. Starting a fresh one is the fix; the old session's log stays on disk either way.

Related

Frequently asked questions

Do I need an Anthropic API key?

No. Earkeep runs the CLI you already signed in to, with whatever subscription or credentials that CLI uses. Earkeep itself has no API keys and no account.

Does this keep everything on my device?

Earkeep's part does: capture, transcription and storage never leave your machine. The agent is a separate decision. Claude Code calls Anthropic's API, so a transcript you hand it is a transcript you have sent there. Choosing which meeting to hand over is the control you have.

What is ACP?

The Agent Client Protocol, a standard way for an application to drive a coding agent. Earkeep integrates with the protocol rather than with ten separate agents, which is why any other agent that speaks it works the same way.

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

14-day full trial, no account required.