Adds Cisco Webex support via the Chat SDK bridge. NanoClaw doesn't ship channels\nin trunk — this skill copies the Webex adapter in from the channels branch.
The mechanical steps under Apply carry nc: directive fences: an agent\nreads the prose and applies them, and a parser can apply them deterministically\nfrom the same document. Every directive is idempotent, so the whole skill is\nsafe to re-run; anything a parser can't apply falls back to the prose beside it.
Fetch the channels branch and copy the Webex adapter and its registration test\ninto src/channels/ (overwrite — the branch is canonical):
src/channels/webex.ts\nsrc/channels/webex-registration.test.ts\nAppend the self-registration import to the channel barrel (skipped if the line\nis already present). This one line is the skill's only reach-in into core:
\nimport './webex.js';\nPinned to an exact version — the supply-chain policy rejects ranges and latest.\nThe Webex adapter ships under the third-party @bitbasti/* namespace, not\n@chat-adapter/*, so it carries its own version line (0.1.0) rather than\ntracking the chat core version:
@bitbasti/chat-adapter-webex@0.1.0\nBuild first: it guards the typed createChatSdkBridge(...) core call and proves\nthe dependency is installed. Then run the one integration test.
pnpm run build\npnpm exec vitest run src/channels/webex-registration.test.ts\nwebex-registration.test.ts imports the real channel barrel and asserts the\nregistry contains webex. It goes red if the import line is deleted or drifts,\nif the barrel fails to evaluate, or if @bitbasti/chat-adapter-webex isn't\ninstalled (the import throws) — so it also covers the dependency from step 3.\nEnd-to-end delivery against a real Webex space is verified manually once the\nservice runs — see the webhook setup below.
Webex bot setup is human and interactive — these steps are prose, not directives\n(no parser can click through the Webex Developer Portal). A recipe rebuild\nproduces a compiling, registered adapter that cannot receive a message until\nthey're done.
\nhttps://your-domain/webhook/webex.Capture the two values, then write them. prompt only asks and binds the\nanswer to a name; a separate directive consumes it — so the same prompts could\nfeed ncl or the OneCLI vault instead of .env by swapping only the consumer.\nHere they go to .env (set-if-absent — a value you've already filled in is\nnever overwritten):
Paste the Bot Access Token — from the Webex bot you created.\nPaste the webhook secret you set for signature verification.\nWEBEX_BOT_TOKEN={{bot_token}}\nWEBEX_WEBHOOK_SECRET={{webhook_secret}}\nThe Chat SDK bridge automatically starts a shared webhook server on port 3000\n(WEBHOOK_PORT to change it), handling /webhook/webex. This port must be\npublicly reachable for Webex to deliver events. Running locally, expose it with\nngrok (ngrok http 3000), a Cloudflare Tunnel, or a reverse proxy on a VPS —\nthe resulting public URL is the base for the webhook URL above.
If you're in the middle of /setup, return to the setup flow now. Otherwise run\n/manage-channels to wire this channel to an agent group.
webexGET /rooms) to list spaces and their IDs.Sends fail with 401. The Bot Access Token is shown once, on the bot's page under developer.webex.com → My Apps — it is not the 12-hour personal access token from the API docs pages, which is the classic mix-up (that one works briefly, then everything 401s). Regenerate the token on the bot page if needed; regenerating invalidates the old value, so update WEBEX_BOT_TOKEN right away.
Messages in the space never reach the agent. Webex delivers only to the webhook you created: it must target your public host at /webhook/webex (shared webhook server, port 3000) with resource messages. List your webhooks with GET https://webexapis.com/v1/webhooks using the bot token — Webex flips a webhook to inactive after repeated delivery failures, and it stays off until you re-enable or recreate it.
Events arrive but are rejected. Signature mismatch: the secret set at webhook creation must equal WEBEX_WEBHOOK_SECRET exactly. Recreate the webhook with a known secret and update .env to match.
Adapter installed but silent. Run pnpm exec vitest run src/channels/webex-registration.test.ts — red means the barrel import or the @bitbasti/chat-adapter-webex install drifted, so re-run the Apply steps. If green, restart the service so it loads the adapter and the tokens, then watch logs/nanoclaw.log for the webhook hit.