Files

gavrielc c37609ffc8 docs(skills): drop "v2" from skill content + src/index.ts log lines

Cleans up the prose-level v2 references that the rename commit didn't
touch. Skills now describe themselves and the codebase without "v2"
versioning language. /add-X-v2 cross-references in setup, init-first-agent,
and manage-channels updated to /add-X.

Runtime path identifiers (data/v2.db, data/v2-sessions/, container name
nanoclaw-v2) deliberately left as-is — renaming them breaks live installs
without commensurate benefit.

Verified: pnpm run build clean, 326 host tests pass.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-17 14:42:55 +03:00

2.3 KiB

Raw Blame History

name, description

name	description
add-webex	Add Webex channel integration via Chat SDK.

Add Webex Channel

Adds Cisco Webex support via the Chat SDK bridge.

Install

NanoClaw doesn't ship channels in trunk. This skill copies the Webex adapter in from the channels branch.

Pre-flight (idempotent)

Skip to Credentials if all of these are already in place:

src/channels/webex.ts exists
src/channels/index.ts contains import './webex.js';
@bitbasti/chat-adapter-webex is listed in package.json dependencies

Otherwise continue. Every step below is safe to re-run.

1. Fetch the channels branch

git fetch origin channels

2. Copy the adapter

git show origin/channels:src/channels/webex.ts > src/channels/webex.ts

3. Append the self-registration import

Append to src/channels/index.ts (skip if the line is already present):

import './webex.js';

4. Install the adapter package (pinned)

pnpm install @bitbasti/chat-adapter-webex@0.1.0

5. Build

pnpm run build

Credentials

Go to developer.webex.com and create a new bot
Copy the Bot Access Token
Set up a webhook:
- Use the Webex API or Developer Portal to create a webhook pointing to https://your-domain/webhook/webex
- Set a webhook secret for signature verification

Configure environment

Add to .env:

WEBEX_BOT_TOKEN=your-bot-token
WEBEX_WEBHOOK_SECRET=your-webhook-secret

Sync to container: mkdir -p data/env && cp .env data/env/env

Next Steps

If you're in the middle of /setup, return to the setup flow now.

Otherwise, run /manage-channels to wire this channel to an agent group.

Channel Info

type: webex
terminology: Webex has "spaces." A space can be a group conversation or a 1:1 direct message with the bot.
how-to-find-id: Open the space in Webex, click the space name > Settings — the Space ID is listed there. Or use the Webex API (GET /rooms) to list spaces and their IDs.
supports-threads: yes
typical-use: Interactive chat — team spaces or direct messages
default-isolation: Same agent group for spaces where you're the primary user. Separate agent group for spaces with different teams or sensitive information.

2.3 KiB Raw Blame History