Earkeep Download free

Set up Codex in Earkeep

Last updated: · Reviewed quarterly

Earkeep runs the agents you already use, inside the app, against the meeting in front of you. Codex is one of ten built in. Install its command-line tool, sign in 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, which is why there is no inference cost baked into the price of the app.

shell 
curl -fsSL https://chatgpt.com/codex/install.sh | sh

Check it landed:

shell 
codex --version

OpenAI's own Codex CLI documentation covers the Homebrew and npm routes and the editor extension.

Sign in

Run codex in a project directory once and take the Sign in with ChatGPT option, or one of the other methods it offers. Codex is one of only two agents in the roster that can tell Earkeep whether you are signed in, so a missed sign-in shows up as a badge rather than as a puzzle:

shell 
codex login status

Earkeep never sees those credentials. They belong to the CLI, and the app only ever asks the CLI whether they are there.

Confirm Earkeep sees it

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

Earkeep launches it over the Agent Client Protocol using the official adapter, fetched through npx:

shell 
npx -y @agentclientprotocol/codex-acp

So this agent needs Node installed as well as the Codex CLI. 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 Codex 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 Codex from your terminal, where you add the server yourself.

If something goes wrong

"Not found", but it works in your terminal. 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 somewhere your shell profile never adds to PATH is invisible to both. Open a fresh terminal and run codex --version to check.

"Installed but not signed in." Run codex in a terminal, sign in, then reopen Settings.

"npx wasn't found." Install Node. Earkeep starts this agent through its ACP adapter, which 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.

Related

Frequently asked questions

Do I need an OpenAI API key?

No. Earkeep runs the CLI you already signed in to, with whatever account that CLI uses. Earkeep itself has no API keys and no account.

Does this keep everything on my device?

Earkeep's part does: capture, transcription and storage never leave your machine. Codex calls its model provider's API, so a transcript you hand it is a transcript you have sent there. Choosing which meeting to hand over is the control you have.

What is ACP?

The Agent Client Protocol, a standard way for an application to drive a coding agent. Earkeep integrates with the protocol rather than with ten separate agents.

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.