Connect Apple Calendar

Two things, and one of them you almost certainly have already.

• The calendars have to be in the macOS Calendar app. This path reads what that app holds, so an account you only ever open in a browser tab is invisible to it. Adding it in System Settings → Internet Accounts is enough; you do not have to keep Calendar open.
• Earkeep has to be running. Connecting is done from Settings inside the app.

This is the one connection that is macOS-only, because EventKit is. The other three work the same way on any platform Earkeep runs on.

1. Open Earkeep and press Settings, at the bottom of the left rail.
2. Go to Calendar.
3. On the Apple Calendar row, press Connect.
4. macOS shows its own calendar-access prompt. Allow it. This is the system asking on Earkeep's behalf, so the decision is recorded by macOS rather than by the app, and you can change it later in System Settings.
5. The row changes to Connected. Turn on Create spans from events if you want each event to become a meeting on its own.

That last switch is the one that does the work. Without it Earkeep shows you the day's agenda beside the timeline and leaves the marking to you; with it, an event under way starts a span by itself. Either way the transcript is the same, because capture never depended on the calendar.

It reads event names and times, on your own device. That is what it needs to know where the meetings were in your day, and it is all it asks for.

It never writes to your calendar. The only thing Earkeep ever writes is a span marker in your own transcript file.

Nothing crosses the network, because there is nothing to cross it with. This connection has no server on the other end. Earkeep has no server at all. Two applications on one machine are talking through an operating-system API, and that is the whole of it. The wider picture is on private by design.

All-day events, declined invitations and cancelled events never become spans. Neither does an event during which nobody said anything. The rules that turn an event into a meeting are the same for every provider and are described on calendar connection.

"Calendar access is denied." The permission was refused at some point, and macOS will not ask twice. Open System Settings → Privacy & Security → Calendars and turn Earkeep on. If you are running a development build, the entry may be listed under your terminal application rather than under Earkeep.

If the switch is not there at all, macOS has no record of the request. Reset it and connect again:

The row says connected, but no events appear. Check that the calendars you expect are actually in the macOS Calendar app, and that the day you are looking at has events on it. Press Sync now to skip the wait.

You disconnected, and macOS still lists the permission. That is correct. Disconnecting removes the account from Earkeep; it does not revoke a system permission, because permissions are managed by macOS and not by the apps that hold them. Turn it off in System Settings if you want it gone.

• Calendar connection: what an automatic span is, and what happens when the meeting doesn't match the invite.
• Connect Google Calendar and Microsoft Outlook: the two account-based paths.
• Connect a calendar link (ICS): the path that needs no account and no IT approval.
• All Earkeep how-tos.