Codex to build a home drinks-order system
After a new baby brought more visiting relatives into the house, Roji used Codex to build a small drinks-order system for guests. It was a household tool, with no plan to turn it into a public service. The author says it took about two days to build and was still in use at home.
note.com
Suggested prompt
Suggested prompt written by Agents In Use, not the source author. Replace bracketed inputs and review tool permissions first.
Build a home-only drinks-order PWA: guests choose on a tablet and kitchen staff receive phone notifications. Keep the flow simple and expose unavailable database state.
Reach people exploring AI agents
See placements →Evidence at a glance
Sourced account- Source author
- ロジ (@roji_dev)
- Original account
- Read the source ↗
- Published
- Source link checked
- Reported result
- A home-use guest drinks-order PWA, with a documented Supabase inactivity-pause failure.
- Human involvement
- Roji tried the interface and retained usability and completion decisions; humans supplied the drinks.
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
- Define the living-room tablet and kitchen-phone order flow.
- Iterate on the Codex-built PWA and try the interface.
- Operate it at home and check the database when orders stop appearing.
After a new baby brought more visiting relatives into the house, Roji used Codex to build a small drinks-order system for guests. It was a household tool, with no plan to turn it into a public service. The author says it took about two days to build and was still in use at home.
A tablet in the living room lets visitors choose a drink and place an order. A smartphone in the kitchen receives the notification. The web app is packaged as a PWA so it can launch from the home screen, giving the family a direct interface for the particular task rather than another shared chat thread.
The account describes an iterative Codex development method: let the agent inspect existing code, implement changes and perform build or simulator checks, then have the human try the interface and return feedback. Roji retained decisions about usability and completion. The drink-order tool did not pour drinks or replace the person providing them.
The local app used Supabase's free database plan. That introduced a real operating problem: after a period of inactivity, the project paused automatically and order data stopped appearing. The reported outcome is therefore a working household app with an identified hosting dependency. Its narrow tablet-to-kitchen flow is copyable, but it needs attention to the database's actual operating state.
Prompt
Suggested prompt (written by Agents In Use, not the author's)
Source: note.com · ロジ (@roji_dev)
Frequently asked questions
Was this publicly released?
No. The drinks system was intended for use inside the home.
How did an order reach the kitchen?
Guests selected drinks on a living-room tablet and a kitchen smartphone received notifications.
Why did order data disappear?
The free Supabase project automatically paused after inactivity.
More details
About this account
Codex built and iterated on the household PWA.
Firsthand source opened and read. Suggested prompt written by us from the reported workflow; no original task prompt is quoted.
Credit: ロジ (@roji_dev)
Source published
Added to Agents In Use
Source checked
Tools and topics
Codex · PWA · Supabase · Tablet · Smartphone
Guest drinks · Home tablet · Order notifications
Editorial completeness: 100/100. Measures documented fields, not agent performance or verified outcomes.