DreamerOS

Connect

Bring the right context into the tools you already use.

A connector is a link between DreamerOS and a tool you already use, such as Gmail, Notion, Slack or GitHub. Through it, DreamerOS can check an answer and carry your account memory into that tool. Each connector has its own setup and proof path.

Before an outside tool sends or changes something for you, DreamerOS compares the action with what you asked. If it cannot tell what the action does, it holds the action and says why.

Try it free. No card, ever.
A connector action checked against what you asked for before it runs
What a connector may do, and what it may never do on its own

Set it up in three steps

  1. Get your key

    Sign in and open Connect. Every signed-in plan, Light and up, can make its own account-specific connection key there.

  2. Pick your path

    Choose the setup path for your tool. The public setup guide has the client-by-client steps and shows which paths are live now.

  3. Confirm it works

    Confirm the connection with the client's own handshake, its first successful sign-in or call, before you rely on it.

In Beta 2.0, so do not rely on these for customer automation yet: automatic parity across every connected tool, Zapier outbound automation, and universal approval or action parity across connectors. Today each connector has its own setup, its own checks and its own approval behavior.

key: POST /api/v1/api-key/generate, any signed-in plan | link confirmed by the client handshake | enforcement is path-specific | unclassified write action: held | outbound Zapier, cross-connector approval and action parity: In Beta 2.0

Mail and calendar

Your inbox and calendar, read and checked.

Supported mail and calendar connectors can read your mail and schedule, draft replies, and prepare meeting changes when you ask.

How it is wired
direction: supported provider paths read your account and can prepare writes protocol: provider API over HTTPS auth: OAuth login, where the provider supports it
A message read as reference, never as an order
What a connector may do, and what it may never do on its own

Files and notes

Your notes, designs and datasets, held as memory too.

Supported file and note connectors can pull in notes, records, designs, datasets, and audio for your DreamerOS memory. What each one can read and write depends on the connector.

How it is wired
direction: supported paths read connected files and notes protocol: provider API over HTTPS, by provider auth: OAuth login or a stored key, by provider scope: path-specific reads and writes
What you keep in one tool becomes memory in the next
How account memory can reach a supported connection

Code and work

The tools you already code and ship in.

Supported code and work connectors can bring project context into DreamerOS. A deploy, merge, or ticket action has its own path and its own checks, so a listed connector does not prove the same check applies everywhere.

How it is wired
direction: supported paths read project state and may expose write actions protocol: MCP session for editors, provider API for the rest auth: client handshake or provider login
A change checked before it ships
Checked by an AI from a different maker than the one that answered

Money and everything else

Know the path and its limit before money moves.

Bring your own provider key for supported connectors, subject to that provider and your plan limits. Spending and posting safeguards depend on the connector.

How it is wired
direction: supported paths use the provider connection you authorize protocol: provider API over HTTPS, MCP session, or OAuth login, by tool auth: your own provider credential, where supported scope: path-specific spend and post controls; outbound Zapier is In Beta 2.0
A daily ceiling on spend, shown as a wall
Where DreamerOS checks plan spend before work goes out

For builders

The mechanism, one click from here: build with DreamerOS, the client setup guide, and how a connection travels, in plain words. All one click from here.

More detail

What connectors usually get wrong

Elsewhere, an assistant is often handed a key that opens everything, because that was the only key on offer. Reported failures in the trade press include a broad GitHub token that let hidden instructions inside a public issue leak private repositories, a production database deleted in nine seconds by a token meant only for domain management, and automations pulled after any issue posing as a trusted bot could trigger them. The pattern in all of them is the same: the connector was given more permission than the job needed, then it read text somebody else wrote and treated that text as an instruction.

What DreamerOS checks, in order

Each connector has its own path through DreamerOS. On a supported path, DreamerOS checks an action against what you asked for. A mismatch stops that path and tells you why. The path marks what it reads from your tool as reading material and names its source. It does not treat that material as an instruction. Paths with an audit event can record what they did and whether the check passed. If a path cannot tell whether an action writes or only reads, it treats the action as a write and holds it when the check cannot run. Each path handles reads differently.

write -> intent check -> mismatch: 403 with reason | reads wrapped as untrusted data, source tagged | check down: write blocked, read logged unchecked

All connections in the current public registry

Claude Desktop, ChatGPT, Cursor, VS Code, Windsurf, Claude Code (Web), Claude Code (Desktop), Codex (Web), Codex (Desktop / CLI), Lovable, Base44, Gemini, Grok, Hugging Face, Custom LLM endpoint, Bring Your Own AI, Railway, Porkbun, GitHub, Vercel, Notion, Supabase, Firecrawl, Resend, Cloudflare, Sentry, Slack, Gmail, Linear, Google Calendar, Zapier, Yahoo Fantasy, Sleeper Fantasy, OpenAI API Key, Anthropic API Key, Perplexity API Key, X (Twitter), Buffer, Google Drive, Airtable, Airtable (OAuth), Figma, Mermaid Chart, Lucid or ElevenLabs. A listed connection does not prove that every read, write, approval, or memory feature works the same way. Follow that client's setup and proof path. More connectors are planned. Ask for the connector you need.