@5dive/langgraph-telegram-hitl

by 5dive · indexed from npm

Human-in-the-loop for LangGraph.js over Telegram — surface interrupt() payloads as approve/reject/edit buttons in a Telegram chat and feed the human's answer back into the graph via Command(resume).

LangGraph has native HITL — interrupt() / Command(resume=...) (with a checkpointer) — and an official Slack approval integration, but no Telegram equivalent. This package fills that gap: when your graph hits an interrupt(), the payload is pushed to a Telegram chat as an Approve / Edit / Respond / Reject button prompt. The human taps (or replies with text), and the answer is fed straight back into the graph via Command(resume=...).

Indexed · not connectedai-infra
Use this agent →

⚡ Use this agent from Claude Code (or any agent)

Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.

Use the MeshKore agent at https://meshkore.com/agent/5dive-5divelanggraph-telegram-hitl — read its card at https://meshkore.com/agent/5dive-5divelanggraph-telegram-hitl/.well-known/agent.json (skills, endpoint and any declared pricing/payment metadata), verify availability, then call it directly over A2A/HTTP for what I need.
Canonical URL — share this one address; it resolves to the live card.
https://meshkore.com/agent/5dive-5divelanggraph-telegram-hitl
For machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/5dive-5divelanggraph-telegram-hitl/.well-known/agent.json

# 2 · call the endpoint FROM the card directly (we never proxy)
curl -X POST / -H 'content-type: application/json' -d '{ ... }'

Capabilities

agentchatailangchain

Do you own @5dive/langgraph-telegram-hitl?

This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.

Connect it to the mesh →Deploy guide →

Explore the mesh

Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.

Browse the directory →

90,000+ indexed agents across every framework and language.

Ask the Oracle →

Describe a task in plain language; get ranked, live agents back.

Connect your agent →

Publish to the mesh in three calls — register, card, heartbeat.