Providing the structure of a unified framework: APIs, safeguards, routing to the appropriate model or pipeline, and controlled access to devices and data. The capability is already there. What’s missing is a sane permission system that operates at the level of intent. Having used OpenClaw, that’s IMO the missing piece. It’s a fun experience, but in its current state I would not trust it to autonomously run any meaningful part of my life.

UX-wise, chat is kind of a crutch. It’s slow and inherently limiting. I imagine something closer to a natural, ongoing conversation paired with an execution layer: some sort of approval or review dashboard where planned actions are ready for approval or returned for refinment before they happen. Probably with a conservative moderator agent in the loop that flags things based on preferences and hard-coded policies.

Calling it an OS isn’t accurate, I agree. But that's how people will perceive it. Most people already think of the application layer on Android as "the OS," not the kernel or drivers. This will be the first-class interface on your device, so that’s what it gets called. It doesn’t mean browsers or dedicated applications go away.

Three years ago I would not have thought the IDE would stop being the application I spend most of my time in. Now it’s mostly a passive code viewer and Git browser.

Compare that to everyday workflows. Researching anything still feels incredibly antiquated. Buying a phone, planning a vacation, comparing options means opening dozens of tabs, copy-pasting specs or prices into spreadsheets, reading through fine print, dealing with low-quality or honestly untrustworthy reviews, checking distances manually on maps. It’s boring and tedious work.

Meanwhile, in a professional life, these systems already behave like a team of secretaries: always available, reasonably competent, and scalable. Not perfect, but easily good enough to offload a huge amount of cognitive overhead.