Earkeep Download free

Set up OpenClaw in Earkeep

Last updated: · Reviewed quarterly

Earkeep runs the agents you already use, inside the app, against the meeting in front of you. OpenClaw is one of ten built in, and it has a step the others don't: it runs a gateway of its own that needs setting up once before anything can drive it.

Install it

Earkeep does not install agents. It runs the one you already have.

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

Or through npm, if you already manage tools that way:

shell 
npm install -g openclaw@latest

Check it landed with openclaw --version. The OpenClaw repository is the reference, including its current Node requirements.

Run the onboarding

This is the step that distinguishes OpenClaw. Its onboarding verifies model access, creates its workspace and configures its gateway, and until it has run there is nothing for Earkeep to talk to:

shell 
openclaw onboard --install-daemon

Check it came up:

shell 
openclaw gateway status

Earkeep never sees your model credentials. They belong to OpenClaw's own configuration.

Confirm Earkeep sees it

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

Earkeep starts it in the bridge mode OpenClaw provides for exactly this:

shell 
openclaw acp

OpenClaw documents that mode as the way an external client drives it over the protocol, 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 OpenClaw 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 openclaw --version: if that fails too, the install did not finish wiring itself in.

The session starts and immediately ends. Check the gateway first with openclaw gateway status. Bridge mode needs it, and a gateway that never came up is the most likely cause on a fresh install.

It complains about Node. OpenClaw is particular about versions when installed through npm. The install script provisions what it needs, so switching to that route is the quicker fix.

No signed-in badge appears. That is expected. Only two agents in the roster expose a reliable non-interactive check, and OpenClaw is not one of them.

Related

Frequently asked questions

Why does this one need onboarding when the others don't?

Because OpenClaw runs a gateway rather than being a single command. The onboarding is what creates its workspace and verifies model access, and bridge mode depends on it.

Do I need to keep the daemon running?

Yes. The bridge talks to a live gateway, so a stopped daemon means a session that cannot start. openclaw gateway status is the check.

Does this keep everything on my device?

Earkeep's part does: capture, transcription and storage never leave your machine. What OpenClaw does depends on the model you configured it with.

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.