Check-ins

A check-in is a scheduled prompt Lucille sends you to ask how you're doing or to nudge you toward a recurring thing. They're configured per user in the web app.

What they look like

A check-in is usually a short question with optional buttons. Examples:

• "How are you doing?" with ✅ OK / 😕 Not OK buttons.
• A morning prompt: "Anything you want to capture from yesterday?"
• A weekly nudge: "How did the focus blocks go this week?"

You can answer with the button or type a free-form reply. Free-form answers become notes Lucille can refer back to (see Thoughts).

Where to manage them

In the web app: /integrations/checkin (or /checkins). This is where you create new check-ins, change their schedule, or pause/resume them.

How they trigger

Check-ins fire on a schedule (e.g. every weekday at 8am). The server runs the scheduler and dispatches the prompt — there's nothing you need to do on your phone for it to arrive.

If you want a check-in to run right now, ask Lucille in chat ("run my morning check-in"). The intent is checkin.run_checkin_now internally.

Snoozing / skipping

If a check-in arrives at a bad time, just ignore it — Lucille won't keep re-asking. The next scheduled run will go ahead as normal. To stop a check-in entirely, pause or delete it from the web app.

Why they exist

Check-ins are how Lucille gathers signal she wouldn't otherwise have. A calendar entry tells her when something happened; a check-in tells her how it went. Over time these answers become inputs to thoughts and the day brief.