Earkeep Download free

Set up Qwen Code in Earkeep

Last updated: · Reviewed quarterly

Earkeep runs the agents you already use, inside the app, against the meeting in front of you. Qwen Code is one of ten built in. Install it, configure a provider 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 @qwen-code/qwen-code@latest

Homebrew works too:

shell 
brew install qwen-code

Qwen Code needs Node 22 or newer for the npm route. Check both at once:

shell 
node --version && qwen --version

The Qwen Code repository is the reference for the standalone installers.

Configure a provider

Run qwen in a terminal and send /auth at its prompt to choose a provider and set a key.

Do this before trying to use it from Earkeep. Qwen Code is not one of the two agents that can report their sign-in state, so the app cannot warn you: an unconfigured 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 Qwen Code card should read Installed with its version number.

Earkeep launches it in the protocol mode Qwen Code provides:

shell 
npx -y @qwen-code/qwen-code --experimental-acp

So this agent needs Node installed even if you used Homebrew for the CLI itself. 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 Qwen 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.

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 qwen --version: if that fails too, the install did not finish wiring itself in.

"npx wasn't found", or a Node version complaint. Qwen Code wants Node 22 or newer. Upgrade Node and try again.

The session starts and immediately ends. No provider is configured yet. Run qwen in a terminal and send /auth.

It stopped working after an upgrade. The protocol mode is marked experimental by its authors, so it can change between releases. That is the first thing to suspect.

Related

Frequently asked questions

Which Node version do I need?

22 or newer for the npm install. The standalone installers bundle what they need.

Why does Earkeep use npx when I installed with Homebrew?

Because npx is how the protocol mode is launched, 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. Qwen Code calls whichever provider you configured, 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.