Skip to content
AI Primer
release

OpenHistory adds MCP access to local work history

OpenHistory is an open-source Mac app that records local activity and generates hourly and daily summaries with on-device inference. Its MCP bridge exposes that work history to local agents using event logs.

3 min read
OpenHistory adds MCP access to local work history
OpenHistory adds MCP access to local work history

TL;DR

Raw JSONL, rather than generated summaries, remains the source of truth, with timeline items tied to source event IDs in the project architecture. The full-delete control also removes saved provider keys and agent connections alongside activity, summaries, and settings, per its privacy documentation.

Event logs, not screenshots

The collector records permitted foreground-app activity and Accessibility changes, then groups them into deterministic episodes before producing timeline, hourly, and daily indexes, according to the repository's architecture.

Its stated exclusions are screenshots, audio, individual key events, password fields, private browser windows, and protected apps or sites. First-run setup does select email activity and recognized Messages, iMessage, and chat activity by default, though each can be disabled.

The read-only MCP projection

The local MCP server exposes a sanitized projection rather than the raw activity log. Its documented tools can:

  • search work history;
  • retrieve a day or timeline item;
  • find referenced files, links, and work surfaces;
  • identify unfinished work.

Each connection receives a dedicated revocable credential, stored as a SHA-256 hash. The server binds to loopback and requires bearer authentication, details in the security policy.

Inference options

OpenHistory can run summaries through Apple's experimental on-device model, an explicitly configured cloud provider, or not generate summaries at all. When automatic summaries are enabled with a provider key, the README says completed episode evidence is sent directly to that provider about every 10 minutes.

Provider keys are encrypted in macOS-backed Electron secure storage and are not returned to the renderer, collector, or MCP clients. The launch itself foregrounded on-device inference in zachtratar's announcement.

Battery claim

The collection-rate tradeoff is central to the design. In a reply about screenshot capture, zachtratar argued that screenshot-based systems must repeatedly capture and analyze far more data, which sharply increases battery cost.

macOS requirements and endpoint

The app requires macOS 14 or later. Apple Intelligence summaries additionally require macOS 26 or later; source builds require Node.js 22 and Xcode with Swift 6.1 or later, while the repository also provides a Mac download path.

Its default MCP endpoint is http://127.0.0.1:47831/openhistory/mcp. Collection remains paused on first launch until the privacy notice is accepted.

Further reading

Discussion across the web

Where this story is being discussed, in original context.

On X· 3 threads
TL;DR1 post
Inference options1 post
Battery claim1 post
Share on X