Belief and doubt
Bayesian control means the app tracks how sure it is, not just what it said. Uncertainty and a written constitution gate which tools may run.
Coming soon
BeliefOS
A director for language-model agents you can actually steer. You run it on your machine. You open the folder you want to work on. You connect your Cursor, Codex, Claude, OpenAI, Ollama, or Grok Build login — a provider account does not ship with the app. Then the loop is Ask → Lock → Review → Approve → Go. The model drafts. It does not own the rooms.
BeliefOS is not a game engine, and it is not a chat sidebar next to your files. It is a control plane: a constitution, a 3D belief graph, scoped memory with provenance, and a Tool Host that only runs what the constitution allows. GitHub save and upload apply only to the folder you opened — not automatically to BeliefOS itself.
Live capture
Inside the Director
Project open · graph, Agent, Tools
Live capture
Open a project
Home is “open the folder you want to work on.” Quick open can be this app or a demo project. Recent and a system ledger sit below. GitHub never silently uploads BeliefOS itself.
Director loop
Ask, lock, review, go
There is no Run plan button. Go stays disabled until you Lock and Approve. Plan Go writes the phased plan and stops. Apply Go is a later gate after you Secure. Continuity Fabric can propose changes; you Accept or Reject — identity does not silently mutate.
01
Ask
02
Lock
03
Review
04
Approve
05
Go
Memory with provenance
What the agent remembers is scoped, dated, and revisable. History stays immutable. Retrieval knows current from past.
Local first
Command-line, 3D director viewport, and a desktop app you run yourself. You bring the provider. A hosted service is planned. It is not the product today.
Coming soonTalk to the studio