mirror of
https://github.com/outbackdingo/optimclaw.git
synced 2026-08-25 14:53:34 +00:00
e9f32eaebe
When installing the Telegram WASM channel via the web UI, a name collision between registry/tools/telegram.json and registry/channels/telegram.json caused the tool entry to win, installing to ~/.ironclaw/tools/ instead of ~/.ironclaw/channels/. This made activation fail with "WASM runtime not available". - Add `get_with_kind()` to ExtensionRegistry for kind-aware lookup - Use `kind_hint` parameter in `install()` to resolve collisions - Rename tool entries to avoid future collisions: telegram → telegram-mtproto, slack → slack-tool - Fix `_bundles.json` stale reference (tools/slack → tools/slack-tool) - Fix `cache_discovered()` to deduplicate by (name, kind) consistently - Add path traversal validation to install/activate/remove entry points - Add tests for kind-aware lookup, discovery cache, and bundle resolution Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
32 lines
807 B
JSON
32 lines
807 B
JSON
{
|
|
"name": "telegram-mtproto",
|
|
"display_name": "Telegram",
|
|
"kind": "tool",
|
|
"version": "0.1.0",
|
|
"description": "Telegram user-mode integration via MTProto for messages and contacts",
|
|
"keywords": ["messaging", "chat", "telegram", "mtproto"],
|
|
|
|
"source": {
|
|
"dir": "tools-src/telegram",
|
|
"capabilities": "telegram-tool.capabilities.json",
|
|
"crate_name": "telegram-tool"
|
|
},
|
|
|
|
"artifacts": {
|
|
"wasm32-wasip2": {
|
|
"url": "https://github.com/nearai/ironclaw/releases/latest/download/telegram-wasm32-wasip2.tar.gz",
|
|
"sha256": null
|
|
}
|
|
},
|
|
|
|
"auth_summary": {
|
|
"method": "manual",
|
|
"provider": "Telegram",
|
|
"secrets": ["telegram_api_id", "telegram_api_hash"],
|
|
"shared_auth": null,
|
|
"setup_url": "https://my.telegram.org/apps"
|
|
},
|
|
|
|
"tags": ["messaging"]
|
|
}
|