Xpersona
agentCLAWHUBUnverified

Telegram Full Access

Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and man...

OpenClaw
View on ClawHubHomepage

Rank

62

Safety

84

Downloads

971

Updated

Oct 12, 2026

Version

1.1.1

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 971 downloads reported by the source. Last updated 10/12/2026.

Avoid when

  • Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor
Clawhubvendor · observed Oct 12, 2026
Protocol compatibility
OpenClawcompatibility · observed Oct 12, 2026
Adoption signal
971 downloadsadoption · observed Oct 12, 2026
Latest release
1.1.1release · observed Jul 22, 2026
Handshake status
UNKNOWNsecurity

What changed

Newest first. Only changes that point at a source are listed.

  • Release 1.1.1release

    Clarify Chiho bearer authentication and Claude connector compatibility

    Observed Jul 22, 2026 · source

Install and run

Setup complexity: low.

clawhub skill install s17bp094epwabt8q4pp0edvd0983nm1k:telegram-full-access
  1. Install using `clawhub skill install s17bp094epwabt8q4pp0edvd0983nm1k:telegram-full-access` in an isolated environment before connecting it to live workloads.
  2. No published capability contract is available yet, so validate auth and request/response behavior manually.
  3. Review the upstream CLAWHUB listing at https://clawhub.ai/seichris/telegram-full-access before using production credentials.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/snapshot"

Run-check

$0.02 USD

1 measured facts are behind this paywall: success rate and latency, uptime and estimated cost, when not to use it, how to call it, benchmark scores.

Agents pay $0.02 in USDC. A card payment is $0.50, the smallest a card allows.

Documentation

CLAWHUB

22,661 characters of source documentation, loaded on request.

Extracted files

3 files captured from the source.

SKILL.md

---
name: telegram-full-access
description: "Give OpenClaw full access to your Telegram: Log into a local Telegram session, use a personal or dedicated account, let Claw automate your workflows, and manage chats through a CRM UI."
metadata:
  openclaw:
    homepage: https://github.com/chihoai/telegram-for-ai-agents
    envVars:
      - name: TELEGRAM_API_ID
        required: false
        description: Required for the self-hosted local Telegram session path.
      - name: TELEGRAM_API_HASH
        required: false
        description: Required for the self-hosted local Telegram session path.
      - name: DATABASE_URL
        required: false
        description: Required for self-hosted CRM metadata, sync, import, and export.
---

# telegram-full-access

Use this skill when the user wants OpenClaw to work with Telegram through an explicit user-owned Telegram login instead of the limited-access Telegram Bot API.

This gives an agent account-level read/write access through a Telegram session owned by the user. It can be used with a personal Telegram account or with a dedicated Telegram account created for agent workflows.

## What This Sets Up

- A local Telegram session controlled by the user.
- Account-level Telegram access for OpenClaw, using the same class of access as Telegram Web or a Telegram app session.
- A path to let Claw automate Telegram workflows across chats the logged-in account can access.
- A CRM UI path through Chiho.ai for managing chats, contacts, tags, tasks, summaries, and follow-ups.

## Why Not Bot Access

Telegram bot access is useful for bot-first workflows, but it is intentionally narrower:

- Bots must be manually added to chats.
- Bots do not automatically see a user's existing Telegram inbox.
- Bots may have limited visibility into group history, membership, and account-level organization.

Use this skill when the user wants account-level access through an explicit user-owned Telegram login, not a bot that has to be invited chat by chat.

## Choose A Runtime

### Chiho.ai Cloud

Use Chiho.ai Cloud when the user wants the hosted CRM UI and does not want to manage local Telegram API credentials.

1. Open [Chiho.ai](https://chiho.ai/signup).
2. Connect Telegram with the user-owned account that should be available to the agent.
3. Use the CRM UI for chats, tags, tasks, summaries, follow-ups, and team workflows.
4. Mint an Agent Access token from `https://chiho.ai/profile/agent-access`.
5. Copy the MCP endpoint shown on Agent Access and configure OpenClaw or another compatible client to send `Authorization: Bearer <CHIHO_AGENT_TOKEN>` with every MCP request.

Claude Code supports this hosted bearer-token flow through `claude mcp add --transport http ... --header ...`. Claude web, Claude Desktop, and Cowork remote custom connectors require OAuth for authenticated hosted servers and cannot use Chiho Agent Access tokens yet. Never place a Chiho token in a connector URL or OAuth credential field.

Prefer this path when the user

_meta.json

{
  "ownerId": "kn7c1rymeb2nv12cx4t7vqfaf181t35p",
  "slug": "telegram-full-access",
  "version": "1.1.1",
  "publishedAt": 1784714227907
}

skill-card.md

## Description:

Give OpenClaw full access to Telegram through a user-owned session, with options for a hosted Chiho.ai CRM flow or a self-hosted local tgchats runtime.

This skill is ready for commercial/non-commercial use.

## Publisher:

[seichris](https://clawhub.ai/user/seichris)

### License/Terms of Use:

MIT-0

## Use Case:

External users and developers use this skill to connect OpenClaw or compatible agents to Telegram through an explicit user-owned login, enabling account-level chat automation and CRM-style chat management. It is intended for workflows where bot-only Telegram access is too limited.

### Deployment Geography for Use:

Global

## Known Risks and Mitigations:

Risk: The connected Telegram account grants broad read/write access to chats available to that account.

Mitigation: Use a dedicated Telegram account with limited chat membership where possible, and require explicit user approval before enabling write-capable message workflows.

Risk: Chiho Agent Access tokens can expose the connected Telegram session if leaked.

Mitigation: Protect and rotate the token, send it only as a bearer header, and do not paste it into URLs or OAuth credential fields.

Risk: The self-hosted setup asks users to run external code that handles sensitive Telegram API credentials and local session data.

Mitigation: Pin the GitHub repository to a reviewed commit and use locked dependency installation before running npm scripts.

## Reference(s):

- [ClawHub skill page](https://clawhub.ai/seichris/skills/telegram-full-access)
- [telegram-for-ai-agents on GitHub](https://github.com/chihoai/telegram-for-ai-agents)
- [Local tgchats runtime skill](https://github.com/chihoai/telegram-for-ai-agents/blob/main/skills/tgchats-local/SKILL.md)
- [Telegram workflow catalog](https://github.com/chihoai/telegram-for-ai-agents/blob/main/docs/SKILL_CATALOG.md)
- [Chiho.ai signup](https://chiho.ai/signup)
- [Chiho Agent Access](https://chiho.ai/profile/agent-access)
- [Telegram API app credentials](https://my.telegram.org/apps)

## Skill Output:

**Output Type(s):** [Text, Markdown, Shell commands, Configuration, Guidance]

**Output Format:** [Markdown with inline bash code blocks]

**Output Parameters:** [1D]

**Other Properties Related to Output:** [Includes hosted bearer-token setup guidance, local environment variable guidance, and runtime selection guidance.]

## Skill Version(s):

1.1.1 (source: server release metadata)

## Ethical Considerations:

Users should evaluate whether this skill is appropriate for their environment, review any generated or modified files before relying on them, and apply their organization's safety, security, and compliance requirements before deployment.

Related agents

Same protocol, similar job.

Github ReposUpdated 3d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW
Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW
Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.

MCPOPENCLAW
Github ReposUpdated 7mo agoRank 70

CopilotKit

The Frontend for Agents & Generative UI. React + Angular

OPENCLAW

Machine-readable data

The same record, as JSON, for agents and crawlers.

{
  "facts": [
    {
      "factKey": "vendor",
      "category": "vendor",
      "label": "Vendor",
      "value": "Clawhub",
      "href": "https://clawhub.ai/seichris/skills/telegram-full-access",
      "sourceUrl": "https://clawhub.ai/seichris/skills/telegram-full-access",
      "sourceType": "profile",
      "confidence": "medium",
      "observedAt": "2026-10-12T00:03:29.625Z",
      "isPublic": true
    },
    {
      "factKey": "protocols",
      "category": "compatibility",
      "label": "Protocol compatibility",
      "value": "OpenClaw",
      "href": "https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/contract",
      "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/contract",
      "sourceType": "contract",
      "confidence": "medium",
      "observedAt": "2026-10-12T00:03:29.625Z",
      "isPublic": true
    },
    {
      "factKey": "traction",
      "category": "adoption",
      "label": "Adoption signal",
      "value": "971 downloads",
      "href": "https://clawhub.ai/seichris/telegram-full-access",
      "sourceUrl": "https://clawhub.ai/seichris/telegram-full-access",
      "sourceType": "profile",
      "confidence": "medium",
      "observedAt": "2026-10-12T00:03:29.625Z",
      "isPublic": true
    },
    {
      "factKey": "latest_release",
      "category": "release",
      "label": "Latest release",
      "value": "1.1.1",
      "href": "https://clawhub.ai/seichris/telegram-full-access",
      "sourceUrl": "https://clawhub.ai/seichris/telegram-full-access",
      "sourceType": "release",
      "confidence": "medium",
      "observedAt": "2026-07-22T09:57:07.907Z",
      "isPublic": true
    },
    {
      "factKey": "handshake_status",
      "category": "security",
      "label": "Handshake status",
      "value": "UNKNOWN",
      "href": "https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/trust",
      "sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-seichris-telegram-full-access/trust",
      "sourceType": "trust",
      "confidence": "medium",
      "observedAt": null,
      "isPublic": true
    }
  ],
  "events": [
    {
      "eventType": "release",
      "title": "Release 1.1.1",
      "description": "Clarify Chiho bearer authentication and Claude connector compatibility",
      "href": "https://clawhub.ai/seichris/telegram-full-access",
      "sourceUrl": "https://clawhub.ai/seichris/telegram-full-access",
      "sourceType": "release",
      "confidence": "medium",
      "observedAt": "2026-07-22T09:57:07.907Z",
      "isPublic": true
    }
  ]
}

Record generated Oct 12, 2026.

For crawlers

This page is free to read. The run-check above is the only paid part, and it answers HTTP 402 until it is paid. Everything else here is public.

  • One record, as JSON: card, facts, snapshot, contract, trust, changes, warnings, seen by, disagreements.
  • Every agent, one feed: /.well-known/ai-catalog.json
  • What this site sells, and the price: /.well-known/x402
  • Paid run-check: /api/v1/agents/clawhub-seichris-telegram-full-access/run-check

Sponsored

Ads related to Telegram Full Access and adjacent AI workflows.