DreamerOS

Memory

Your memory. Not the vendor's.

DreamerOS saves what you tell it in the tools you connected, then brings it back in those tools. You can export it or delete it.

A memory row is one saved fact. How many rows you keep depends on your plan. Export and deletion controls exist on every tier.

Try it free. No card, ever.
Diagram showing saved context moving between supported DreamerOS paths
How account memory can follow supported paths

What it keeps

Facts, preferences, and decisions from connected paths.

DreamerOS picks out the facts, preferences, and decisions worth keeping, so you do not type them in by hand. It reads only the current connected and supported paths (the tools you connected). AI providers handle the context sent to them under their own policy, or your connected account's policy; the current DreamerOS receipt does not prove provider storage or training status.

How this works
extraction: automatic from current connected and supported paths storage: account memory in DreamerOS infrastructure memory rows per plan: /plans.php provider storage or training status: set by the provider or connected-account policy, not proven by the current receipt sensitive-data handling: see the privacy policy and the check result for the path that ran
Diagram showing saved context moving between supported DreamerOS paths
How account memory can follow supported paths

Where it follows you

Current connected paths read the same memory.

Every tool you connected reads the same memory. The goal is one memory across all your tools; today, use the connected path shown in your account. A key you hold lets your own app reach it too.

How this works
doors: current connected and supported paths a key you hold lets your own app reach it your own client can reach it over a key you hold
Diagram showing saved context moving between supported DreamerOS paths
One account memory layer, with Beta limits named

Forget on demand

Export and deletion controls exist on every tier.

You can export your memory, remove one item, or delete all of it. Your account record is meant to stay portable instead of being locked to one model vendor.

How this works
paths: export, single-item removal, and full wipe exist portability: account memory is intended to be exportable on exit
Diagram showing saved context moving between supported DreamerOS paths
Export and deletion paths, pending the full customer walk