![\"OrgX](\"./orgx-live-mission-control-0.7.15-check.png\")
\n ![\"OrgX](\"./orgx-live-activity-0.7.15-check.png\")
\n\n \n \n
\n Mission Control for shared execution state. Activity for the live history your agents can build on.\n
\n\n---\n\n## What changes after you install this\n\n| Before OrgX | After OrgX |\n|---|---|\n| Each agent starts every session with amnesia | Agents query decisions, context, and history from prior sessions |\n| You manually stitch context between agents | Agents read and write to a shared entity graph: initiatives, milestones, decisions, tasks |\n| \"What was I working on?\" requires you to remember | The morning brief tells your agents, and you, exactly where things stand |\n| Running 5+ agents means 5+ unsyncable contexts | One coordination layer across all agents and sessions |\n| Heartbeat files and markdown workarounds | Typed organizational structure with semantic relationships |\n\n---\n\n## Install\n\n```bash\n# From your OpenClaw workspace\nopenclaw plugins install clawhub:@useorgx/openclaw-plugin\n\n# npm also works if you prefer the package directly\nopenclaw plugins install @useorgx/openclaw-plugin\n```\n\nThen open the OrgX dashboard in your OpenClaw gateway, click **Connect OrgX**, and approve the browser pairing flow. First sync runs automatically after connect.\n\nAgent-suite provisioning is **opt-in**. MCP client config edits are also **opt-in**. You can review and apply the managed suite later from **Settings -> Agent Suite** in the dashboard, and you can explicitly enable MCP client auto-configuration in plugin config if you want that behavior.\n\n**Manual key setup** is still available if you prefer it. Use the onboarding panel and choose **Manual API key**.\n\n---\n\n## What you get\n\n### Persistent Organizational Memory\nYour agents can query what happened in past sessions. Decisions persist. Context accumulates. An agent spawned today can ask, \"What did we decide about the API design last week?\" and get an answer.\n\n### Optional Agent Suite Provisioning\nOrgX can create managed agent workspaces, install coordinated configurations, and preserve your local overrides when you explicitly apply the suite. Your existing setup does not get clobbered. It gets enhanced.\n\n### Shared Entity Graph\nInitiatives, workstreams, milestones, decisions, and tasks: all structured, all queryable, all shared across your agents. This is not a flat to-do list. It is a model of how your work actually connects.\n\n### Live Dashboard\nSee what your agents are doing, what decisions are pending, and what is blocked. One view across your entire agent operation.\n\n### Local MCP Bridge\nOrgX connects through MCP, so the coordination layer can live wherever your agents work. The plugin exposes a local bridge at `/orgx/mcp`. If you want Claude, Cursor, or Codex wired to that bridge automatically, you can explicitly enable that behavior in plugin config.\n\n---\n\n## How it works with your existing setup\n\nOrgX does not replace your OpenClaw agents or change how they work. It adds a shared memory and coordination layer underneath them.\n\n```text\n┌─────────────────────────────────────────┐\n│ Your OpenClaw Agents │\n│ (coding, research, marketing, ops...) │\n└──────────────┬──────────────────────────┘\n │ read/write\n┌──────────────▼──────────────────────────┐\n│ OrgX Entity Graph │\n│ decisions · initiatives · milestones │\n│ tasks · memory · agent trust levels │\n└──────────────┬──────────────────────────┘\n │ persists across\n┌──────────────▼──────────────────────────┐\n│ Every session. Every agent. │\n│ Every tool. Forever. │\n└─────────────────────────────────────────┘\n```\n\nYour agents keep their skills, configurations, and autonomy. They just gain the ability to remember, coordinate, and build on each other's work.\n\n---\n\n## vs. heartbeat files, Paperclip, and manual context\n\n| Approach | Memory | Structure | Cross-agent coordination |\n|---|---|---|---|\n| Heartbeat `.md` files | File-based, fragile | Flat task lists | Manual |\n| Paperclip | File-based + schedules | Org chart + tickets | Delegation via hierarchy |\n| **OrgX** | **Typed entity graph** | **Semantic: initiatives -> workstreams -> milestones -> decisions -> tasks** | **Shared memory + trust architecture + autonomous coordination** |\n\nHeartbeat files are a workaround. Paperclip organizes the workaround. OrgX removes the need for the workaround entirely.\n\n---\n\n## Quick start: scaffold your first initiative\n\nAfter connecting, try this in any OpenClaw agent session:\n\n```text\nScaffold an initiative called \"MVP Launch\" with workstreams for engineering, marketing, and operations.\n```\n\nOrgX creates the structure, and every agent in your setup can query and contribute to it. When your engineering agent finishes a task, your marketing agent can operate against the same shared context.\n\n---\n\n## Need help setting this up for your specific workflow?\n\nOrgX Amplify is our guided setup service for founders and teams running serious agent operations. We configure OrgX for your exact stack, migrate your existing context, and get you operational in a week.\n\n-> [Book an Amplify call](https://useorgx.com/amplify)\n\n---\n\n## Security and transparency\n\nOrgX is designed for developers who want to know what a plugin changes before they install it.\n\n### Local files the plugin may write\n\nThe plugin stores its own auth and local state under:\n\n- `~/.config/useorgx/openclaw-plugin/auth.json`\n- `~/.config/useorgx/openclaw-plugin/installation.json`\n- `~/.config/useorgx/openclaw-plugin/snapshot.json`\n- `~/.openclaw/orgx-outbox/`\n- `~/.config/useorgx/wizard/hooks/events.jsonl` for compact, redacted Work\n Graph hook events when runtime hooks are installed\n\nIf you explicitly enable MCP client auto-configuration, the plugin may update supported client config files and create timestamped backups before writing:\n\n- `~/.claude/mcp.json`\n- `~/.codex/config.toml`\n- `~/.cursor/mcp.json`\n\nIf you choose to apply the managed OrgX agent suite, the plugin may also create or update managed OpenClaw workspace files. Conflict detection is used to avoid silently overwriting out-of-band edits.\n\n### Credentials\n\nBrowser pairing and manual API-key setup both store credentials locally on your machine. Auth files are written with restricted filesystem permissions. The current credential store is file-based rather than OS-keychain-backed. The README and plugin UI intentionally avoid printing full key values.\n\n### Network calls\n\nThe plugin talks to OrgX services for pairing, sync, MCP, and dashboard-backed workflows:\n\n- `https://www.useorgx.com`\n- `https://mcp.useorgx.com/mcp`\n\n### Telemetry\n\nProduct telemetry is **off by default**. PostHog events are only sent if you explicitly enable telemetry with environment variables such as `ORGX_TELEMETRY_ENABLED`. Telemetry can also be disabled via `ORGX_TELEMETRY_DISABLED`, `OPENCLAW_TELEMETRY_DISABLED`, or `POSTHOG_DISABLED`.\n\nPassive AI-client hooks write compact, summary-only records to\n`~/.config/useorgx/wizard/hooks/events.jsonl`. The packaged\n`orgx-openclaw-reconcile-hooks` command can turn that outbox into a Work Graph\nhydration report with a stable `work_graph_fingerprint` and\n`signup_hydration.hydration_key`:\n\n```bash\norgx-openclaw-reconcile-hooks \\\n --outbox ~/.config/useorgx/wizard/hooks/events.jsonl \\\n --output /tmp/orgx-work-graph-report.json\n```\n\nPublishing is explicit:\n\n```bash\nORGX_API_KEY=oxk_... orgx-openclaw-reconcile-hooks --post\n```\n\n### Background processes and local execution\n\nThe plugin runs a background sync service as part of normal operation. It can also start a local gateway watchdog process to keep the OpenClaw gateway reachable; if you do not want that behavior, set `ORGX_DISABLE_GATEWAY_WATCHDOG=1`.\n\nAgent turns, terminal opens, and other `openclaw` CLI child-process actions are only triggered by explicit runtime or dashboard actions. They are not part of the passive install path.\n\n### What the plugin does not do by default\n\n- It does not auto-install the managed OrgX agent suite unless you enable that behavior.\n- It does not patch Claude, Cursor, or Codex MCP config files unless you enable that behavior.\n- It does not send product telemetry unless you explicitly enable it.\n- It does not send raw transcripts through runtime hooks. Hook scripts write\n redacted event summaries locally so the OrgX wizard can reconcile Work Graph\n fingerprints, missed OrgX writeback, and safe public readouts later.\n\n---\n\n## Links\n\n- [OrgX Platform](https://useorgx.com)\n- [OrgX MCP Server](https://mcp.useorgx.com/mcp)\n- [Documentation](https://docs.useorgx.com)\n- [Discord](https://discord.gg/orgx)\n- [GitHub](https://github.com/useorgx)\n\n**Built by [Hope](https://twitter.com/hopeatogun)** - solo founder, bioengineering background, self-taught engineer. Building the coordination layer for the agent era since a 2016 ML thesis on directed network evolution.\n\n---\n\n## Technical reference\n\n## What's New (0.7.x)\n\n- Mission Control lifecycle UX now cleanly separates `Next Up` queue intent from `In Progress` runtime state, with stronger task/workstream hierarchy rendering and queue controls (`Play`, `Pin`, `Reorder`, `Move`, `Bulk`, `Clear`).\n- Autopilot and manual `Play` now share the same lifecycle contract and spawn-guard behavior, including deterministic blocked/needs-decision handling surfaced in triage and activity.\n- Workspace-scoped reads/writes were hardened across Mission Control graph, Next Up, slices, and snapshot surfaces to avoid cross-workspace leakage.\n- Activity and session detail surfaces were upgraded with clearer run outcome metadata, safer error messaging, and improved context labels.\n- Dashboard build output was stabilized by fixing chunk-splitting behavior and eliminating circular-chunk warnings in production builds.\n\n## Architecture Overview\n\n```\n ┌──────────────────────────────┐\n │ OrgX Cloud API │\n │ (useorgx.com) │\n │ │\n │ Snapshots, Decisions, │\n │ Activity, Entity CRUD, │\n │ Quality Gates, Model Routing │\n └──────────────┬───────────────┘\n │\n Authenticated OrgX session\n │\n┌───────────────────────────────────────┼───────────────────────────────────────┐\n│ OpenClaw Gateway (localhost:18789) │ │\n│ ┌────────────────────────────────────┴──────────────────────────────────┐ │\n│ │ OrgX Plugin (this repo) │ │\n│ │ │ │\n│ │ ┌──────────────┐ ┌──────────────┐ ┌─────────────────────────┐ │ │\n│ │ │ OrgXClient │ │ Outbox │ │ State Stores │ │ │\n│ │ │ │ │ │ │ │ │ │\n│ │ │ API calls │ │ Offline │ │ auth-store (creds) │ │ │\n│ │ │ to cloud │◄──│ event queue │ │ snapshot-store (cache) │ │ │\n│ │ │ │ │ + replay │ │ activity-store (feed) │ │ │\n│ │ └──────┬───────┘ └──────────────┘ │ agent-run-store │ │ │\n│ │ │ │ next-up-queue-store │ │ │\n│ │ │ └─────────────────────────┘ │ │\n│ │ │ │ │\n│ │ ┌──────┴──────────────────────────────────────────────────────────┐ │ │\n│ │ │ HTTP Handler │ │ │\n│ │ │ │ │ │\n│ │ │ /orgx/live → Dashboard SPA (Vite-built React app) │ │ │\n│ │ │ /orgx/api/* → Modular REST routes │ │ │\n│ │ │ /orgx/mcp → MCP bridge (tools/list, tools/call) │ │ │\n│ │ │ /orgx/api/live/* → Polling + SSE for real-time data │ │ │\n│ │ └────────────────────────────────┬────────────────────────────────┘ │ │\n│ │ │ │ │\n│ │ ┌────────────────────────────────┼─────────────────────────────┐ │ │\n│ │ │ Background Services │ │ │ │\n│ │ │ │ │ │ │\n│ │ │ Sync service (every 5min) │ Gateway watchdog │ │ │\n│ │ │ Agent suite provisioning │ MCP client auto-config │ │ │\n│ │ │ Auto-continue pipeline │ Worker supervisor │ │ │\n│ │ └────────────────────────────────┘─────────────────────────────┘ │ │\n│ └──────────────────────────────────────────────────────────────────────┘ │\n│ │ │\n│ ┌───────────────────────────────────┴──────────────────────────────────┐ │\n│ │ MCP Tools (exposed to agents) │ │\n│ │ │ │\n│ │ orgx_status orgx_spawn_check orgx_create_entity │ │\n│ │ orgx_sync orgx_quality_score orgx_update_entity │ │\n│ │ orgx_emit_activity orgx_request_decision orgx_list_entities │ │\n│ └──────────────────────────────────────────────────────────────────────┘ │\n└──────────────────────────────────────────────────────────────────────────────┘\n │\n SSE primary + polling fallback\n │\n ┌──────────────┴───────────────┐\n │ React Dashboard │\n │ /orgx/live │\n │ │\n │ Mission Control (hierarchy) │\n │ Activity Timeline │\n │ Decision Queue (approve/ │\n │ reject with notes) │\n │ Session Inspector │\n │ Agent Provisioning │\n └──────────────────────────────┘\n```\n\n### Data Flow\n\n```\nAgent calls MCP tool (e.g. orgx_emit_activity)\n → Plugin validates + forwards to OrgX Cloud\n → Cloud persists, returns updated state\n → Plugin caches snapshot locally\n → Dashboard subscribes to /orgx/api/live/stream (SSE)\n → Falls back to /orgx/api/live/snapshot-v2 polling when needed\n → useLiveData hook merges + renders\n\nIf cloud is unreachable:\n → Plugin queues event in Outbox (~/.orgx/plugin/outbox/)\n → Dashboard reads from cached snapshot + outbox replay\n → On reconnect, outbox auto-replays with backoff\n```\n\n## Installation\n\n```bash\nopenclaw plugins install @useorgx/openclaw-plugin\n```\n\n## Local MCP Bridge (Claude/Codex/Cursor)\n\nThis plugin exposes the same `orgx_*` tools over a local MCP HTTP endpoint served by the OpenClaw gateway:\n\n- URL: `http://127.0.0.1:18789/orgx/mcp` (port follows your OpenClaw gateway config)\n- Why: avoids the separate cloud MCP OAuth flow and keeps your OrgX credential in the plugin's local credential store.\n\nIf you explicitly enable MCP client auto-configuration, the plugin can patch:\n\n- `~/.claude/mcp.json` (adds `mcpServers[\"orgx-openclaw\"]` pointing to the local bridge)\n- `~/.codex/config.toml` (add/update `[mcp_servers.\"orgx-openclaw\"].url` to the local bridge)\n- `~/.cursor/mcp.json` (adds `mcpServers[\"orgx-openclaw\"]` pointing to the local bridge)\n\nEach file is backed up first (only when a change is needed) with a `*.bak.