Memory
Your memory. Not the vendor's.
DreamerOS stores memory from currently connected and supported paths, then carries it into those paths.
Memory rows run from 100 on Light to 100,000 on Elite. Export and deletion controls exist on every tier; the full browser path remains In Beta 2.0 until its customer walk passes.
Try it free. No card, ever.
What it keeps
Facts, preferences, and decisions from connected paths.
This structured layer holds what current connected and supported paths pull. DreamerOS can extract facts, preferences, and decisions worth keeping, so you do not have to type them in by hand. Past ChatGPT and Claude ingestion, plus full cross-engine parity, are In Beta 2.0. Not every conversation or engine automatically ingests today. Model providers process the context sent to them under that provider or connected-account policy; the current DreamerOS receipt does not prove provider storage or training status.
How this works
Where it follows you
Current connected paths read the same memory.
This is one memory surface for the doors that are currently connected and supported. Past ChatGPT and Claude ingestion, plus full cross-engine parity, are In Beta 2.0. The goal is one memory layer across your tools; today, use the connected path shown in your account and do not assume an unconnected conversation was ingested.
How this works
Forget on demand
Export and deletion controls exist on every tier.
Account memory includes export, single-item removal, and routes that delete all memory. The full browser path on every tier remains In Beta 2.0 until a non-HC customer completes the walk. Your account record is meant to stay portable instead of being locked to one model vendor.
How this works