1. Check the prerequisites
You need a working OpenCLAW installation, Node.js 18 or newer and a durable folder for the extracted MarketingOS package. Your model choice and billing remain configured in OpenCLAW.
OpenCLAW installation
Install MarketingOS in an existing OpenCLAW instance.
The native installer adds a MarketingOS orchestrator and eleven specialist roles to OpenCLAW. Models, sessions, memory, tools, secrets and channels remain part of your OpenCLAW instance. The install uses its own namespace and writes an installation manifest.
2. Review the plan without changing anything
Run node bin/install-openclaw.mjs --dry-run from the package root. The dry run lists the proposed MarketingOS agents and workspaces without changing OpenCLAW. Review paths, name collisions and the detected OpenCLAW home folder.
3. Install the agent pack
node bin/install-openclaw.mjs registers twelve namespaced agents: the marketingos orchestrator and eleven specialists. Their workspaces live below ~/.openclaw/workspace-marketingos/. The installer writes a backup before changing agent configuration and an installation manifest afterwards.
4. Verify the install and a real agent turn
Run node bin/check-openclaw-native-install.mjs to inspect files and registrations. node bin/run-openclaw-native-e2e.mjs starts a real turn of the marketingos agent. node bin/run-openclaw-specialist-source-e2e.mjs then checks the continuous source assignment to marketingos-tech-seo.
5. Enter the business context
A useful first assignment starts with the domain, market, offer, audience, brand rules, business goal, KPI and accountable owner. Only then should the orchestrator inspect a source or delegate work to a specialist.
6. Review the proven source path
The current specialist run passed WorkspaceContext revision 2 with its hash, read the live website and connected Action, Receipt, Evidence and specialist synthesis. All 37 checks passed and externalWrites remained 0. Every additional source must carry its property, domain, period and freshness in the same way.
7. Report runtime state separately
node bin/runtime-context-client.mjs check-in --input <runtime-presence.json> sends a bounded technical state to the Local Agent. Browser sessions are blocked from this route, externalWrites must be 0 and a report becomes stale after five minutes without a replacement.
8. Approve live actions separately
CMS, Git, ticket, Google, Bing, outreach and budget changes are blocked by default. A write needs specific approval and, depending on its target, a backup, restore, rollback and post-change verification path.
9. Use the manifest for removal
The intended command is node bin/install-openclaw.mjs --uninstall. The verified ownership guard removes only MarketingOS marked workspaces inside the dedicated namespace. Foreign agents, the main workspace and unowned files remain untouched.
Continue
Review the proven boundaries before installation
The Proof Ledger records the real OpenCLAW test and the gates that remain open.