Files
optimclaw/registry/tools/telegram.json
T
c937dfa315 fix(registry): use versioned artifact URLs and checksums for all WASM manifests (#1007)
All 14 registry manifests (10 tools + 4 channels) referenced legacy
unversioned filenames and null checksums, causing 404s on install.

Updated all manifests with versioned artifact URLs and concrete SHA256
values cross-referenced against v0.18.0 checksums.txt. Also fixed
slack-tool and telegram-mtproto tool manifests which used incorrect
artifact name prefixes (slack-tool vs slack, telegram-mtproto vs telegram).

Verified: all 14 URLs return HTTP 200, all checksums match release.

Fixes #958

[skip-regression-check]

Co-authored-by: Claude Opus 4.6 <[email protected]>
2026-03-12 11:09:43 -07:00

39 lines
943 B
JSON

{
"name": "telegram-mtproto",
"display_name": "Telegram Tool",
"kind": "tool",
"version": "0.2.0",
"wit_version": "0.3.0",
"description": "Your agent uses your Telegram account to read and send messages",
"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-0.2.0-wasm32-wasip2.tar.gz",
"sha256": "2c66245913854be4294021fc6bb479e43f7d65830c5cec25cf6c60a71d1af468"
}
},
"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"
]
}