gitops/optimclaw

Fork 0

mirror of https://github.com/outbackdingo/optimclaw.git synced 2026-08-25 14:53:34 +00:00

Files

T

History

b3bf50f10e feat: add pairing/permission system to all WASM channels and fix extension registry (#286 )

Port Telegram's permission model (owner_id, dm_policy, allow_from, pairing codes)
to Discord, Slack, and WhatsApp WASM channels. Add web UI for configuration and
pairing approval. Fix extension registry issues preventing Discord install and
causing Slack activation to hit the wrong endpoint.

WASM channels:
- Discord: add DiscordConfig, permission checks, ephemeral pairing replies,
  fix capabilities.json (header_name→name), downgrade wit-bindgen to 0.36
- Slack: expand SlackConfig with permission fields, add check_sender_permission
  and send_pairing_reply via chat.postMessage
- WhatsApp: expand WhatsAppConfig with permission fields, add permission checks
  and pairing reply via Cloud API
- Telegram: reformat capabilities.json, add setup.required_secrets

Extension system:
- Add Discord to KNOWN_CHANNELS in bundled.rs and to extension registry
- Rename "slack" MCP→"slack-mcp", "slack-channel"→"slack" to fix name collision
- Add ExtensionSource::Bundled variant handling in discovery.rs
- Add get_setup_schema/save_setup_secrets to ExtensionManager
- Add needs_setup field to InstalledExtension

Web gateway:
- Add GET/POST /api/extensions/{name}/setup for configuration modal
- Add GET /api/pairing/{channel} and POST /api/pairing/{channel}/approve
- Add configure modal UI (password fields, provided badges, auto-generate hints)
- Add pairing request UI on active WASM channel cards
- Show "Restart to activate" label instead of Activate button for WASM channels

Co-authored-by: Claude Opus 4.6 <[email protected]>

2026-02-20 23:21:32 -08:00

src

feat: add pairing/permission system to all WASM channels and fix extension registry (#286 )

2026-02-20 23:21:32 -08:00

Cargo.lock

feat: add pairing/permission system to all WASM channels and fix extension registry (#286 )

2026-02-20 23:21:32 -08:00

Cargo.toml

feat: add pairing/permission system to all WASM channels and fix extension registry (#286 )

2026-02-20 23:21:32 -08:00

discord.capabilities.json

feat: add pairing/permission system to all WASM channels and fix extension registry (#286 )

2026-02-20 23:21:32 -08:00

README.md

Add GitHub tool and Discord channel (#34 )

2026-02-16 15:58:13 +04:00

README.md

Discord Channel for IronClaw

WASM channel for Discord integration - handle slash commands and button interactions via webhooks.

Features

Slash Commands - Process Discord slash commands
Button Interactions - Handle button clicks
Thread Support - Respond in threads
DM Support - Handle direct messages

Setup

Create a Discord Application at https://discord.com/developers/applications
Create a Bot and get the token
Set up Interactions URL to point to your IronClaw instance
Copy the Application ID and Public Key
Store in IronClaw secrets:
```
ironclaw secret set discord_bot_token YOUR_BOT_TOKEN
```
Note: The discord_bot_token secret is the only value read directly by this Discord channel WASM component. The discord_app_id and discord_public_key secrets are used by the IronClaw host (for example, to verify Discord interaction signatures and manage slash command registration) and are not accessed from the WASM module itself.

Discord Configuration

Register Slash Commands

curl -X POST \
  -H "Authorization: Bot YOUR_BOT_TOKEN" \
  -H "Content-Type: application/json" \
  https://discord.com/api/v10/applications/YOUR_APP_ID/commands \
  -d '{
    "name": "ask",
    "description": "Ask the AI agent",
    "options": [{
      "name": "question",
      "description": "Your question",
      "type": 3,
      "required": true
    }]
  }'

Set Interactions Endpoint

In your Discord app settings, set:

Interactions Endpoint URL: https://your-ironclaw.com/webhook/discord

Usage Examples

Slash Command

User types: /ask question: What is the weather?

The agent receives:

User: @username
Content: /ask question: What is the weather?

Button Click

When a user clicks a button in a message, the agent receives:

User: @username
Content: [Button clicked] Original message content

Error Handling

If an internal error occurs (e.g., metadata serialization failure), the tool attempts to send an ephemeral message to the user:

❌ Internal Error: Failed to process command metadata.

Check the host logs for detailed error information.

Advanced Usage

Embeds

To send embeds, include an embeds array in the metadata_json field of the agent's response. The structure should match the Discord API embed object.

Troubleshooting

"Invalid Signature"

Check that discord_public_key is set correctly in IronClaw secrets.
This validation happens on the host before reaching the WASM.

"401 Unauthorized"

Check that discord_bot_token is set correctly in IronClaw secrets.
Ensure the bot is added to the server.

"Interaction Failed"

The interaction might have timed out (Discord requires a response within 3 seconds).
The interactions_endpoint_url might be unreachable.

Building

cd channels-src/discord
cargo build --target wasm32-wasi --release

License

MIT/Apache-2.0