Skip to main content

​
Questions This Page Answers

  • What is the fastest way to connect OpenClaw to OrgX reliably?
  • When should I use browser pairing vs manual API key fallback?
  • How do I verify the plugin is actually healthy after pairing?
  • What unique capabilities does the OpenClaw plugin add vs hosted MCP alone?

​
60-Second Setup

1

Install the plugin

bash openclaw plugins install @useorgx/openclaw-plugin
2

Open the dashboard

Visit http://127.0.0.1:18789/orgx/live from your OpenClaw runtime.
3

Start pairing

Click Connect OrgX in the onboarding panel.
4

Confirm on web

Sign in at useorgx.com and approve the OpenClaw connection.
5

Return to OpenClaw

The plugin stores a dedicated credential and runs first sync automatically.
OpenClaw OrgX dashboard onboarding panel

​
How Pairing Works

  1. OpenClaw requests a short-lived pairing session from OrgX.
  2. OrgX opens a secure browser confirmation page tied to that session.
  3. After confirmation, OrgX provisions a plugin-scoped key for that installation.
  4. OpenClaw receives the key, stores it locally with restricted file permissions, then acknowledges receipt.
Pairing sessions expire automatically after 10 minutes for security.

​
Manual Key Fallback

If browser pairing is blocked, use Use API key instead in onboarding.

​
Step-by-step (With Screenshots)

  1. Open OrgX settings and go to API keys:
    • https://www.useorgx.com/settings#security
  2. Generate a new API key (keep it private).
OrgX settings security page (API keys)
  1. In OpenClaw onboarding, choose Use API key instead.
  2. Paste the oxk_... key and submit.
OpenClaw manual API key entry
  1. On success, onboarding should show Connected and first sync should start automatically.
Manual key fallback is for auth recovery, not for forcing a GitHub or Linear dependency. OrgX can still orchestrate through direct provider APIs with your own supported model credentials when hosted Claude pairing is not the active path.

​
First-Run Validation Checklist

Onboarding status changes to Connected
The dashboard loads live sessions/activity without restart
orgx_status returns OrgX workspace data from the plugin tools
First sync completes within your first minute on healthy network

​
Troubleshooting Matrix

​
Rotate, Revoke, Reconnect

  1. Revoke plugin credentials from OrgX API key settings when rotating access.
  2. In OpenClaw onboarding, click disconnect (or clear and reconnect).
  3. Run browser pairing again to mint a fresh installation-scoped credential.

​
Security Notes

  • The plugin stores credentials in ~/.config/useorgx/openclaw-plugin/auth.json.
  • Directory and file permissions are restricted to local user access.
  • Browser pairing avoids copy/paste secret handling on the primary path.

​
What the Plugin Enables

The OpenClaw plugin gives you more than onboarding: See the full code-generated tool matrix in OpenClaw Plugin MCP Tools.

​
Local MCP Bridge Endpoints

The plugin can auto-register this local bridge in Claude/Codex/Cursor config files under the name orgx-openclaw.