FAQ & About
Questions people actually ask
Plain answers, including the ones that involve saying "not yet" or "that's a design goal, not a finished feature."
No. AIOS doesn't generate text or compete with foundation models. It's a memory and knowledge layer that sits alongside AI assistants — the assistant still does the reasoning and conversation; AIOS gives it durable, governed context to reason with.
Not quite. A note app stores what you type. AIOS is built around AI assistants reading and writing governed, project-scoped knowledge on your behalf, with routing, authorization, and structured retrieval built in — closer to a governed knowledge system than a notebook.
No, deliberately. The goal is "remember the right things, in the right place, under the right rules" — not a permanent log of every sentence. Passing remarks are meant to be ignored; genuine decisions and project state are meant to be kept, correctable, and supersedable.
Portability across AI clients is the architectural goal AIOS is built toward, not a claim that every AI product is already a validated integration today. Check Status & Roadmap for what's actually connected as of the last review date.
Markdown is plain text and human-readable — you or any tool can open it directly, without needing AIOS itself to be running. That matters for the recovery and ownership story: the canonical record isn't locked inside a proprietary database.
Because a single undifferentiated memory pool makes retrieval noisier and governance harder. Projects give AIOS a boundary to route to, authorize against, and retrieve within — so a question about work doesn't accidentally pull in personal or business context.
It fails closed. Ambiguous routing doesn't get resolved by guessing the "most likely" project — the request is declined or escalated instead of risking a write to, or a read from, the wrong boundary.
No — AIOS is an active experimental architecture and a working personal implementation, not a finished, universal commercial product. It's in real multi-project use, but it's still under active development. See Status & Roadmap for the current line between working, in-development, and exploratory.
Built-in provider memory typically lives inside that one product and travels with it, not with you. AIOS is designed so the durable layer is independent of any single AI provider — the assistant is a replaceable interface to knowledge you keep, rather than the permanent owner of it.
No. A saved transcript is a record of everything said. AIOS is built to extract and govern what's actually useful from a conversation — decisions, reasons, open items — as structured, correctable, project-scoped knowledge, not an ever-growing archive you have to re-read.
About the project
What AIOS is, in one paragraph
AIOS is not another foundation model, a transcript archive, or a note-taking app. It's a developing architecture for a durable, governed, portable second brain that sits behind replaceable AI interfaces. The long-term asset is the knowledge and its governance — the AI answering you today is a replaceable way of reaching it. AIOS is an active experiment: a working multi-project personal implementation with real routing, retrieval, controlled mutation, bootstrap, authorization, and recovery principles behind it, while the broader vision keeps developing.