DreamerOS
LIVE AND SHIPPING

One URL.
Every AI tool you already have open.

You have five AI tabs open right now. They have never met each other. ChatGPT does not know what you told Claude. Cursor does not know what Perplexity found. You are the only shared memory between them, and that is exhausting. Connect is the middleware that fixes that. One MCP URL, one API key, paste them once. Your memory and your rules travel with you everywhere.

Open Connect See the clients

Paste flows on Light. API key and one-click installs on Pro and above.

The actual problem

Your AI tools have never
met each other.

It is not that the tools are bad at memory. It is that none of them have a shared protocol for knowing who you are. So you re-introduce yourself five times a day. We fixed the seams, not the tools.

Five tabs, five strangers

Every AI tool you open starts fresh. It has no idea what you decided in the last one. Your preferences, your project context, your tone - all of it lives in your head because there was nowhere else to put it. Until now.

Your rules reset at every door

You set governance rules in one place. You move to another tool. Gone. The filter you set, the no-fly topics, the way you like things written - each client treats you like a first-time visitor. DreamerOS is the memory that persists between them.

How to fix it in under 5 minutes

Two steps.
One paste each.

No new client to learn. No workflow to change. You keep using the tools you have. We just wire them together in the middle.

1

Generate your key in Connect

Takes about four seconds. You get one MCP URL and one API key tied to your DreamerOS account. That is all you need.

2

Paste it into every client you use

Five clients have a one-click install button. Four web clients get a config snippet. Either way, the paste takes longer to describe than to do.

3

Go back to actually building

That is it. Every client you just connected now shares the same DreamerOS layer. Your memory lives in the middle. Context does not die at the boundary anymore. You never do this again.

Your AI tools

If it speaks MCP,
it speaks DreamerOS.

Nine clients wired in. Five get a one-click install button - open Connect, click, done. Four are web-based and get a paste snippet instead. Same memory, same governance, different delivery method.

One-click install
Claude Desktop
Anthropic
One-click
Cursor
Anysphere
One-click
VS Code
Microsoft
One-click
Windsurf
Codeium
One-click
ChatGPT
OpenAI
One-click
Paste flow - web clients
Claude.ai
Anthropic
Paste flow
Perplexity
Perplexity AI
Paste flow
Gemini
Google
Paste flow
Grok
xAI
Paste flow
Where DreamerOS ships your work

You approve it in chat.
DreamerOS puts it where it belongs.

Once you approve something in Automate, DreamerOS handles the rest - the commit, the PR, the deploy, the message. No clipboard. No tab switching. No "copy this, paste that, go back here." Railway is live. Seven more are queued and shipping in order.

Railway
Live
GitHub
Coming
Vercel
Coming
Slack
Coming
Notion
Coming
Linear
Coming
Gmail
Coming
Stripe
Coming

Each outbound integration means one fewer manual step between "approved" and "shipped." We are wiring them in the order they actually matter.

What your tier gets you

Paste flows on Light.
The API key lives on Pro.

If you have a free account, the web-client paste flows work today. The MCP API key - which is what powers one-click installs, local clients, and outbound automation - requires Pro or higher. Worth it.

Tier Web paste flows MCP API key Outbound automation
Light (free) Yes - -
DreamWeaver Yes - -
Pro recommended Yes Yes As providers ship
Elite Yes Yes As providers ship
Self-service security hygiene

Rotate your key
in one click.

If a key leaks, or it is just time for a fresh one, rotation lives behind a single endpoint on the gateway. Old key invalid the moment the new one issues. Every rotation logged to your governance audit trail.

POST /api/v1/me/rotate-key 
curl -X POST https://dreameros-scs-gateway-production.up.railway.app/api/v1/me/rotate-key \
  -H 'Authorization: Bearer <your gateway JWT>'

# Response (200 OK)
{
  "api_key": "dros_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "rotated": true,
  "note": "Save this key now. The previous key is no longer valid..."
}
Built in

Audit trail by default

Every rotation emits a governance event: who, when, what surface (self-service vs auto-rotation policy). Append-only, queryable from the audit log.

Available now

Self-service for everyone

Any authenticated DreamerOS user can rotate their own MCP key. No support ticket. No HC intervention. Light, Pro, Elite all included.

Roadmap

Multi-surface propagation

Coming next: rotate once, DreamerOS pushes the new key to every connected client (Claude Desktop, Perplexity, Railway env, Vercel env) automatically. 24h grace window so nothing in flight drops.

Rotate your key now See the Pro API surface
One person, one account

Two emails.
One canonical you.

Most people end up with more than one email tied to AI accounts over time. DreamerOS links them. Sign in with either one - your memory, governance, tier, and connected clients resolve to the same canonical identity every time.

GET /api/v1/me/aliases 
curl https://dreameros-scs-gateway-production.up.railway.app/api/v1/me/aliases \
  -H 'Authorization: Bearer <your gateway JWT>'

# Response (200 OK)
{
  "canonical_user_id": "4942291b-...",
  "canonical_email": "you@example.com",
  "aliases": [
    {
      "alias_email": "you-old@example.com",
      "linked_at": "2026-05-19T...",
      "note": "HC alias merge"
    }
  ]
}
How it resolves

One-hop only

Each alias points to exactly one canonical identity. No chains, no loops. The resolver runs on every authenticated request, so a sign-in via either email lands the same canonical state.

What stays put

History keeps its attribution

Rows written under the alias id stay tagged with the alias. The resolver unifies at read time. No silent backfill. The audit trail bifurcates by design and unifies on lookup.

Roadmap

Self-service linking

Today merges happen via the admin endpoint. Self-service alias linking from the user surface needs a verified-email round trip; that ships in a follow-on. The read endpoint is live now.

Open Connect See key rotation

Paste once.
Never re-introduce yourself again.

One MCP URL. One API key. Every client you already have open. Your context lives in the middle now.

Open Connect See Automate See Pro

Free Light account for paste flows. Pro unlocks the API key and one-click installs.

Connect is live - one MCP URL for every AI tool Open Connect
98