Your first served day.

1 Install Diurna

Download the latest release for macOS and open it. Diurna lives in your menubar — a small dot that tells you whether it's recording. Nothing is collected yet: a bare Diurna has no sources.

macOS only for now — the check-in prompt and menubar experience are built native-first rather than lowest-common-denominator.

2 Add your sources

Open Settings → Community plugins and install the sources you want. Before anything runs, Diurna shows you the plugin's capability sheet — exactly what it may read, where it may connect, what it may run. Good starters:

• Git commits — every commit you author becomes a point signal.
• ActivityWatch — window focus as extent signals (requires ActivityWatch running locally).
• Periodic check-in — a Spotlight-style prompt that asks “What are you working on?” and records your own words. Touches nothing else.

3 Connect Claude Desktop

Diurna serves your days over MCP (Model Context Protocol) via a stdio server that the consumer spawns on demand. For Claude Desktop, add this to claude_desktop_config.json and restart:

{
  "mcpServers": {
    "diurna": {
      "command": "diurna",
      "args": ["mcp"]
    }
  }
}

The server exposes three read-only tools: ping, get_day (one day's signals as a flat, time-ordered list, optionally filtered by kind) and list_days. There is no write tool and no aggregation — serving the record is the whole job.

4 Ask about your day

Now the interesting part happens in the consumer, not in Diurna:

• “What did I actually do yesterday?”
• “Show me only my commits from Tuesday.”
• “Draft my worklog from today's signals, grouped by project.”

Claude reads the flat signal list and does the interpreting — which meeting mattered, which ticket that commit belonged to, what the day amounted to. Diurna never guesses; it just remembers.