Personal
A personal life-OS in your messenger
Give Pi read access to the feeds that make up your day and let it assemble a single brief, delivered to the messenger you check first.
Who it's for: Individuals who want one assistant across every app instead of ten disconnected ones.
The problem
- Your day is scattered across a dozen apps that never talk to each other.
- Cloud life-assistants want all of that data centralised on their servers.
- One identity should follow you across messengers, not fragment per app.
With openclawOS
- Pi's tools pull from your calendar, notes and dashboards, then compose one brief.
- openclawOS routes one identity across channels, so it's the same agent on iMessage and Telegram.
- It's self-hosted, so the personal data stays yours.
How to set it up
- 1
Install openclawOS
Start the gateway on a machine that's always on.
- 2
Pair your daily channel
Pair iMessage or Telegram — wherever you look first.
- 3
Connect your feeds
Give Pi read access to calendar, notes and any dashboards.
- 4
Get a brief
Ask for a morning brief and Pi assembles it into one message.
Common questions
Yes. openclawOS routes one identity across channels, so switching from iMessage to Telegram keeps the same Pi and its memory.
Related use cases
- Long-running research with persistent memory Forward a paper or a link and get a structured summary back — with sessions and vector memory that survive reboots via sqlite-vec.
- Conversational home and IoT automation Trigger devices, query dashboards and kick off jobs by messaging Pi — real tool use over WhatsApp or iMessage instead of brittle IFTTT chains.
Ready to build this?
Install openclawOS, pair a channel, and put Pi to work. The whole loop is under ten minutes.