Set up Cursor Agent in Earkeep

Earkeep does not install agents. It runs the one you already have, on your own Cursor account.

The installer puts the binary in ~/.local/bin, named agent. Cursor's own CLI documentation covers the Windows route and the sign-in options.

Check it landed:

An older install may provide cursor-agent instead, which was the CLI's previous name. Earkeep looks for agent; if that is not what you have, reinstall with the command above.

Run the CLI once in a terminal and sign in to your Cursor account when it asks. There is no reliable way for Earkeep to check this from outside, so this agent's card never shows a signed-in badge either way: the app treats it as ready once the binary is there, on the grounds that a wrong "not signed in" is worse than a missing one.

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 Cursor Agent card should read Installed with its version number.

Earkeep starts it in the protocol mode the Cursor CLI provides:

Cursor documents that mode for editor integrations, so the same command is what an editor would use. Nothing about it is specific to Earkeep.

1. Open a saved meeting.
2. In the agent panel, start a New session and pick Cursor Agent 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 you would rather reach your meetings from Cursor the editor, that is connecting Cursor over MCP instead.

"Not found", but it works in your terminal. Two things to separate. The first is the path: Earkeep probes through your login shell, so a binary in ~/.local/bin is only visible if your shell profile adds that directory to PATH. Open a fresh terminal window and run agent --version. The second is the name: if only cursor-agent answers, you are on the older CLI and reinstalling gets you agent.

The session won't start. Confirm the CLI runs on its own first. An agent that cannot start in a terminal cannot start inside Earkeep either.

The session starts and then ends. The panel shows a notice with a New session button. The old session's log stays on disk.

Nothing here matches your install. Any command that speaks the Agent Client Protocol can be added by hand with Add custom agent in Settings → Agents, which is the escape hatch when a tool moves faster than the built-in roster.

• Agents and MCP: why the agent comes to the meeting rather than the other way round.
• Connect Cursor over MCP: reaching your meeting history from the editor instead.
• All Earkeep how-tos.