Shadow LogoShadowOwnBuddy
Launch
English

Cloud Plugins

Cloud plugins add capabilities to a template. A plugin can contribute credentials, skills, scripts, CLI tools, MCP metadata, runtime assets, verification checks, and deployment configuration.

Enable plugins in a template with use:

{
  "use": [
    { "plugin": "model-provider" },
    { "plugin": "shadowob" },
    {
      "plugin": "agent-pack",
      "options": {
        "packs": [
          {
            "url": "https://github.com/example/playbook",
            "ref": "main",
            "autoImport": ["standard", "codex", "mcp", "scripts"]
          }
        ]
      }
    }
  ]
}

Core Plugins

PluginWhat it doesCommon configuration
model-providerBuilds OpenClaw model configuration from the official provider, saved provider profiles, or user-owned OpenAI-compatible keys.Official provider selection or OPENAI_COMPATIBLE_API_KEY, OPENAI_COMPATIBLE_BASE_URL, OPENAI_COMPATIBLE_MODEL_ID
shadowobCreates or attaches Shadow servers, channels, Buddies, bindings, routes, and runtime tokens.servers, channels, buddies, bindings; pod-facing SHADOW_SERVER_URL and provisioning token are injected by the platform.
agent-packMounts skills, slash commands, scripts, setup scripts, MCP fragments, instructions, and sub-agent definitions from Git.packs[].url, packs[].ref, packs[].autoImport, optional GITHUB_TOKEN

Official Connector Catalog

GroupPluginsTypical keys
Browser and test automationagent-browser, browserbase, playwrightAGENT_BROWSER_PROVIDER, BROWSERBASE_API_KEY, BROWSERBASE_PROJECT_ID
Code and product workgithub, gitagent, gitee, cnb, linear, atlassian, tapd, figmaGitHub/Gitee tokens, Linear token, Atlassian site/email/token, TAPD credentials, Figma token
Documents and workspacegoogle-workspace, notion, lark, tencent-docs, wps, yuque, airtableWorkspace OAuth JSON, Notion token, Lark app credentials, document platform tokens
Search, marketing, and analyticsseo-suite, google-analytics, google-ads, meta-ads, oceanengine, tencent-ads, klaviyo, posthog, firecrawlSearch Console site/credentials, ad platform tokens, PostHog keys, Firecrawl key
Cloud and deploymentcloudflare, vercel, firebase, supabase, sentry, huggingfacePlatform tokens, project IDs, org IDs, auth tokens
Commerce and paymentstripe, paypal, alipay, wechat-pay, shopify, wordpress-woocommerceProvider secret keys, merchant IDs, private keys, store domains
Maps, location, and China platformsamap, baidu-maps, tencent-maps, baidu-appbuilder, baidu-netdisk, baidu-smartprogram, douyin-miniprogram, wechat-miniprogram-skyline, huawei-xiaoyi, coze, taobao-aipaas, dingtalkProvider API keys, app IDs, app secrets, access tokens
Media and creationcanva, webflow, wonda, inference-sh, inference-ai-image-generation, flyaiAccess tokens, brand/template IDs, inference keys

Every plugin README under apps/cloud/src/plugins/<plugin>/README.md is the source of truth for exact fields.

How Configuration Works

  1. The template declares which plugins it needs.
  2. The deploy page shows required keys and provider choices.
  3. Users choose the official provider or their own provider profile.
  4. Sensitive values are stored as encrypted provider profiles or secret references.
  5. The runtime receives only the scoped configuration it needs.

Security Rules

  • Do not write raw API keys into template.json.
  • Mark sensitive fields as sensitive in plugin manifests.
  • Prefer OAuth or provider profiles when a user owns the integration.
  • Keep official upstream keys on Shadow servers; never inject them into user deployments.
  • Add verification checks for required CLI tools and mounted skill files.

Development Checklist

When adding a plugin:

  1. Add one plugin per platform or service.
  2. Document every key in the plugin README.
  3. Register MCP metadata only when the upstream MCP endpoint or package is stable.
  4. Add verification checks where possible.
  5. Update the plugin index and tests.

Run:

pnpm --filter @shadowob/cloud typecheck
pnpm --filter @shadowob/cloud exec vitest run __tests__/plugins/plugins.test.ts __tests__/infra/runtime-package.test.ts scripts/generate-schema.test.ts
ON THIS PAGE