OpenClaw Allbase Plugin

Connect OpenClaw agents to Allbase profiles with OAuth (recommended) and env/api-key fallback.

What it supports

• Map each OpenClaw agent to a different Allbase profile
• OAuth-first auth (access token or refresh-token flow)
• Env/api-key fallback for server-side automation
• Tools exposed in agent runtime:
  • allbase with actions:
    • status
    • save_memory
    • save_knowledge
    • search_memories
    • upload_document
    • search_documents

Install (npm)

openclaw plugins install @allbaseai/openclaw-allbase

Install (local path)

cd /home/jason/Documents/botscripts/skills/openclaw-allbase-plugin
npm install
openclaw plugins install -l /home/jason/Documents/botscripts/skills/openclaw-allbase-plugin

Then restart gateway.

Config path

Use plugins.entries.openclaw-allbase.config.

OAuth config (recommended)

{
  baseUrl: "https://allbase.ai",
  defaultProfile: "team",
  profiles: {
    team: {
      // Option A: direct access token
      oauthAccessToken: "eyJ...",

      // Option B: refresh flow
      // oauthRefreshToken: "...",
      // oauthClientId: "oac-...",
      // oauthTokenEndpoint: "https://allbase.ai/oauth/token"
    }
  },
  mapByOpenclawAgent: {
    "alan-allbase": "team"
  }
}

With OAuth, users can authorize/select their Allbase agent upstream and avoid static env wiring.

Env/API-key fallback (secondary)

If OAuth is not configured, the plugin can use profile credentials or env vars:

• ALLBASE_WORKSPACE_ID
• ALLBASE_AGENT_ID
• ALLBASE_AGENT_API_KEY (or ALLBASE_API_KEY)
• optional: ALLBASE_BASE_URL, ALLBASE_TOKEN_PATH

Profile-based api-key config still works:

{
  baseUrl: "https://allbase.ai",
  tokenPath: "/token",
  defaultProfile: "team",
  profiles: {
    team: {
      workspaceId: "ws-TEAM",
      agentId: "team-agent",
      apiKey: "abk_..."
    }
  }
}

Usage examples

• Check mapping/health:
  • tool call: allbase with action: "status"
• Save memory:
  • action: "save_memory", content, optional category, tags
• Search memory:
  • action: "search_memories", query

Optional profile parameter overrides automatic mapping for one call.

Notes

• Plugin id is openclaw-allbase (use this id in plugins.entries.*).
• Keep tokens/API keys private.
• upload_document requires local file path available to the gateway host.

Interactive OAuth CLI flow (new)

You can now run a browser-based OAuth flow directly from OpenClaw commands:

1. Start flow (prints a URL):

/allbase-auth-start <profile>

2. Open URL on any device, approve, copy code.

3. Complete flow (stores tokens in ~/.openclaw/openclaw.json):

/allbase-auth-complete <CODE> <profile>

4. Check pending states:

/allbase-auth-status

After completion, restart gateway if needed:

openclaw gateway restart