WeSearch

Horolog – a self-hosted, open-source alternative to Reclaim.ai

·7 min read · 0 reactions · 0 comments · 4 views
Horolog – a self-hosted, open-source alternative to Reclaim.ai
TL;DR · WeSearch summary

Horolog is an open-source, self‑hosted AI calendar that runs on a user's own machine and integrates with any preferred language model. It offers features such as smart task scheduling, habit management, dynamic calendar sync, and productivity analytics while keeping data local and avoiding telemetry. The project positions itself as a privacy‑focused alternative to services like Reclaim.ai, providing rapid re‑planning and a modular architecture.

Key facts
About this source

Hacker News (AI / LLM) files mainly under ai. We currently carry 4,222 of its stories.

Original article
GitHub
Read full at GitHub →

Story provenance

Source · retrieval · rights · ranking — open for full record
inspect →

Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.

Record

Original publisherGitHub
Canonical URLhttps://github.com/ujjwalredd/horolog
Publication timeMon, 10 Aug 2026 03:51:31 +0000
Retrieval time2026-08-10T04:05:41.885Z
Last seen2026-08-10T04:05:41.885Z
Headline sourcePublisher (no WeSearch rewrite)
Excerpt sourcepublisher body
Excerpt methodFirst ~120 words (~800 chars) of extracted publisher body, fair-use limited.
SummaryWeSearch · cerebras-chat (WeSearch summarizer)
Summary source textcontentText
Citation coverageSummary is a WeSearch-generated derivative; primary citation is the original publisher URL.
ClusterDL_DV0fpQG6y · 1 stories
Cluster logicGrouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison.
Ranking reasonStory pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking.
Publisher visitYes — open original
Substitutes article?No — link-out required for full text

Rights status (four layers)

Publisher-declared
No publisher-confirmed rights record for this source yet.
Machine-readable
No source-specific machine-readable restriction detected beyond the public feed.
WeSearch interpretation
WeSearch declared handling (basis: Derived from the published RSS/Atom feed). This is WeSearch policy, not a legal grant on the publisher's behalf.
Unknown
Retrieval and training permissions are not asserted unless the publisher confirms them.

WeSearch handling by dimension

Indexing May the item be indexed (stored, ranked, made findable)? Allowed
Snippet May a short excerpt of the publisher's text be shown? Allowed
AI summary May WeSearch generate its own short summary of the article? Limited
Retrieval / RAG May the content be exposed for third-party retrieval-augmented generation? Not asserted
Model training May the content be used to train AI models? Not asserted
Commercial reuse May the content be reused commercially? Not permitted

Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.

Opening excerpt (first ~120 words) tap to expand

Horolog An open-source, self-hosted AI calendar that defends your time. Horolog places focus time, habits and tasks around the meetings you actually have - then keeps them there. It runs entirely on your own machine, against your own calendar, with whichever language model you already trust. It is a working alternative to Reclaim.ai (acquired by Dropbox in 2024). At the time of writing no open-source equivalent existed: Cal.com covers booking links, but the auto-scheduling half - focus time, habits, priority preemption, automatic rescheduling - had not been built in the open. git clone https://github.com/ujjwalredd/horolog.git && cd horolog cp .env.example .env docker compose -f infra/docker-compose.yml up # → http://localhost:3000 No account. No telemetry. Nothing leaves the machine.

Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.

Anonymous · no account needed
Share 𝕏 Facebook Reddit LinkedIn Threads WhatsApp Bluesky Mastodon Email

Discussion

0 comments

More from GitHub