telegram-weblisted

Use a dedicated authenticated Telegram Web K profile through Trelio's signed local runtime to inspect the local dialog index, read or search explicit exact chats, check unread state, take one watch snapshot, download an attachment, send one verified local document, perform verified plain-text chat actions, or open headed read-only composer recovery for an explicit account slot. Use when the user explicitly chooses Telegram Web, needs headed Telegram Web login, consent, or recovery, or the enabled telegram-mtproto skill reports exact not_configured, no_access, needs_reconnect, or unsupported_operation status for the requested operation. Supports local Codex and local Claude Code with the same fail-closed runtime contract.
trelio-ru/agent-workspaces · ★ 1 · AI & Automation · score 62

Install: claude install-skill trelio-ru/agent-workspaces

# Telegram Web Use Telegram Web K only through the exact signed local runtime returned by the current Trelio `get_agent_skill` response. Take `runtimeExecution.command` verbatim and append runtime arguments after its terminal `--`. Never invent an executable, call this script by a repository path, import the browser profile, or reconstruct trusted `TRELIO_*` identity/configuration variables. The runtime uses one dedicated persistent Chrome profile per Trelio connection. It never imports cookies from the user's normal browser and never returns a raw Telegram account ID. Telegram Web may retain its ordinary authenticated session, IndexedDB/cache, and message data in that dedicated profile. The runtime creates no separate message-search index or stored search-results database. Codex and Claude Code invoke the same signed CLI and receive the same permissions, approval rules, errors, and result schema. ## Route Telegram work Prefer an enabled `telegram-mtproto` skill for ordinary Telegram work unless the user explicitly selected Telegram Web. Route to this skill as a fallback only when the exact MTProto connection/operation reports one of: - `not_configured`; - `no_access`; - `needs_reconnect`; - `unsupported_operation` with an exact operation reason. Do not switch from MTProto to Telegram Web, or from Telegram Web back to MTProto, after a timeout, DNS/reset/5xx error, control-plane failure, unclear result, or `TELEGRAM_WEB_MUTATION_OUTCOME_AMBIGUOUS`. A transient failure is