[verdict][generated prompt][source: reclaim.ai]
Can I vibecode Reclaim.ai?
// buildable in a weekend, but real gaps stay open
A personal auto-blocker is buildable, but two-way calendar sync, scheduling links, team features, and conflict-safe automation are upkeep-heavy.
confidence: high
what it is: Smart calendar scheduling for habits, tasks, breaks, and meetings
Buildability index · an editorial game
- Price 12 $/month · per seat weight: plus 2
- Time multi-day weight: plus 1
- Category tasks and calendar no weight
- Moat integrations · execution quality weight: minus 2
- Confidence high weight: plus 1
- What you lose 5 items weight: minus 2
- Site reclaim.ai (si apre in una nuova scheda) no weight
They cancel out. This is where it comes down to how much the subscription annoys you.
Gioco editoriale: il verdetto dice se un agente può, l’indice se conviene.
What you build
Read free/busy, create flexible calendar holds for tasks/habits, adjust when meetings move, and expose settings.
what you need
- Google Calendar OAuth
- scheduling logic
- hosted backend
- background workers
- notifications
Clear case where the product is integrations plus trust, not AI magic.
The prompt
A weekend with a coding agent. The gaps that stay are right below, under “what you lose”.
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.Prompt generated from the data on this page, not reviewed by hand yet. In English on purpose — it is the language coding agents work best in.
What you lose
- team coordination
- smart rescheduling polish
- scheduling links
- calendar edge cases
- uptime
Why people still pay
They pay because calendar automation is only valuable if it never makes embarrassing mistakes.
moat: Integrations Execution quality what a moat is
calendar integration/reliability
Who has already built it
Starting from here is still vibecoding: the prompt is for when you want it exactly your way.
- Cal.com (opens in a new tab) — Open-source scheduling platform; useful prior art for calendar OAuth and scheduling workfl (alive)
What it costs in a year
12 $/mese 144 $/anno
Listino 12 $ al mese a persona su Reclaim.ai. L’anno è dodici mesi pieni, senza sconti annuali.
Do you agree?
The vote balance
Ancora nessun voto: il tuo è il primo.
Nessun voto ancora — il primo pesa.
