Crew connects to Webex over an outbound WebSocket — no public URL, no webhooks. Create a bot on the Webex developer portal, paste one token, and you're talking. Replies land with a live status placeholder while the agent works.
The status badge turns green when connected. Search for your bot's username in Webex and send it a direct message.
# Save token to ~/.kiro/crew/.env echo "WEBEX_BOT_TOKEN=YmFzZTY0…" >> ~/.kiro/crew/.env
In ~/.kiro/crew/config.json:
{ "webex": { "enabled": true, "allowed_emails": ["you@example.com"] } }
Then: kirocrew restart
allowed_emails list rejects everyoneAnyone in an org can message a Webex bot, so add only your own email(s).
| Command | Effect |
|---|---|
/new | Start a fresh conversation |
/compact | Compress context |
/help | List commands |
Messages sent while a reply is in progress are folded into the running turn.
With interactive approval mode, tools that need approval are denied by default — Webex has no approve/deny buttons. Use the dashboard for sessions that need interactive tool approval, or set agent.approval_mode: "auto".
| Key | Default | Purpose |
|---|---|---|
webex.enabled | false | Turns the channel on |
webex.allowed_emails | [] | Webex emails allowed (empty = nobody) |
webex.soft_threshold_pct | 80 | Suggest /compact past this usage |
webex.hard_threshold_pct | 95 | Force-compact past this |
webex.bot_token | "" | Token fallback if WEBEX_BOT_TOKEN isn't set |
Prefer the WEBEX_BOT_TOKEN env var over bot_token.
| Problem | Fix |
|---|---|
| No reply | Your email isn't in allowed_emails or enabled is false |
No Webex channel started in logs | Token isn't set or is invalid |
| Group-space messages ignored | By design — DM the bot directly |
Webex