Your prep plan, on your calendar — never written without your say-so.
Loop turns your goal and your real availability into a week-by-week study plan, drafts it around your existing commitments, and writes it to Google Calendar only after you approve.
Loop is in limited testing — sign-in is open to a small allowlist of Google accounts (≤100 testers). If yours isn’t on it yet, you’ll be told at sign-in rather than let in halfway.
Propose, review, approve — then it’s on your calendar.
A deterministic pipeline does the routing and scheduling; the AI only proposes candidates. The approval gate is the hinge — nothing reaches your calendar before it.
Onboard
A quick form: your goal, weekly hours, deep-work windows, and an optional résumé paste.
Generate
The AI proposes a structured plan; deterministic code validates and schedules it around your busy times.
Review & adjust
Drag any proposed block to a new time or day. Every move is re-checked on the server.
Approve
You confirm the exact set of events. The payload is hash-locked to what you saw.
the gateWrite & verify
Loop writes to one calendar and re-reads every event to confirm it landed. If anything can’t be verified, the plan is not activated — you see exactly what did and didn’t land.
Check in & calibrate
Mark sessions complete or missed. Honest progress — telemetry tunes the plan over time.
Safe by construction — not by good intentions.
No silent calendar writes
Every write needs your explicit approval. Loop never edits your calendar on its own.
Hash-checked at write time
The approved plan is fingerprinted; if anything changed since you approved, the write is refused.
Verified after writing
Each event is re-read after writing. Anything unverified blocks the plan from activating — nothing is silently treated as done.
Your data stays yours
Your résumé and plan live on your account and are never used for training.
Scoped, revocable access
Loop reads your busy times and writes to a single dedicated calendar — revoke any time.
Typed failures, never dead ends
When it can’t proceed, it says exactly why — and how to recover.
What Loop accesses from your Google account — and why
Who you are
email · profileYour email address and display name, used to sign you in and identify your account. Nothing else from your Google profile.
When you’re busy
calendar.freebusyBusy/free time ranges only, so the scheduler plans study sessions around your existing commitments. Loop cannot see event titles, descriptions, attendees, or locations on your calendars — the permission it requests does not allow it.
One calendar Loop creates
calendar.app.createdApproved study sessions are written to a dedicated calendar Loop creates in your account. Loop cannot edit or delete events on any other calendar.
Your Google data is used only to provide these features. It is never sold, never shared with third parties, never used for advertising, and never used to train AI models. You can revoke Loop’s access at any time from your Google Account permissions, and it stops working immediately.
LLMs propose. Deterministic infrastructure disposes.
The AI generates candidates and explanations. Routing, validation, scheduling, the approval gate, calendar writes, and verification are deterministic code.
What Loop is not.
Put your prep on the calendar — safely.
Limited testing — a small allowlist of Google accounts for now.