
Life OS
A private chief of staff, in plain files

A private chief of staff, in plain files
A self-hosted AI chief of staff. Coding agents work over a private markdown repo and talk to me through a Telegram bot, by text and by voice.
I wanted one place that knows my calls, tasks and plans, and an assistant that preps me before a meeting and reminds me at the right moment. Life OS is that assistant.
My notes live as plain markdown in a git repo I own. AI coding agents (Claude Code, Codex or OpenCode) do the work inside that repo. I talk to them from my phone through a Telegram bot, by text or voice, and approve changes with a tap.
Memory is files and agents are swappable, so changing tools loses nothing. Models decide what to do; simple scripts deliver the timers, reminders and syncs, so a reminder never depends on a model being up.
Agents read by default and write only where they own the target. Every write is a dry run first, then confirmed, logged and undoable. Private data and web research run in separate passes, and every fact carries its source and date.
The design went through three versions, backed by two research rounds and a study of about 20 public setups. Version 3 moves the hub to an always-on home server, with local speech-to-text and text-to-speech and a stack of free tools only. The server base is in place. The Telegram bridge and voice are next.
Alongside it, I designed and set up a full Notion workspace: 10 linked databases for tasks, projects, content, knowledge, trips and more, 49 views, a home dashboard, and a rules page that tells the agents how to use it. I then checked it against the spec and fixed what did not match.
Next project

A local chat that can draw