gitops/optimclaw

Fork 0

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

Files

T

History

13697976db feat(extensions): improve auth UX and add load-time validation (#536 )

* feat(extensions): add load-time validation for auth capabilities

Catch common misconfigurations (missing auth section, missing setup_url,
short prompts) at startup via tracing::warn instead of silently failing
at auth time.

* feat(extensions): improve auth prompts, setup_url, and showAuthCard

Add setup_url and descriptive prompts to channel and tool capabilities
files. Fix showAuthCard in web gateway and improve extension manager
auth flow messaging.

* refactor(extensions): extract MIN_PROMPT_LENGTH constant in validate()

Address review feedback: replace magic number 30 with a named constant
for readability and maintainability.

[skip-regression-check]

Co-Authored-By: Claude Opus 4.6 <[email protected]>

---------

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

2026-03-04 13:57:10 -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

build.sh

fix: add missing build.sh for Discord and WhatsApp channels (#429 )

2026-03-01 08:41:20 +00: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(extensions): improve auth UX and add load-time validation (#536 )

2026-03-04 13:57:10 -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