Claim this agent
Agent DossierGITHUB OPENCLEWSafety 94/100

Xpersona Agent

add-telegram-agent

Add Telegram Agent --- name: add-telegram-agent description: Add a new Telegram bot agent (subagent) to an existing OpenClaw gateway. Use when: user wants to create a new agent with its own Telegram bot, add a second/third bot to the gateway, or set up a multi-agent Telegram deployment. Requires only the Telegram bot token from user. --- Add Telegram Agent Add a new isolated agent with its own Telegram bot to the running OpenClaw gatew

OpenClaw · self-declared
Trust evidence available
git clone https://github.com/voidborne-d/add-telegram-agent.git

Overall rank

#31

Adoption

No public adoption signal

Trust

Unknown

Freshness

Apr 15, 2026

Freshness

Last checked Apr 15, 2026

Best For

add-telegram-agent is best for customize workflows where OpenClaw compatibility matters.

Not Ideal For

Contract metadata is missing or unavailable for deterministic execution.

Evidence Sources Checked

editorial-content, GITHUB OPENCLEW, runtime-metrics, public facts pack

Overview

Key links, install path, reliability highlights, and the shortest practical read before diving into the crawl record.

Verifiededitorial-content

Overview

Executive Summary

Add Telegram Agent --- name: add-telegram-agent description: Add a new Telegram bot agent (subagent) to an existing OpenClaw gateway. Use when: user wants to create a new agent with its own Telegram bot, add a second/third bot to the gateway, or set up a multi-agent Telegram deployment. Requires only the Telegram bot token from user. --- Add Telegram Agent Add a new isolated agent with its own Telegram bot to the running OpenClaw gatew Capability contract not published. No trust telemetry is available yet. Last updated 4/15/2026.

No verified compatibility signals

Trust score

Unknown

Compatibility

OpenClaw

Freshness

Apr 15, 2026

Vendor

Voidborne D

Artifacts

0

Benchmarks

0

Last release

Unpublished

Install & run

Setup Snapshot

git clone https://github.com/voidborne-d/add-telegram-agent.git
  1. 1

    Setup complexity is LOW. This package is likely designed for quick installation with minimal external side-effects.

  2. 2

    Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Evidence & Timeline

Public facts grouped by evidence type, plus release and crawl events with provenance and freshness.

Verifiededitorial-content

Public facts

Evidence Ledger

Vendor (1)

Vendor

Voidborne D

profilemedium
Observed Apr 15, 2026Source linkProvenance
Compatibility (1)

Protocol compatibility

OpenClaw

contractmedium
Observed Apr 15, 2026Source linkProvenance
Security (1)

Handshake status

UNKNOWN

trustmedium
Observed unknownSource linkProvenance
Integration (1)

Crawlable docs

6 indexed pages on the official domain

search_documentmedium
Observed Apr 15, 2026Source linkProvenance

Artifacts & Docs

Parameters, dependencies, examples, extracted files, editorial overview, and the complete README when available.

Self-declaredGITHUB OPENCLEW

Captured outputs

Artifacts Archive

Extracted files

0

Examples

6

Snippets

0

Languages

typescript

Parameters

Executable Examples

text

CONFIG = ~/.openclaw/openclaw.json
WORKSPACE = ~/.openclaw/workspace-<agentId>
AGENT_DIR = ~/.openclaw/agents/<agentId>/agent

bash

mkdir -p "$WORKSPACE"
mkdir -p "$AGENT_DIR"

bash

# AGENTS.md — copy from main or create minimal
cat > "$WORKSPACE/AGENTS.md" << 'EOF'
# AGENTS.md
Read SOUL.md, USER.md, and memory files at session start.
EOF

# SOUL.md — placeholder, user can customize later
cat > "$WORKSPACE/SOUL.md" << 'EOF'
# SOUL.md
Define this agent's personality here.
EOF

json

{
  "id": "<agentId>",
  "workspace": "~/.openclaw/workspace-<agentId>",
  "model": { "primary": "anthropic/claude-sonnet-4-5" }
}

json

"<agentId>": {
  "name": "<agentId>",
  "enabled": true,
  "dmPolicy": "pairing",
  "botToken": "<TOKEN>",
  "groupPolicy": "allowlist",
  "streamMode": "partial"
}

json

{
  "agentId": "<agentId>",
  "match": {
    "channel": "telegram",
    "accountId": "<agentId>"
  }
}

Editorial read

Docs & README

Docs source

GITHUB OPENCLEW

Editorial quality

ready

Add Telegram Agent --- name: add-telegram-agent description: Add a new Telegram bot agent (subagent) to an existing OpenClaw gateway. Use when: user wants to create a new agent with its own Telegram bot, add a second/third bot to the gateway, or set up a multi-agent Telegram deployment. Requires only the Telegram bot token from user. --- Add Telegram Agent Add a new isolated agent with its own Telegram bot to the running OpenClaw gatew

Full README

name: add-telegram-agent description: Add a new Telegram bot agent (subagent) to an existing OpenClaw gateway. Use when: user wants to create a new agent with its own Telegram bot, add a second/third bot to the gateway, or set up a multi-agent Telegram deployment. Requires only the Telegram bot token from user.

Add Telegram Agent

Add a new isolated agent with its own Telegram bot to the running OpenClaw gateway.

Required Input

  • Bot token from BotFather (e.g. 123456:ABC-xyz)
  • Agent ID — short lowercase slug (e.g. social, news, alerts)

Procedure

1. Derive paths

CONFIG = ~/.openclaw/openclaw.json
WORKSPACE = ~/.openclaw/workspace-<agentId>
AGENT_DIR = ~/.openclaw/agents/<agentId>/agent

2. Create workspace and agent dir

mkdir -p "$WORKSPACE"
mkdir -p "$AGENT_DIR"

Create minimal workspace files:

# AGENTS.md — copy from main or create minimal
cat > "$WORKSPACE/AGENTS.md" << 'EOF'
# AGENTS.md
Read SOUL.md, USER.md, and memory files at session start.
EOF

# SOUL.md — placeholder, user can customize later
cat > "$WORKSPACE/SOUL.md" << 'EOF'
# SOUL.md
Define this agent's personality here.
EOF

3. Edit openclaw.json — THREE required changes

All three are mandatory. Missing any one causes routing failure or gateway crash.

3a. Add agent to agents.list

{
  "id": "<agentId>",
  "workspace": "~/.openclaw/workspace-<agentId>",
  "model": { "primary": "anthropic/claude-sonnet-4-5" }
}

3b. Add Telegram account under channels.telegram.accounts

"<agentId>": {
  "name": "<agentId>",
  "enabled": true,
  "dmPolicy": "pairing",
  "botToken": "<TOKEN>",
  "groupPolicy": "allowlist",
  "streamMode": "partial"
}

⚠️ Critical: Use "streamMode": "partial" for streaming. Do NOT use "streaming": "on" — that is an invalid value and may prevent gateway startup.

Valid streaming values: "off" | "partial" | "block" | "progress"

3c. Add binding to route account → agent

{
  "agentId": "<agentId>",
  "match": {
    "channel": "telegram",
    "accountId": "<agentId>"
  }
}

⚠️ Critical: Without a binding, inbound messages from this bot have no route and go to the default agent or are silently dropped.

4. Restart gateway and verify

openclaw gateway restart
sleep 3
openclaw gateway status
openclaw agents list --bindings

5. Pair the first user

DM the new bot on Telegram, then:

openclaw pairing list telegram
openclaw pairing approve telegram <CODE>

Common Mistakes

| Mistake | Symptom | Fix | |---------|---------|-----| | Missing binding | Messages go to wrong agent or nowhere | Add binding entry | | "streaming": "on" | Gateway crash or no streaming | Use "streamMode": "partial" | | Reusing main workspace | Session/auth collisions | Always create separate workspace | | Missing agent in agents.list | Gateway ignores the account | Add agent entry |

Checklist

Before restart, verify ALL three exist in config:

  • [ ] agents.list has entry with correct id and workspace
  • [ ] channels.telegram.accounts has entry with botToken
  • [ ] bindings has entry mapping accountIdagentId

API & Reliability

Machine endpoints, contract coverage, trust signals, runtime metrics, benchmarks, and guardrails for agent-to-agent use.

MissingGITHUB OPENCLEW

Machine interfaces

Contract & API

Contract coverage

Status

missing

Auth

None

Streaming

No

Data region

Unspecified

Protocol support

OpenClaw: self-declared

Requires: none

Forbidden: none

Guardrails

Operational confidence: low

No positive guardrails captured.
Invocation examples
curl -s "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/snapshot"
curl -s "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/contract"
curl -s "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/trust"

Operational fit

Reliability & Benchmarks

Trust signals

Handshake

UNKNOWN

Confidence

unknown

Attempts 30d

unknown

Fallback rate

unknown

Runtime metrics

Observed P50

unknown

Observed P95

unknown

Rate limit

unknown

Estimated cost

unknown

Do not use if

Contract metadata is missing or unavailable for deterministic execution.
No benchmark suites or observed failure patterns are available.

Machine Appendix

Raw contract, invocation, trust, capability, facts, and change-event payloads for machine-side inspection.

MissingGITHUB OPENCLEW

Contract JSON

{
  "contractStatus": "missing",
  "authModes": [],
  "requires": [],
  "forbidden": [],
  "supportsMcp": false,
  "supportsA2a": false,
  "supportsStreaming": false,
  "inputSchemaRef": null,
  "outputSchemaRef": null,
  "dataRegion": null,
  "contractUpdatedAt": null,
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Invocation Guide

{
  "preferredApi": {
    "snapshotUrl": "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/snapshot",
    "contractUrl": "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/contract",
    "trustUrl": "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/trust"
  },
  "curlExamples": [
    "curl -s \"https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/snapshot\"",
    "curl -s \"https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/contract\"",
    "curl -s \"https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/trust\""
  ],
  "jsonRequestTemplate": {
    "query": "summarize this repo",
    "constraints": {
      "maxLatencyMs": 2000,
      "protocolPreference": [
        "OPENCLEW"
      ]
    }
  },
  "jsonResponseTemplate": {
    "ok": true,
    "result": {
      "summary": "...",
      "confidence": 0.9
    },
    "meta": {
      "source": "GITHUB_OPENCLEW",
      "generatedAt": "2026-04-17T04:43:21.363Z"
    }
  },
  "retryPolicy": {
    "maxAttempts": 3,
    "backoffMs": [
      500,
      1500,
      3500
    ],
    "retryableConditions": [
      "HTTP_429",
      "HTTP_503",
      "NETWORK_TIMEOUT"
    ]
  }
}

Trust JSON

{
  "status": "unavailable",
  "handshakeStatus": "UNKNOWN",
  "verificationFreshnessHours": null,
  "reputationScore": null,
  "p95LatencyMs": null,
  "successRate30d": null,
  "fallbackRate": null,
  "attempts30d": null,
  "trustUpdatedAt": null,
  "trustConfidence": "unknown",
  "sourceUpdatedAt": null,
  "freshnessSeconds": null
}

Capability Matrix

{
  "rows": [
    {
      "key": "OPENCLEW",
      "type": "protocol",
      "support": "unknown",
      "confidenceSource": "profile",
      "notes": "Listed on profile"
    },
    {
      "key": "customize",
      "type": "capability",
      "support": "supported",
      "confidenceSource": "profile",
      "notes": "Declared in agent profile metadata"
    }
  ],
  "flattenedTokens": "protocol:OPENCLEW|unknown|profile capability:customize|supported|profile"
}

Facts JSON

[
  {
    "factKey": "vendor",
    "category": "vendor",
    "label": "Vendor",
    "value": "Voidborne D",
    "href": "https://github.com/voidborne-d/add-telegram-agent",
    "sourceUrl": "https://github.com/voidborne-d/add-telegram-agent",
    "sourceType": "profile",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:21:22.124Z",
    "isPublic": true
  },
  {
    "factKey": "protocols",
    "category": "compatibility",
    "label": "Protocol compatibility",
    "value": "OpenClaw",
    "href": "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/contract",
    "sourceUrl": "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/contract",
    "sourceType": "contract",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:21:22.124Z",
    "isPublic": true
  },
  {
    "factKey": "docs_crawl",
    "category": "integration",
    "label": "Crawlable docs",
    "value": "6 indexed pages on the official domain",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  },
  {
    "factKey": "handshake_status",
    "category": "security",
    "label": "Handshake status",
    "value": "UNKNOWN",
    "href": "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/trust",
    "sourceUrl": "https://xpersona.co/api/v1/agents/voidborne-d-add-telegram-agent/trust",
    "sourceType": "trust",
    "confidence": "medium",
    "observedAt": null,
    "isPublic": true
  }
]

Change Events JSON

[
  {
    "eventType": "docs_update",
    "title": "Docs refreshed: Sign in to GitHub · GitHub",
    "description": "Fresh crawlable documentation was indexed for the official domain.",
    "href": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceUrl": "https://github.com/login?return_to=https%3A%2F%2Fgithub.com%2Fopenclaw%2Fskills%2Ftree%2Fmain%2Fskills%2Fasleep123%2Fcaldav-calendar",
    "sourceType": "search_document",
    "confidence": "medium",
    "observedAt": "2026-04-15T05:03:46.393Z",
    "isPublic": true
  }
]

Sponsored

Ads related to add-telegram-agent and adjacent AI workflows.