Set up Qwen Code in Earkeep

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

• Qwen Code, installed and signed in. The sections below walk through it.
• Node.js 22 or newer, which brings npm and npx with it. Earkeep starts Qwen 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, on your own account.

Homebrew works too:

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

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

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.

1. Open Earkeep and press Settings, at the bottom of the left rail.
2. Go to Agents.
3. The Qwen 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 in the protocol mode Qwen Code provides:

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

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

"Needs setup", asking for Node.js. Qwen Code wants Node 22 or newer. Install or upgrade Node (brew upgrade node), then reopen Settings.

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.

• Agents and MCP: why the agent comes to the meeting, not the other way round.
• All Earkeep how-tos.