ScreenSearch v0.4.0 Timekeeper

Sessions: your screen history now has chapters

ScreenSearch groups your captured frames into sessions: a meeting, a Claude Code run, a stretch of focused work. Sessions are additive and pull-based, so nothing about capture, search, Ask, reports, marks, the overlay, or where-was-i changes, and there are no notifications, nudges, or scores.

• Recognition ships from a real-data-tuned taxonomy: Claude Code, Codex, Claude desktop, browser AI, and five meeting apps (Zoom, Teams, Meet, Webex, Discord).
• Sessions appear in the Timeline as lane-packed bands, with a drill-in showing representative frames, extracted user/agent exchanges, and a cited Recap.
• The read-only local API and MCP wrapper gain list_sessions, get_session, and ask_session, so scripts and AI clients can list sessions, open one, and ask a question scoped to a single session. This closes the AI-tool recall request (#88).

Under the hood it is a pure heuristic engine with no model calls, behind a single schema upgrade (v10 to v11) that adds structure only and segments your existing history on first launch.

First release delivered automatically

This is the first release existing 0.3.2-and-later installs receive automatically. The full update path was verified end to end before this tag on a real prior install: update check, background download, signature verification, a restart you initiate, the first-boot schema upgrade, and sessions appearing over pre-existing history, with every earlier feature unchanged.

Note on the installer

The NSIS installer is not Authenticode-signed, so Windows SmartScreen may warn on a manual download (More info, then Run anyway). The updater's own signature (minisign) is separate and verifies every automatic update.