Files

gavrielc 57a6491c7e v2: channel isolation model, manage-channels skill, refactored channel skills

- Add three-level isolation model (shared session, same agent, separate agent)
  with agent-shared session mode for cross-channel shared sessions
- Create /manage-channels skill for wiring channels to agent groups
- Refactor all 12 v2 channel skills: lean SKILL.md + VERIFY.md + REMOVE.md
  with structured Channel Info section for platform-specific metadata
- Create /add-discord-v2 skill (was missing)
- Add step 5a to setup SKILL.md invoking /manage-channels after channel install
- Update setup/verify.ts to check all 12 channel token types
- Add docs/v2-isolation-model.md explaining the isolation model
- Update v2-checklist.md and v2-setup-wiring.md to reflect completed work

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

2026-04-09 13:19:19 +03:00

1.8 KiB

Raw Blame History

name, description

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

Add Webex Channel

Adds Cisco Webex support to NanoClaw v2 using the Chat SDK bridge.

Pre-flight

Check if src/channels/webex.ts exists and the import is uncommented in src/channels/index.ts. If both are in place, skip to Credentials.

Install

npm install @bitbasti/chat-adapter-webex

Uncomment the Webex import in src/channels/index.ts:

import './webex.js';

npm 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.

1.8 KiB Raw Blame History