> IMO, an agentic operating system should be not only about "integrating the agent everywhere" but also about providing the compartimentalization and tools to allow working safely with agents when they can reach into every part of the system. It should allow to easily extend the system safely.
Right, but that's also a contradiction. An "agentic" OS is most interesting to the average AI enthusiast if it can, essentially, be your executive assistant: shop for you, book travel for you, manage your agenda, sort through your emails, do your taxes, and so on - possibly including anticipating your needs before you articulate them. That requires human-equivalent access, more or less.
Most people also don't need it - really, most lives are not that complicated - but the allure of your own computerized EA is undeniable. It's your personal servant, how cool is that.
The safe and principled way to use agents is to scope permissions appropriately, restrict them to narrowly-defined tasks, etc, but that also makes the technology a lot more boring. And these silos are very difficult to build when you're interacting with third-party services anyway.
You could as well argue that vibecoding is wrong and that there are principled ways to use agents for precisely-scoped, restricted tasks. Sure, but the entire SF Bay Area is vibecoding now, and if something breaks or gets hacked, that's just the cost of business.
Right, but that's also a contradiction. An "agentic" OS is most interesting to the average AI enthusiast if it can, essentially, be your executive assistant: shop for you, book travel for you, manage your agenda, sort through your emails, do your taxes, and so on - possibly including anticipating your needs before you articulate them. That requires human-equivalent access, more or less.
Most people also don't need it - really, most lives are not that complicated - but the allure of your own computerized EA is undeniable. It's your personal servant, how cool is that.
The safe and principled way to use agents is to scope permissions appropriately, restrict them to narrowly-defined tasks, etc, but that also makes the technology a lot more boring. And these silos are very difficult to build when you're interacting with third-party services anyway.
You could as well argue that vibecoding is wrong and that there are principled ways to use agents for precisely-scoped, restricted tasks. Sure, but the entire SF Bay Area is vibecoding now, and if something breaks or gets hacked, that's just the cost of business.