A choice of execution
The planned desktop and mobile experiences include a path to local AI where devices and models support it, alongside connected cloud tools. It is a product direction, not a claim that this HTML runs an offline language model.
What can stay local
Some reasoning, drafting and document tasks can be designed around local processing. A connected service still receives the data needed to perform its task; local AI does not make every future workflow offline or private by default.
Always-on work needs an available worker
Scheduled background operation needs an awake, authorised desktop, server or other supported worker. A closed browser or suspended phone cannot be described as a guaranteed 24-hour worker. Email delivery, calls and online publishing need connectivity.
Keep the controls visible
The intended system makes permissions, selected providers, budgets and approvals explicit. Company knowledge should remain portable rather than trapped inside one model's conversation history.