Set up Claude Code in Earkeep

Two things on your device, and Settings → Agents checks for both:

• The Claude Code CLI, installed and signed in. The sections below walk through it.
• Node.js 22 or newer, which brings npm and npx with it. Earkeep starts Claude Code through an adapter fetched with npx, so without Node the CLI can be installed and signed in and the agent still cannot run.

If you don't have Node yet, install it with Homebrew or from nodejs.org:

Then check that both answer, and that the first says 22 or higher:

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:

Check it landed:

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

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 instead of leaving you guessing:

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.

1. Open Earkeep and press Settings, at the bottom of the left rail.
2. Go to Agents.
3. The Claude Code card should show a green Ready with its version number. A yellow Needs setup lists underneath what is still missing, and a red Not installed means Earkeep could not find the CLI.

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

So this agent needs Node installed as well as the Claude Code CLI. If Node is missing or older than 22, the card turns yellow and says which version to install.

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.

"Not installed", 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.

"Needs setup", asking you to sign in. Run claude in a terminal and sign in, then reopen Settings.

"Needs setup", asking for Node.js. Install Node.js 22 or newer, or update the one you have (brew upgrade 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.

• Agents and MCP: why the agent comes to the meeting, not the other way round.
• Connect Claude Code over MCP: reaching your meeting history from your terminal instead.
• All Earkeep how-tos.