How to use Codex for a read-only family calendar
Codex connected the family’s Apple calendar read-only to a Raspberry Pi and iPad display, retrieving 14 checked events while keeping editing on the iPhone.
note.com
Original prompt
Shared by the source author. See source notes for context.
新しい予定入力画面は作らない
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- ぶんぐー | 暮らしメモ (@wise_bee4925)
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- The source reports fourteen real family events retrieved and displayed through a read-only Raspberry Pi integration; outage fallback is designed rather than demonstrated.
- Human involvement
- The owner issued and entered the password locally, checked calendar identity and compared real events; credentials stayed outside chat and Git.
A linked account supports attribution. It does not mean we independently reproduced its result.
Report an issue with this case
Open correction emailOpens your email app with the case link included. Nothing is sent automatically.
How the agent did it
- The owner required reuse of the family Apple calendar without a new event-entry interface.
- Codex connected through read-only CalDAV and the owner verified fourteen retrieved events.
- The agent implemented SQLite caching and separate iPad and phone display layouts.
ぶんぐー used Codex to connect an existing family Apple calendar to an always-visible household display. The constraint was explicit: keep entering events on the iPhone and avoid creating another schedule-entry screen.
Codex first worked on a small CalDAV connection that listed calendars and read the intended family calendar. The owner generated an app-specific password and entered it locally rather than pasting it into chat. The account reports retrieving fourteen real events and checking that the correct calendar and appointments had been selected.
The implementation cached events in SQLite on a Raspberry Pi. A permanent iPad display showed a Monday-start, twenty-one-day grid, while the phone layout allowed horizontal scrolling. Scheduled retrieval was separated from display rendering, so the design could retain the last known cache if fetching failed.
The demonstrated result is the working read-only integration and family-event display. The post does not report an outage test proving the fallback, and later LINE-notification work is outside this case. Human checkpoints included local credential setup, calendar selection and comparing the actual displayed events, while the existing Apple calendar remained the place where the family edited its schedule.
Prompt
Original prompt
Source: note · ぶんぐー | 暮らしメモ (@wise_bee4925)
Frequently asked questions
Where does the family edit events?
The existing iPhone and Apple calendar workflow remains the editing interface.
Was the calendar connection actually exercised?
Yes. The author reports retrieving and checking fourteen real events.
Was the cached fallback proven during an outage?
No. The source describes the design, not an executed outage test.
More details
About this account
The owner required reuse of the family Apple calendar without a new event-entry interface. Codex connected through read-only CalDAV and the owner verified fourteen retrieved events.
Full Japanese primary article and exact publication metadata opened. Original prompt excerpt means no new schedule-entry screen. Fourteen events are author-reported; future LINE work and untested outage claims are excluded. Original prompt excerpt.
Credit: ぶんぐー | 暮らしメモ (@wise_bee4925) — note
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex · Apple Calendar · CalDAV · SQLite · Raspberry Pi · iPad
shared calendar · read-only integration · cached display
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.