Your meetings, committed to your own repository

Earkeep's record is already plain files: one JSONL file per day, in a folder you pick, often inside the repository your notes live in. But a folder is only versioned if someone commits it, and committing by hand stops happening by Wednesday. So Earkeep makes the commits and leaves the rest of the repository to you.

It switches on only inside a repository. When the transcripts folder, or one above it, is a git repository, Settings → Storage & Git offers the feature. Otherwise there is one button that runs git init, the only way Earkeep ever creates a repository.

You choose when it commits: when a day ends, when a meeting changes, both (the default), or never.

• When a day ends means five minutes after midnight. A laptop asleep at midnight commits yesterday when it wakes.
• When a meeting changes means saved, ended, resized, renamed or deleted, a few seconds after the last edit, so dragging an edge is one commit. A meeting starting makes no commit, and nor do new transcript lines alone.

One commit per day file, and nothing else. What you have staged yourself stays out of Earkeep's commits, and a day file your .gitignore excludes is left out.

Only on a branch you allow: main (or master), whichever branch is checked out, or one you name. On any other branch nothing is committed and Settings says why.

Each message names the day and the meeting, so git log --oneline reads like the week you had:

Every message is a template you can rewrite in Settings, one per event, with {date} and {meeting} as placeholders.

Push to every remote (the default), to the remotes you pick, or not at all, and every commit stays on your device.

This is the one way a transcript leaves your device, and only to a remote you configured, under your own account. Earkeep has no server in that path.

It is your own git, so your SSH agent, credential helpers and hooks apply as in a terminal. A push that would ask for a password or passphrase fails at once and says why, rather than waiting on a prompt nobody can see.

A remote that has moved on is pulled, not refused. Earkeep does what git pull --rebase --autostash does, then pushes. Recording carries on; editing a meeting is paused for that moment and says so.

When the remote's commits conflict with yours, Earkeep hands the stopped rebase to one of the ACP agents on your machine, such as Claude Code or Codex. It then checks the repository, not the agent's answer: the rebase finished, both sides' commits are there, no conflict marker is left. Only then does it push.

Anything short of that is undone: the rebase is aborted, your branch and uncommitted changes go back as they were, and Earkeep tells you what the agent said. The agent is your own tool with your own key, so what it reads goes wherever that agent normally sends it.

A failure shows above the transcript in plain words (the remote turned your key away, the host could not be reached, a conflict needs you), with git's own words underneath. Earkeep retries every five minutes, so once the cause is fixed the push goes through.

• Private by design: the files this commits.
• Agents and MCP: the agents that write your minutes and resolve your conflicts.
• PKM for developers: notes as a git repository.
• The LLM wiki: what a versioned folder of meetings becomes.