DreamerOS Agent Plugin
The official DreamerOS plugin in the Agent Plugins v1.0
open format. Each compatible client follows its own native install process.
Cursor uses the setup in install/cursor/README.md.
The installed client connects to DreamerOS's intent-verified gateway:
- Cross-session memory - recall and remember across every AI surface you use, in one private vault you own and can export or delete.
- Verified answers - DreamerOS checks high-stakes claims before you act.
- Multi-engine routing - DreamerOS sends hard questions to the best-fit engine or at least two independent engines. It shows disagreements.
What is inside
dreameros/
plugin.json identity + spec version
mcp.json DreamerOS MCP server (Streamable HTTP)
skills/
dreameros-boot/ vendor-neutral boot canon
dreameros-life-of-intent/ one automatic DreamWeaver request path
dreameros-continuity/ compatibility mode for continuity
dreameros-verified-answers/ compatibility mode for verification
dreameros-verified-routing/ compatibility mode for model routing
Shared vendor boot pack
bootpack/SOURCE-dreameros-boot-canon.md is the single Git-backed source for
installed boot files. The live MCP session package supplies current runtime
context. bootpack/build-boot-pack.ps1 builds the native format each vendor
reads:
- Claude
CLAUDE.mdblock and discoverable skill - Codex
AGENTS.mdblock and discoverable skill - Cursor global
alwaysApplyrule - stable fail-closed project pointer blocks for Claude, Codex, and Cursor repositories
- credential-free project OAuth on-ramp templates for Claude, Cursor, and Codex; these register an endpoint only and require client OAuth approval before CONNECTED
- Claude users can set
MAX_MCP_OUTPUT_TOKENS=30000as a non-secret user or project setting when full package output is needed. This is not a connection proof and no Cursor output limit is configured here. - Codex is a client surface for the DreamerOS
chatgptpackage engine. Its generated global adapter passesengine: "chatgpt"todreameros_session_package;codexis not a live package-engine value. - thin project coordination, handoff, and Claude SessionStart adapters that preserve tracked paths without duplicating canon or hardcoding an MCP id
- Agent Plugin skill
- plain-text bootstrap for any LLM
- JSON manifest for automated clients
Cursor also has a native full-surface layer at .cursor-plugin/plugin.json.
The boot builder writes a generated byte-identical mirror into the plugin rule
directory so the plugin does not depend on separate user-level rule discovery.
The native component packages both the shared boot canon and its runtime
adapter from one path. The plugin also reuses the portable skill and
credential-free MCP definition, then adds Cursor subagents, commands, and
lifecycle hooks under cursor/.
The four native roles use collision-proof dreameros-platform-* names and
explicitly inherit the parent Cursor model. This keeps Claude-compatible
project agents, model pins, and legacy tool ids from replacing the native
plugin roles inside Cursor.
Install the boot pack first. Then run install/cursor/install.ps1 to install
and verify the Cursor plugin. The installer refuses target collisions by
default. An explicit -Update first backs up the existing plugin target, then
replaces that one target from the exact source inventory and rolls back on
failure. It never touches separate user hooks or project configuration, and
never copies a bearer token from another client.
The same installer provides confirmation-gated, recoverable -Uninstall and
-RestoreBackup operations. Successful project-pointer migrations carry a
durable manifest. Before commit, restore-project-rules.ps1 reads that
manifest.
The Cursor target excludes the portable root plugin.json and mcp.json so
Cursor cannot choose the narrower Agent Plugin manifest over its native one.
Run bootpack/build-boot-pack.ps1 -Install to build, install, and verify
the machine-wide Claude, Codex, Cursor, and shared-agent destinations. The
live DreamerOS MCP session package remains the runtime context source.
Use -VerifyInstalled for a read-only exact block and file check across those
installed destinations.
Run install/cursor/sync-project-rules.ps1 without switches to inventory tracked
Cursor project rules. GLOBAL_ONLY is a CLOUD_BOOT_GAP. A project pointer
is required for universal cloud parity. POINTER_ALIGNED FILE-CLEAN is the
portable default. Each repository's instruction
and ownership review must approve migration separately because tracked files
can have active owners and companion registries.
Run install/cursor/audit-project-boot-surfaces.ps1 for the broader Claude,
Codex, and Cursor project-surface inventory. It is read-only and treats duplicated
full canon blocks as a conflict even when their version is current. It also
checks named Cursor adapters and registered project Claude SessionStart hooks,
so a stale hydration order cannot hide behind aligned pointer counts.
Generated thin enforcement adapters preserve the existing Cursor rule paths
without carrying full canon text. The project coordination, verified handoff,
and Claude SessionStart adapters replace stale tool sequences. The
historical-generator pointer keeps old script paths fail-closed without
deleting them.
Run install/cursor/plan-project-migration.ps1 to convert that census into a
reconciled read-only plan per physical checkout. JSON is the default; pass
-Format Markdown for a human review packet. The planner reports local
tracking-ref and worktree state but never fetches. It names generated source
hashes, registry constraints, exact targets, held-back actions, authorization
gates, and fresh-fetch requirements in both formats without
printing, copying, or persisting MCP Authorization values. The underlying
audit inspects header structure and emits one trusted PASS or FINDINGS marker.
Every requested estate root must exist. Reparse-point children are not
traversed; the plan exposes only a digest and a blocked human review action.
The planner cannot apply or publish a change.
Run install/cursor/render-project-migration-diffs.ps1 to turn an independently
sealed JSON plan into strict, in-memory review diffs for the five
deterministic project transformations. It revalidates source hashes, current
Git state, target classification, path containment, and generated-region
boundaries. Credential-bearing MCP configuration and manual-boundary actions
remain metadata-only. The renderer never fetches or writes. The existing
authorization and current-main gates prevent every preview from becoming
apply-ready. See the
Cursor install guide for the exact command and
dual-PowerShell verification suite.
Inside Cursor, use /dreameros-parity-check for the measured connection table.
Use /dreameros-claude-review to build and preflight a clean-context Claude Code
review packet. The command requires separate confirmation before it sends the
packet.
Install
Install mechanics differ per client (each client owns distribution and permissions under the Agent Plugins standard). In all cases the plugin directory is this repository's root.
Choose the client guide:
Authentication
The MCP server at https://mcp.dreameros.app/mcp authenticates each user.
- Cursor native plugin: complete Cursor's OAuth prompt. Do not add an
Authorizationheader. Do not copy a token from Claude, Codex, an environment variable, or another client. - Clients that explicitly require a bearer: use that client's protected credential mechanism and follow the signed-in instructions at app.dreameros.app/connect.
Per the Agent Plugins specification, this plugin never embeds credentials. No key ships in any file here, and you should never commit yours.
The DreamerOS server gates capabilities by subscription tier. The same plugin installs on every tier, including free. Installation does not prove that a capability ran. The complete Life of an Intent path is a DreamWeaver Solo, DreamWeaver Duo, and higher-plan capability; the Gateway checks that entitlement on each call and the returned receipt shows when DreamerOS was actually used.
Gateway Lockstep
gates/gateway_lockstep.py validates a bounded evidence record for the
portable Life of an Intent entry. It emits five distinct states:
CONFIGURED, INVOKED, UNSUPPORTED, OFFLINE, and TERMINAL. A terminal result needs
a signed Gateway receipt that binds the actual MCP input and signed intent
anchor. States are SUCCESS, NO-OP, BLOCKED, STALLED, and EXHAUSTED.
The verifier centralizes the intent-envelope schema, receipt-event schema, terminal-state enum, client capability matrix, managed-artifact manifest, and hook-event adapter table. SDK typed contracts and Gateway enforcement are held outside this portable plugin slice.
Cursor checks this record after a supported DreamerOS MCP result. Claude's
Stop event reports UNSUPPORTED when it lacks the record. These hooks do not
claim universal enforcement.
Versioning
Semantic versioning. The plugin tracks Agent Plugins spec 1.0.0.
License
Proprietary. The plugin manifest and skill texts may be redistributed unmodified for the purpose of installing the plugin.