Ask Moka About My Schedule — Reading, Booking, and Checking Free Time in Google Calendar
The result first
When I want to know my schedule, I ask Moka — and Moka reads the calendar itself.
“What do I have today?” “Am I free that afternoon?” Moka checks the actual calendar and answers. When a new event is settled, Moka checks the free time first, puts the event in only after I confirm, and then reads it back to make sure the date and time are right.
I am Kurashiki Bouzu (kurashiki-bouzu), born in 1971, a former funeral director now living in an old house in Kurashiki, Okayama, working with Moka (Muse), my AI butler. In the previous article I wrote about Moka handling Gmail. This one is about the other thing closest to daily life: the schedule.
This episode is a rewrite. Since the first version came out, the morning check at my house has grown into one pass: the email report, the phone calls, and today’s schedule, looked at together. The map of the whole series is in the overview episode, “Everything Moka Can Do Across Google Apps.”
What Google Calendar is
A calendar is a schedule book — the paper diary or wall calendar you write appointments on.
Google Calendar is that schedule book kept on the internet. The same schedule appears on your phone and your computer, and an event entered once shows up everywhere. You can:
- Add events with a date and a time
- Look at them later from any device
- Enter a weekly or monthly repeating event once and be done
It is free to use with a Google account. I covered the basics in an earlier article; this one is about what Moka can do with that schedule book once it is connected, with my permission.
What Moka can do in the calendar
Read the schedule
Ask “today,” “tomorrow,” or “this week,” and Moka reads that range and tells me. If I keep more than one calendar — work and private, for example — it can read across all of them. The point is small but large: I ask the schedule book itself, not my memory.
Check free time
“Am I free that afternoon?” Moka finds the hours with nothing in them. That one check, before adding anything new, is where double bookings are prevented.
Add, change, and remove events
Once an event is confirmed, Moka puts it in — timed events, all-day events, with a place and notes attached. It can also create events with a Google Meet video link. Changes and deletions work the same way, and for a repeating weekly event, Moka can change just one occurrence or the whole series.
The way I hand over an appointment is my usual way: a few short words from my phone. There is no long text to type.
Add guests — confirmation first, always
Events can include guests. But an invitation sends a notice to another person, and that is an action that leaves the house. Moka always takes my confirmation before adding guests, and the same goes for change and cancellation notices.
What Moka cannot do — honestly
- It never sends notices to people without my confirmation. Invitations, changes, cancellations — my “yes” comes first
- It cannot see calendars it is not connected to. The permitted range is the whole of what Moka can see
- I have not handed over my password. As with Gmail, the connection is a permission — “reading and writing are allowed for this app” — and I can revoke it at any time
A schedule is a set of promises. A wrongly entered event, or a notice sent without checking, causes trouble for other people too. That is exactly why “confirm before entering” and “confirm before notifying” are fixed rules at my house, not afterthoughts.
How it works at my house, now
My requests go roughly like this:
- The morning check is now one pass: the email report and the phone calls, and then today’s schedule. Once each morning, the whole entrance to the day is checked together
- When a new appointment comes up, I first ask “am I free?” — and only then have it entered
- After an event is entered, Moka reads it back on the spot, and we check the date and time together
Reading back after writing is the house way of checking — the same habit I use for spreadsheets and for articles. The calendar gets the same treatment, because it is the place where a mistake reaches other people.
What I do, and what Moka does
My part
- Decide the appointment itself — whether to go is my judgment
- Confirm whenever a person is invited
- Give the connection permission, and revoke it if I ever stop
Moka’s part
- Read the schedule and check free time
- Enter, change, and remove confirmed events
- Read entered events back and check them for mistakes
Around a schedule book, just like around an inbox, small chores pile up: checking, searching, entering. When Moka carries those, what remains in my hands is only the decision of whether the appointment happens at all. The schedule belongs in the book, not in my head — and the keeping of that book can be handed to Moka. That is the Google Calendar combination.
- November 20, 2026 ― Re-draft created — English version (result-first rewrite of the Japanese article). The previous version (ledger No.174) was published on 2026-11-18. Not published.(3,902 characters)
- November 20, 2026 ― Published as a new article at the author's instruction on 2026-11-20. The previously published version remains untouched.(3,902 characters)
