Set up opencode in Earkeep
Last updated: · Reviewed quarterly
Earkeep runs the agents you already use, inside the app, against the meeting in front of you. opencode is one of ten built in. It is provider-agnostic, so it is the easiest of the roster to point at a model you already pay for, or at one running on your own machine.
Install it
Earkeep does not install agents. It runs the one you already have.
curl -fsSL https://opencode.ai/install | bash
Homebrew and npm both work too. Check it landed:
opencode --version
The opencode site is the reference for the other routes.
Log in to a provider
opencode brings no model of its own. Run it once in a terminal and connect it to whichever provider you intend to use: an existing GitHub Copilot or ChatGPT account, an API key from anyone, or a model running locally.
That last option is worth a moment if privacy is why you are here. Earkeep keeps capture, transcription and storage on your device, and the agent is normally where that stops, because most agents call somebody's API. Pointing opencode at a local model is the one configuration in this roster that keeps the whole loop on your machine. It is slower and usually less capable, and it is a real choice rather than a theoretical one.
Earkeep never sees those credentials. They belong to opencode.
Confirm Earkeep sees it
- Open Earkeep and press Settings, at the bottom of the left rail.
- Go to Agents.
- The opencode card should read Installed with its version number.
Earkeep starts it in the protocol mode opencode provides:
opencode acp
opencode documents that mode for editor integrations, so the same command is what an editor would use. Nothing about it is specific to Earkeep.
Use it on a meeting
- Open a saved meeting.
- In the agent panel, start a New session and pick opencode and a working directory.
- 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. The install script puts the binary under your home directory, and Earkeep probes through your login shell, so it is visible only if your shell profile adds that directory to PATH. Open a fresh terminal window and run opencode --version to check.
The session starts and immediately ends. Run opencode acp in a terminal on its own. If it exits there, no provider is configured yet.
No signed-in badge appears. That is expected. Only two agents in the roster expose a reliable non-interactive check, and opencode is not one of them.
Related
- Agents and MCP: why the agent comes to the meeting rather than the other way round.
- Local-first AI at work: the case for keeping the whole loop on your own machine.
- All Earkeep how-tos.
Frequently asked questions
Can I use this with a local model?
Yes, and it is the reason this agent is worth a look. opencode connects to a great many providers, local ones included, which makes it the straightforward way to keep the whole loop on your own machine.
Do I need Node?
No, not with the install script. opencode ships its own protocol mode, so nothing from the Node ecosystem is involved at launch.
Does this keep everything on my device?
Earkeep's part does. Whether the agent's part does is decided by the provider you connected opencode to, which is the one place in this roster where that is genuinely your call.
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
14-day full trial, no account required.