A household meal planner
Dinner, handled.
No spreadsheet required.
Heisenberg is a small Telegram bot that plans the dinner week for Aniket and Rushil. Changes happen in the group chat, and the final menu stays in one place.
- Friday, 6 PM
- fresh weekly draft
- 5 dinners
- planned each week
- 2 people
- separate memories
How it works
A draft, a few replies,
a confirmed week.
Everything happens in the household Telegram group. There is no separate planning dashboard.
-
01
A draft arrives
Every Friday at 6 PM, Heisenberg assembles the plan using the active dish list, rotation history, and household rules.
-
02
Change it by chatting
Tag the bot or reply to its message to swap a dish, add a side, change a preference, or ask why something was chosen.
-
03
Confirm and cook
The server checks the result before saving the confirmed menu and its prep notes on persistent storage.
An example
Three things
it handles.
These representative screens show a weekly draft, a menu edit, and a personal memory.
The week, plated.
Under the hood
One service,
intentionally.
A Node.js process runs the bot, scheduler, API, MCP endpoint, and landing page. JSON data lives on one Railway volume.
The landing page and health check are public. /api and
/mcp use separate bearer tokens, and Telegram updates
are restricted to the configured group.
A small household project
Less “what should we eat?”
More eating.
The bot only responds inside its configured Telegram group.