Set up Codex in Earkeep

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

• The Codex CLI, installed and signed in. The sections below walk through it.
• Node.js 18 or newer, which brings npm and npx with it. Earkeep starts Codex 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 18 or higher:

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.

Check it landed:

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

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:

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

1. Open Earkeep and press Settings, at the bottom of the left rail.
2. Go to Agents.
3. The Codex 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 over the Agent Client Protocol using the official adapter, fetched through npx:

So this agent needs Node installed as well as the Codex CLI. If Node is missing or older than 18, 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 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.

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

"Needs setup", asking you to sign in. Run codex in a terminal, sign in, then reopen Settings.

"Needs setup", asking for Node.js. Install Node.js 18 or newer, or update the one you have (brew upgrade 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.

• Agents and MCP: why the agent comes to the meeting, not the other way round.
• Connect Codex CLI over MCP and Codex in your IDE.
• All Earkeep how-tos.