A general assistant bolted onto a desktop can read a screen and guess. It cannot know, with certainty, which packages are installed, which services are running, or which configuration has drifted since yesterday. It sees pixels, not state.
We think the operating system is the right place for AI, because the operating system already holds the ground truth.
State, not screenshots
Directioner-OS exposes its own state as structured data: installed packages, running services, open ports, file changes, pending updates. When you ask for an outcome, the AI reasons over that state directly instead of inferring it from what happens to be visible.
The difference matters at the moment of action. A plan built on real state can say exactly what it will touch before it touches it.
Plans you can read
Before anything changes, you get a plan: the steps, the capabilities each step will call, and the blast radius of each. You can read it, narrow it, or refuse it. Nothing acts behind a curtain.
One account, four parts
The product family shares one account and one task model. Directioner-OS is the system. AI-Engineer is the subscription that grants the agent. Directioner-CLI is the local agent, prebuilt in. Aria is the voice that drives it.
Where it is today
Directioner-CLI runs locally today. The backend that will carry identity, entitlements and task history is running. The operating system and the hosted account are in development. The roadmap says so plainly, and we keep it that way on purpose.