Vibecode Reclaim.ai
track this build5 steps, step by step0%KINDA · weekend project
A personal auto-blocker is buildable, but two-way calendar sync, scheduling links, team features, and conflict-safe automation are upkeep-heavy.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Reclaim.ai. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Reclaim.ai indie build ## Goal Build the smallest trustworthy replacement for the core Reclaim.ai workflow for one developer or a tiny team. ## Scope Read free/busy, create flexible calendar holds for tasks/habits, adjust when meetings move, and expose settings. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - team coordination - smart rescheduling polish - scheduling links - calendar edge cases - uptime If those capabilities are essential, use Cal.com instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief 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. ## Required capabilities - Google Calendar OAuth - scheduling logic - hosted backend - background workers - notifications ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Reclaim.ai. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Reclaim.ai indie build ## Goal Build the smallest trustworthy replacement for the core Reclaim.ai workflow for one developer or a tiny team. ## Scope Read free/busy, create flexible calendar holds for tasks/habits, adjust when meetings move, and expose settings. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - team coordination - smart rescheduling polish - scheduling links - calendar edge cases - uptime If those capabilities are essential, use Cal.com instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build brief 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. ## Required capabilities - Google Calendar OAuth - scheduling logic - hosted backend - background workers - notifications ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Reclaim.ai. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Reclaim.ai product brief ## Problem A personal auto-blocker is buildable, but two-way calendar sync, scheduling links, team features, and conflict-safe automation are upkeep-heavy. ## Product outcome Read free/busy, create flexible calendar holds for tasks/habits, adjust when meetings move, and expose settings. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Google Calendar OAuth - scheduling logic - hosted backend - background workers - notifications ## Explicit non-goals for v1 - team coordination - smart rescheduling polish - scheduling links - calendar edge cases - uptime ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting brief 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Reclaim.ai capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Reclaim.ai indie build ## Goal Build the smallest trustworthy replacement for the core Reclaim.ai workflow for one developer or a tiny team. ## Scope Read free/busy, create flexible calendar holds for tasks/habits, adjust when meetings move, and expose settings. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - team coordination - smart rescheduling polish - scheduling links - calendar edge cases - uptime If those capabilities are essential, use Cal.com instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build brief 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. ## Required capabilities - Google Calendar OAuth - scheduling logic - hosted backend - background workers - notifications ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Reclaim.ai product brief ## Problem A personal auto-blocker is buildable, but two-way calendar sync, scheduling links, team features, and conflict-safe automation are upkeep-heavy. ## Product outcome Read free/busy, create flexible calendar holds for tasks/habits, adjust when meetings move, and expose settings. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - Google Calendar OAuth - scheduling logic - hosted backend - background workers - notifications ## Explicit non-goals for v1 - team coordination - smart rescheduling polish - scheduling links - calendar edge cases - uptime ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting brief 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Reclaim.ai capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
They pay because calendar automation is only valuable if it never makes embarrassing mistakes.
xteam coordination
xsmart rescheduling polish
xscheduling links
xcalendar edge cases
xuptime
share on X ↗"I just replaced Reclaim.ai ($12/mo) with one prompt"
Reclaim.ai pricing
| plan | monthly | annual (per mo) | what you get |
|---|---|---|---|
| lite | $0/user | $0/user | 5 AI agents; 1-user team; 1-week scheduling range; 1 calendar sync; 1 scheduling link. |
| starter | $12/user | $10/user | Up to 10 seats; 10 AI agents/seat; 8-week scheduling range; 3 calendar syncs; 3 scheduling links. |
| business | $18/user | $15/user | Up to 100 seats; 100 AI agents/seat; 12-week range; unlimited calendar syncs and scheduling links. |
| enterprise | — | $22/user | 100+ seats; unlimited AI agents; 12-week scheduling range. |
free tier5 AI agents; 1-user team; 1-week scheduling range; 1 calendar sync; 1 scheduling link.
billingLite free; Starter/Business monthly + annual; Enterprise annual only
hidden costsCumulative attendee users are billed separately: annual Starter packs cost $8/$16/$24/$32 per month for 3/6/9/12 attendee users; annual Business packs cost $12/$24/$36/$48 for 6/12/18/24. Monthly packs cost more. Each pack includes one free paid seat.
verified 2026-08-14 · source ↗
Vibecode Reclaim.ai
Kinda. The core of Reclaim.ai is buildable in a weekend with the prompt on this page, but there are real gaps: team coordination, smart rescheduling polish. Read the honest list above before committing.
How much does Reclaim.ai cost?
Reclaim.ai costs about $12/month (Starter, checked 2026-07-30), which is $144 per year.
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?
Yes: Cal.com (Open-source scheduling platform; useful prior art for calendar OAuth and scheduling workfl). Using prior art is also vibecoding; the prompt is for when you want it exactly your way.