Agentic OS
My personal operating system: day plan, inbox, briefing and a voice assistant, on desktop, Android and my own server.
- Role
- Solo: design, development, infrastructure
- Period
- Since July 2026
Overview
I wanted one place that tells me what matters today, instead of ten apps that each want attention.
Agentic OS pulls it together: a day plan with my calendars and university timetable, one inbox across several Gmail accounts and Slack, a morning briefing written by Claude, a world news map and a tracker for new AI models.
Lina, the built-in assistant, listens for her name on my phone and PC. She understands English, German and Swiss German and can put things on my calendar or todo list. Anything that would reach other people waits for my approval.
What I do
- Product and interface design, including its own design system
- One frontend in Vite and plain JavaScript modules, shared by desktop and Android
- Native Android parts: exact morning alarm, widgets, Quick Settings tile, notifications
- The backend: sync, connectors, scheduler and AI agent in one Node process
- Deployment in Docker behind nginx on my Hetzner server, with health checks and nightly backups
Setup
How it's put together, layer by layer.
Interface
One web UI for every device
Desktop
Global hotkey, tray icon, starts with Windows, custom installer
Android
Native widgets, alarm, Quick Settings tile and notifications
Backend
Sync, Google and Slack connectors, scheduled jobs, the agent
Data
Every device keeps an offline copy; tokens are encrypted at rest
AI & voice
Wake word runs on the device; spoken briefings and replies
Hosting
Skills it shows
Tech
One codebase, three platforms
The same web UI ships as a Windows app (Tauri) and an Android app (Capacitor), each with native extras.
Offline-first sync
Every device works offline and syncs with the server; each one has its own revocable token.
AI with guardrails
Mail and news reach the model as data, never as instructions. Actions that would reach other people go to an approval queue.
Running it in production
Containerised deploys, health checks, nightly backups and a monthly cap on AI spend.
Product
Designing for daily use
Built around a real morning: a 30-second spoken briefing, and a widget that shows the next lesson and its room.
Status & next steps
- Next upTake the phone check-ins out of prototype
- ThenPolish the Android widgets and the lock-screen card
- LaterAccounts for more than one person. Every table already carries a user ID, so it means adding a login, not a redesign.
Building something? Let's talk.
A project, a venture to build together, or a role to talk through. I read every message myself.