Replace Reclaim.ai?

KINDA · weekend project
catalog price reference $12/mocategory 🗓️ tasks & calendarreported replacement votes 0

A personal auto-blocker is buildable, but two-way calendar sync, scheduling links, team features, and conflict-safe automation are upkeep-heavy.

the prompt
Build me a personal calendar auto-blocker to replace Reclaim.ai, for one Google
Calendar, mine. Requirements:

- A Node script on a 30-minute cron (node-cron or plain crontab): googleapis for
  Calendar, better-sqlite3 for state, config in a YAML file. No web UI.
- config.yaml defines habits and tasks: name, duration, ideal window (e.g. gym, 60 min,
  weekdays 16:00-19:00), times per week, and priority.
- Each run: read free/busy for the next 7 days and place holds for unscheduled habits
  inside their windows, highest priority first.
- Tag every event it creates with a marker string in the description; the script may
  only ever move or delete events carrying that marker.
- If a meeting lands on a hold, re-place the hold at the next free slot in its window
  and append the move to a plain-text log.
- `blocker plan` prints next week's placements as a table before anything is written;
  `blocker clear` removes every machine-created hold.
- OAuth client credentials and refresh token in .env; budget an hour for the Google
  Cloud console, it is genuinely annoying.
- Out of scope: scheduling links, team coordination, and multi-calendar juggling. Never
  touch or decline events it did not create.
- README: Google Cloud console steps, the calendar scopes needed, and the first-run auth
  flow.

$ open in your agent (prompt prefilled, you press enter) or copy it raw · this prompt is generated from the build plan · improve it via PR

why people still pay

They pay because calendar automation is only valuable if it never makes embarrassing mistakes.

what you lose

xteam coordination

xsmart rescheduling polish

xscheduling links

xcalendar edge cases

xuptime

prior art to inspect before buildingCal.comOpen-source scheduling platform; useful prior art for calendar OAuth and scheduling workfl
reported replacements · 0share on X ↗"Reclaim.ai replacement research and build prompt"
questions
What does the Reclaim.ai verdict mean?

The core job looks buildable, with meaningful gaps: team coordination, smart rescheduling polish. Read the full tradeoff list before committing. This research record is not a hosted IVCIFY tool.

What price does this directory record show for Reclaim.ai?

The directory records $12/month for Starter, checked 2026-07-30. Verify the source before making a purchase decision. This reference stays outside retail Stack Math unless current matched evidence supports the comparison.

What do I lose by replacing Reclaim.ai?

Honestly: team coordination; smart rescheduling polish; scheduling links; calendar edge cases; uptime. If any of those are load-bearing for you, keep paying.

Is there an open-source alternative to Reclaim.ai?

The listed prior art includes Cal.com (Open-source scheduling platform; useful prior art for calendar OAuth and scheduling workfl). Inspect those projects before starting from a blank prompt.