@useorgx/openclaw-plugin 0.4.5 → 0.4.6

package/README.md

@@ -10,7 +10,7 @@ OrgX plugin for [OpenClaw](https://openclaw.ai) — connect your AI agents to Or
 4. Sign in at [useorgx.com](https://useorgx.com) and approve the connection.
 5. Return to OpenClaw. The plugin stores a dedicated credential and runs first sync automatically (no key copy/paste).
 
-If Claude/Cursor/Codex MCP configs are detected on this machine, the pairing flow also installs a local MCP bridge entry (no OAuth) pointing at `http://127.0.0.1:18789/orgx/mcp`. To opt out, set `ORGX_DISABLE_MCP_CLIENT_AUTOCONFIG=1`.
+If Claude/Cursor/Codex MCP configs are detected on this machine, the pairing flow also installs a local MCP bridge entry (no OAuth) pointing at `http://127.0.0.1:18789/orgx/mcp`. To avoid overwriting your hosted `orgx` server entry, the local bridge is installed under the name `orgx-openclaw`. To opt out entirely, set `ORGX_DISABLE_MCP_CLIENT_AUTOCONFIG=1`.
 
 Manual API key entry is still available as a permanent fallback from the onboarding panel.
 
@@ -29,8 +29,8 @@ This plugin exposes the same `orgx_*` tools over a local MCP HTTP endpoint serve
 
 On successful browser pairing, the plugin will attempt to patch:
 
-- `~/.claude/mcp.json` (rewire `mcpServers.orgx.url` to the local bridge)
-- `~/.codex/config.toml` (rewire `[mcp_servers.orgx].url` to the local bridge)
+- `~/.claude/mcp.json` (adds `mcpServers["orgx-openclaw"]` pointing to the local bridge)
+- `~/.codex/config.toml` (add/update `[mcp_servers."orgx-openclaw"].url` to the local bridge)
 - `~/.cursor/mcp.json` (adds `mcpServers["orgx-openclaw"]` pointing to the local bridge)
 
 Each file is backed up first (only when a change is needed) with a `*.bak.<timestamp>-<rand>` suffix.
@@ -79,6 +79,8 @@ Environment overrides:
 The plugin registers these tools for your agents:
 
 - **`orgx_status`** — Get current org status (initiatives, agents, tasks, decisions)
+- **`orgx_status_json`** — Get current org status as JSON (for MCP Apps / automation)
+- **`orgx_live_app`** — Open the OrgX Live MCP App (interactive widget)
 - **`orgx_sync`** — Bidirectional memory sync with OrgX
 - **`orgx_spawn_check`** — Pre-spawn quality gate + model routing
 - **`orgx_quality_score`** — Record quality scores for completed work
@@ -98,6 +100,14 @@ Shows:
 - Activity stream
 - Outbox replay visibility for buffered offline events
 
+### 🔁 Auto-Continue (Scaffold → Agent Execution)
+
+If you scaffold an initiative from chat (for example, "plan X" and then create/scaffold), OrgX can automatically start executing the first workstream via the stream auto-continue pipeline.
+
+Troubleshooting:
+- If agents do not start automatically, say: `start agents` to re-trigger dispatch.
+- Open the live link (Mission Control) to see stream status (`ready`, `active`, `blocked`) and any upgrade/approval decisions.
+
 ### 🎯 Model Routing
 
 OrgX automatically routes tasks to the appropriate model tier:
@@ -205,6 +215,17 @@ Notes:
 Manual dispatch:
 - Use `docs/marketing/manual-agent-dispatch-golden-prompt.md` when manually launching a marketing agent for a specific task (non-batched dispatch).
 
+## SEO Automation (Keywords Everywhere + DataForSEO)
+
+This repo also includes a repo-local SEO pipeline runner (scripts only; not shipped in the plugin package) under `scripts/seo/`.
+
+- Apply an OrgX initiative plan for SEO automation: `npm run seo:plan`
+- Run the pipeline:
+  - Dry run (no API calls): `npm run seo:run -- --config=docs/seo/seo.config.example.json --mode=all --dry-run=true`
+  - Live run: `npm run seo:run -- --config=docs/seo/seo.config.example.json --mode=all`
+
+Details: `scripts/seo/README.md`
+
 ## API Endpoints
 
 When the plugin is loaded, these HTTP endpoints are available: