@clawops/cli 1.7.9 → 2.0.1

package/spec/integrations.yaml

@@ -1,9 +1,44 @@
 # spec/integrations.yaml — OpenClaw channel integration catalog for the setup wizard.
 # Read at runtime by src/cli/commands/setup.ts — not compiled or code-generated.
 #
-# Each integration maps to a key in openclaw.json's `channels` object.
+# Each integration maps to a key in the `channels` object of OpenClaw's config.
 # infraRequired: true means a publicly reachable webhook URL must be registered
 # with the provider after the stack is deployed.
+#
+# ── Checked against OpenClaw 2026.9.2 (WO-60) ────────────────────────────────
+#
+# EVERY channel in 2.0 is an install-gated plugin. `openclaw channels list --all --json`
+# reports all 31 as `origin: "installable"`, and none is bundled — the same shape as model
+# providers (WO-43), which is why `plugin:` below carries the package to install.
+#
+# Configuring a channel without installing it produces a gateway that starts, reports
+# healthy, and never connects to the channel.
+#
+# `dmPolicy` and `groupPolicy` are REQUIRED by the schema on every channel here, and Slack
+# and WhatsApp require more. `defaults:` carries OpenClaw's own default for each of them, and
+# the wizard writes them — a JSON Schema default does not satisfy `required`, so a config
+# omitting them is REJECTED. Every channel the wizard wrote was invalid before this.
+#
+# Every credential field also accepts a SecretRef — `{source: env, provider, id}` — as well
+# as a plain string, so a token need not be inlined into the config.
+#
+# The catalog was wrong in four ways before this pass, all of which would have produced a
+# config OpenClaw rejects or ignores: the Teams key was `teams` (the schema has `msteams`),
+# Discord's token field was `botToken` (it is `token`), WhatsApp's `phoneNumberId` and
+# `accessToken` do not exist on that channel at all, and EVERY `envDefault` used an
+# `OPENCLAW_*` name that OpenClaw does not read.
+#
+# `envVar` below is the variable `openclaw channels add --use-env` actually reads, taken from
+# the binary's own error message. `useEnvSupported: false` means that flag is rejected for the
+# channel outright — measured, not assumed.
+#
+# `plugin.version` is pinned to the runtime floor, and it is not decoration. Measured on
+# 2026.9.2: `@openclaw/discord@2026.9.3` refuses to install with
+#
+#   plugin "discord" requires plugin API >=2026.9.3, but this OpenClaw runtime exposes 2026.9.2
+#
+# The same drift that forced version pins on model providers in WO-43. `latest` would break
+# the deploy the moment upstream publishes ahead of the runtime, which it already has.
 
 integrations:
   - id: discord
@@ -11,12 +46,21 @@ integrations:
     displayName: Discord
     description: Connect OpenClaw agents to a Discord server via bot
     infraRequired: false
+    plugin:
+      package: "@openclaw/discord"
+      source: npm
+      version: "2026.9.2"
+    useEnvSupported: true
+    requiredConfig: [dmPolicy, groupPolicy]
+    defaults:
+      dmPolicy: pairing
+      groupPolicy: allowlist
     fields:
-      - name: botToken
+      - name: token
         label: Bot token
         description: Bot token from the Discord Developer Portal (Bot → Token)
         sensitive: true
-        envDefault: OPENCLAW_DISCORD_TOKEN
+        envDefault: DISCORD_BOT_TOKEN
     setupUrl: https://discord.com/developers/applications
 
   - id: telegram
@@ -24,33 +68,69 @@ integrations:
     displayName: Telegram
     description: Connect OpenClaw agents to a Telegram bot
     infraRequired: false
+    # Bundled in the image: `channels add --channel telegram --use-env` succeeds with
+    # `--network none`, so there is nothing to download and no egress needed. It is listed
+    # as "installable" alongside the rest, which is why this looked unresolved at first.
+    plugin:
+      package: ""
+      source: bundled
+    useEnvSupported: true
+    requiredConfig: [dmPolicy, groupPolicy]
+    defaults:
+      dmPolicy: pairing
+      groupPolicy: allowlist
     fields:
       - name: botToken
         label: Bot token
         description: Token from @BotFather (/newbot)
         sensitive: true
-        envDefault: OPENCLAW_TELEGRAM_TOKEN
+        envDefault: TELEGRAM_BOT_TOKEN
     setupUrl: https://t.me/BotFather
 
   - id: slack
     channelKey: slack
     displayName: Slack
-    description: Connect OpenClaw agents to a Slack workspace via app
-    infraRequired: true
-    infraNote: >
-      After deployment, register the gateway webhook URL in your Slack app
-      configuration at api.slack.com (Event Subscriptions → Request URL).
+    description: Connect OpenClaw agents to a Slack workspace via app (Socket Mode)
+    # Socket Mode, not a webhook. `mode` defaults to "socket" in OpenClaw and it is what
+    # `channels add --use-env` drives: the gateway opens an OUTBOUND WebSocket to Slack, so
+    # there is no public URL to register and no inbound rule to open.
+    #
+    # This entry said infraRequired: true — the `http` mode setup — while declaring the
+    # socket credentials incompletely. It described one setup while the tooling installed
+    # the other, and the config it produced failed validation either way.
+    #
+    # `mode: http` is still available: it needs a public webhook at `webhookPath` and a
+    # signingSecret to verify inbound requests. That is a deliberate choice, not the default,
+    # and clawops does not configure it.
+    infraRequired: false
+    plugin:
+      package: "@openclaw/slack"
+      source: npm
+      version: "2026.9.2"
+    # Socket Mode is what --use-env drives, and it demands SLACK_APP_TOKEN:
+    #   "Slack Socket Mode requires SLACK_APP_TOKEN when using --use-env."
+    useEnvSupported: true
+    # Slack requires more than the two policies: the schema also demands postAs, mode,
+    # webhookPath and userTokenReadOnly.
+    requiredConfig: [dmPolicy, groupPolicy, postAs, mode, webhookPath, userTokenReadOnly]
+    defaults:
+      dmPolicy: pairing
+      groupPolicy: allowlist
+      postAs: bot
+      mode: socket
+      webhookPath: /slack/events
+      userTokenReadOnly: true
     fields:
       - name: botToken
         label: Bot OAuth token
         description: "Bot User OAuth Token (starts with xoxb-)"
         sensitive: true
-        envDefault: OPENCLAW_SLACK_TOKEN
-      - name: signingSecret
-        label: Signing secret
-        description: App signing secret from Basic Information → App Credentials
+        envDefault: SLACK_BOT_TOKEN
+      - name: appToken
+        label: App-level token
+        description: "App-level token for Socket Mode (starts with xapp-), from Basic Information → App-Level Tokens"
         sensitive: true
-        envDefault: OPENCLAW_SLACK_SIGNING_SECRET
+        envDefault: SLACK_APP_TOKEN
     setupUrl: https://api.slack.com/apps
 
   - id: whatsapp
@@ -62,27 +142,49 @@ integrations:
       After deployment, register the gateway webhook URL in the Meta Developer
       Console (WhatsApp → Configuration → Webhook). The gateway URL is printed
       at the end of setup.
-    fields:
-      - name: phoneNumberId
-        label: Phone number ID
-        description: Phone Number ID from Meta Developer Console → WhatsApp → API Setup
-        sensitive: false
-        envDefault: ""
-      - name: accessToken
-        label: Access token
-        description: Permanent system user access token from Meta Business Suite
-        sensitive: true
-        envDefault: OPENCLAW_WHATSAPP_TOKEN
+    plugin:
+      package: "@openclaw/whatsapp"
+      source: npm
+      version: "2026.9.2"
+    # `openclaw channels add --use-env` answers: OpenClaw does not recognize option
+    # "--use-env". There is no non-interactive path for this channel.
+    useEnvSupported: false
+    requiredConfig: [dmPolicy, groupPolicy, mediaMaxMb]
+    defaults:
+      dmPolicy: pairing
+      groupPolicy: allowlist
+      mediaMaxMb: 50
+    # WhatsApp has no top-level credential fields in 2.0 — credentials live under
+    # `accounts.<name>`, with `defaultAccount` selecting one. The wizard cannot collect a
+    # flat token for it, so it is marked unsupported rather than collecting fields that go
+    # nowhere. `phoneNumberId` and `accessToken`, which this entry used to declare, are not
+    # properties of the whatsapp channel at all.
+    wizardSupported: false
+    unsupportedNote: >
+      WhatsApp uses per-account credentials (`channels.whatsapp.accounts.<name>`) rather
+      than a single token. Configure it with `openclaw channels add --channel whatsapp`
+      on the host after deployment.
+    fields: []
     setupUrl: https://developers.facebook.com/apps
 
-  - id: teams
-    channelKey: teams
+  - id: msteams
+    channelKey: msteams
     displayName: Microsoft Teams
     description: Connect OpenClaw agents to a Microsoft Teams channel via bot
     infraRequired: true
     infraNote: >
       After deployment, update the bot's messaging endpoint in Azure Bot Service
       to the gateway webhook URL.
+    plugin:
+      package: "@openclaw/msteams"
+      source: npm
+      version: "2026.9.2"
+    # Same as WhatsApp: --use-env is rejected outright.
+    useEnvSupported: false
+    requiredConfig: [dmPolicy, groupPolicy]
+    defaults:
+      dmPolicy: pairing
+      groupPolicy: allowlist
     fields:
       - name: appId
         label: App (client) ID
@@ -93,5 +195,10 @@ integrations:
         label: App password
         description: Client secret from the Azure app registration
         sensitive: true
-        envDefault: OPENCLAW_TEAMS_APP_PASSWORD
+        envDefault: ""   # no --use-env path; collected interactively on the host
+      - name: tenantId
+        label: Directory (tenant) ID
+        description: Azure AD tenant ID for the app registration
+        sensitive: false
+        envDefault: ""
     setupUrl: https://portal.azure.com/

package/spec/mcp-tools.yaml

@@ -11,6 +11,15 @@
 #   R8  — enums for closed sets
 #   R10 — all four annotation hints set
 #   R11 — annotations bound to safety modes (--read-only, --no-destructive)
+#
+# NOTE on `output:` — these blocks are DESCRIPTIVE, not generated. gen-schemas reads
+# `input:` and `annotations:` only; nothing emits an MCP outputSchema, and no handler is
+# checked against what its entry claims to return. Making them real means generating an
+# outputSchema per tool and returning `structuredContent` from every handler — worth doing,
+# but it is a change to all 18 handlers, not a spec edit. Until then, treat `output:` as the
+# intended shape and the handler as the truth. Keeping them honest is not optional:
+# clawops_status declared health, uptimeSec, openclawVersion and agentCount for three
+# releases while returning none of them (WO-47).
 
 version: 1
 
@@ -32,14 +41,15 @@ tools:
   - name: clawops_status
     toolset: [cli, read]
     description: |
-      Get current status of a clawops-managed stack: gateway health, OpenClaw
-      version, agent count, uptime.
+      Get what is deployed for a clawops-managed stack: public IP, gateway URL,
+      SSH user, or that nothing is deployed yet. Reads stack outputs; does not
+      contact the host.
 
-      Use when: the user asks about the health of a deployed instance, whether
-      the gateway is responding, or wants a quick overview.
+      Use when: the user asks what exists for a stack, or where to reach it.
 
-      Do NOT use when: the user asks for live logs (use clawops_logs) or wants
-      to see specific configuration values (use clawops_config_get).
+      Do NOT use when: the user asks whether the gateway is actually WORKING —
+      that needs the host, so use clawops_doctor. Also not for live logs (use
+      clawops_logs_tail) or config values (use clawops_config_get).
     annotations:
       title: Get Stack Status
       readOnlyHint: true
@@ -51,15 +61,60 @@ tools:
         type: string
         optional: true
         description: Stack name. Defaults to active stack from config.
+    # What the handler returns: the stack's deployment outputs. Health, version and agent
+    # count are NOT here — they need the host, and asking for them is clawops_doctor.
     output:
-      health: { type: enum, values: [healthy, degraded, down, unknown] }
+      stack: { type: string }
+      publicIp: { type: string }
       gatewayUrl: { type: string, format: uri }
-      uptimeSec: { type: integer }
-      openclawVersion: { type: string }
-      agentCount: { type: integer }
-      provider: { type: enum, values: [aws, gcp, azure, local] }
+      sshUser: { type: string }
+      status: { type: enum, values: [not bootstrapped, not deployed] }
       region: { type: string }
 
+  - name: clawops_doctor
+    toolset: [cli, read]
+    description: |
+      Run clawops's diagnostics and return the report: Node and Pulumi runtime, config,
+      SSH key and known_hosts, cloud credentials per configured provider, and the
+      supported OpenClaw range. With stackName, also contacts the host for container
+      state, the deployed OpenClaw version, a real gateway health probe, whether the
+      port is published to the internet, disk usage on the state directory, log
+      rotation, and hardening drift.
+
+      Use when: something is not working and you do not yet know what; before any
+      deploy, upgrade or migration; or to find out which OpenClaw version a gateway is
+      actually running.
+
+      Do NOT use when: you already know the problem and want to fix it. This tool only
+      reports — it changes nothing, and never runs `openclaw doctor --fix`. Repair is
+      part of clawops_gateway_update, where it is gated on a verified backup.
+
+      Every check carries a status: fail (something is wrong that clawops can name),
+      warn (worth knowing, not broken), info (did not apply). `ok` is false only when
+      something failed — a fresh machine with no stacks is full of warnings and healthy.
+    annotations:
+      title: Run Diagnostics
+      readOnlyHint: true
+      destructiveHint: false
+      idempotentHint: true
+      openWorldHint: true
+    input:
+      stackName:
+        type: string
+        optional: true
+        description: |
+          Stack to include remote checks for. Without it, only the local machine is
+          checked — no SSH connection is made.
+      failuresOnly:
+        type: boolean
+        optional: true
+        default: false
+        description: Return only failing and warning checks. Passing checks are counted, not listed.
+    output:
+      ok: { type: boolean }
+      counts: { type: object }
+      sections: { type: array }
+
   - name: clawops_logs_tail
     toolset: [cli, read]
     description: |
@@ -236,10 +291,29 @@ tools:
         description: Defaults to provider configured for this stack
       region: { type: string, optional: true }
       instanceType:
-        type: enum
-        values: [micro, small, medium, large, gpu]
+        type: string
         optional: true
         default: small
+        description: |
+          A clawops size (micro|small|medium|large|gpu) or a provider-native machine type.
+          Not an enum: Azure offers SKU families per subscription, and an account offered
+          none of the five sizes clawops names would otherwise have no way to deploy.
+      sshCidr:
+        type: string
+        optional: true
+        description: |
+          CIDR(s) allowed to reach SSH, comma-separated, or 'auto' for the caller's own
+          address. Omitted means none, and nothing will be able to connect — including
+          every clawops day-two command.
+      gatewayCidr:
+        type: string
+        optional: true
+        description: CIDR(s) allowed to reach the gateway port. Requires publishGateway=all.
+      publishGateway:
+        type: enum
+        values: [loopback, all]
+        optional: true
+        description: Which interface the gateway binds. 'all' serves plaintext HTTP.
       openclawVersion: { type: string, optional: true, description: "semver or 'stable'/'dev'" }
       dryRun: { type: boolean, optional: true, default: false }
     output:
@@ -399,28 +473,6 @@ tools:
       valid: { type: boolean }
       issues: { type: array, items: { type: string } }
 
-  - name: clawops_agents_restart
-    toolset: [cli]
-    description: |
-      Restart a specific OpenClaw agent on the remote gateway.
-
-      Use when: the user reports an agent is stuck, errored, or unresponsive;
-      or after a config change that the agent needs to pick up.
-
-      Do NOT use when: the issue is gateway-wide — use clawops_gateway_restart.
-    annotations:
-      title: Restart OpenClaw Agent
-      readOnlyHint: false
-      destructiveHint: true
-      idempotentHint: true
-      openWorldHint: true
-    input:
-      stackName: { type: string, optional: true }
-      agentId: { type: string }
-    output:
-      previousStatus: { type: string }
-      newStatus: { type: string }
-
   - name: clawops_gateway_restart
     toolset: [cli]
     description: |
@@ -429,8 +481,8 @@ tools:
       Use when: a gateway-wide config change requires reload, or the gateway is
       reported as unresponsive.
 
-      Do NOT use when: only a specific agent is affected — use
-      clawops_agents_restart. Brief downtime (~10s).
+      Note: OpenClaw 2.0 removed per-agent restart; `gateway restart` is the only
+      restart it offers, and it affects every agent on the host. Brief downtime (~10s).
     annotations:
       title: Restart Gateway Daemon
       readOnlyHint: false

package/spec/models.yaml

@@ -39,6 +39,9 @@ providers:
       - { id: deepseek-reasoner,  displayName: "DeepSeek Reasoner (R1)" }
     defaultModel: deepseek-chat
     configPath: models.providers.deepseek
+    plugin:
+      package: "@openclaw/deepseek-provider"
+      version: "2026.9.2"
 
   - id: kimi
     displayName: Kimi (Moonshot AI)
@@ -50,13 +53,27 @@ providers:
       - { id: moonshot-v1-128k,  displayName: "Moonshot v1 128K" }
     defaultModel: moonshot-v1-8k
     configPath: models.providers.kimi
+    plugin:
+      package: "@openclaw/kimi-provider"
+      version: "2026.9.2"
 
   - id: bedrock
     displayName: AWS Bedrock
     credentialSource: aws-profile
-    # No API key — uses EC2 instance role (AmazonBedrockFullAccess) via IMDS.
-    # The Pulumi program attaches AmazonBedrockFullAccess to the instance profile
-    # and passes AWS_PROFILE=default into the container via --env-file.
+    # Bedrock is a plugin provider, so OpenClaw does not resolve its transport on its own:
+    # without `api` the call routes through the OpenAI-compatible transport and fails with
+    # "requires an explicit base URL". Bundled providers do resolve it — `anthropic` selects
+    # anthropic-messages with nothing in the config — so this key is set here and nowhere
+    # else. See docs/spikes/SP-12-bedrock-config-shape.md.
+    api: bedrock-converse-stream
+    # No API key — credentials come from the EC2 instance role via IMDS, resolved by the AWS
+    # SDK chain at call time. The old `AWS_PROFILE=default` env-file mechanism is obsolete
+    # (SP-08); so is the `auth: "aws-sdk"` marker as a *requirement* — Bedrock was reached
+    # with it absent (SP-12 §4) — though clawops still writes it to document the auth route.
+    #
+    # modelId below is the FOUNDATION model id. Bedrock refuses these for on-demand
+    # inference; clawops resolves each to a regional inference profile at plan time, because
+    # the right profile depends on the deployment region and cannot be written down here.
     iamPolicy: AmazonBedrockFullAccess
     iamNote: >
       Credentials are provided by the EC2 instance role. clawops attaches
@@ -80,6 +97,9 @@ providers:
       - { id: deepseek-r1,           displayName: "DeepSeek-R1",            modelId: "deepseek.r1-v1:0",                             family: DeepSeek }
     defaultModel: claude-sonnet-46
     configPath: models.providers.amazon-bedrock
+    plugin:
+      package: "@openclaw/amazon-bedrock-provider"
+      version: "2026.9.2"
 
   - id: ollama
     displayName: Ollama (self-hosted)