tg is a single static Go binary for driving a Telegram personal account (or a bot) from the command line or an AI agent: message yourself, list and triage chats, read history, send/forward/edit/delete messages, upload and download files, manage groups and channels, and stream new messages in real time.

Built on gotd/td.

Download a prebuilt binary or package (.deb/.rpm/.apk) for your platform from the latest release.

$ tg init                                          # write config (release binaries embed app credentials)
$ tg login                                         # QR login — scan once from a logged-in device
$ tg whoami                                         # confirm you're authenticated
$ tg send "Hello world"                             # message yourself (Saved Messages)
$ tg send --peer @gotd_test "Hello world"           # message a peer

App credentials are required. The prebuilt release binaries embed them at build time and present the session as a desktop client, so tg init just works. If you build from source, provide your own from https://my.telegram.org: tg init --app-id APP_ID --app-hash APP_HASH.

The config is written to the gotd subdirectory of your config dir, e.g. ~/.config/gotd/gotd.cli.yaml. The session persists there too, so subsequent commands run headless.

$ tg login                     # QR (default): scan from Settings → Devices → Link Desktop Device
$ tg login --phone +1234567890  # phone-code login (use --phone= to be prompted for the number)
$ TG_PASSWORD=secret tg login   # supply the 2FA cloud password non-interactively

Bot login still works too: provide a token via tg init --token <bot-token> and pass --bot to commands that support it (e.g. tg whoami --bot).

• Structured output: --output json (-o json) on any command emits a stable envelope {"schema":1,"data":…} on stdout. Logs, prompts and progress go to stderr.
• Consistent peers: every <peer> accepts me/self, @username, a phone number, or a t.me/… link. Resolved access-hashes are cached locally.
• Safety: destructive actions (delete, delete-history, unpin-all) require --yes.
• Shell completion: tg completion bash|zsh|fish|powershell, with dynamic completion for peers, accounts, output format and enum flags.

$ tg chats list --output json | jq '.data.chats[].peer.username'
$ tg history @durov --limit 20 -o json

This repo ships an installable Claude Code skill (skills/tg) that teaches an agent how to drive Telegram with tg — setup checks, the JSON/peers conventions, the --yes safety gate, and common recipes. Install it with skills:

$ npx skills add https://github.com/gotd/cli --all
# or a single skill:
$ npx skills add https://github.com/gotd/cli --skill tg

Run tg --help for the full, grouped command list, or tg <command> --help for details.

• Messaging: send, reply, edit, delete, delete-history, forward, history, search (--global), read, pin/unpin/unpin-all/pinned, react/unreact/reactions, draft/drafts, schedule, poll, link, context.
• Media: upload (with --type video/audio/voice/gif/sticker), album, download, stickers.
• Chats & contacts: chats list, chat get/full, mute/unmute, archive/unarchive, resolve, search-public, subscribe, contacts (list, search, add, delete, block/unblock, blocked, import).
• Groups & channels: create-group, create-channel, invite, leave, participants/admins/banned, promote/demote, ban/unban, slow-mode, set-title/set-about/set-photo, invite-link/join-link, topics, recent-actions.
• Profile & folders: profile (update, set/delete photo, status), folders (list, create, add-chat/remove-chat, delete, reorder).
• Realtime: watch [peer] streams new messages as JSON lines; wait [peer] blocks until the next message (with --timeout).

Add named accounts and select them per command:

$ tg accounts add work --app-id … --app-hash …
$ tg login --account work
$ tg accounts                       # list accounts + auth status
$ tg chats list --account work
$ tg watch --account all            # stream every account concurrently, labeled

Initialize a config against the Telegram test server, then log in with a test number. Test mode only switches the DC list — it uses the same app credentials as production (so the same app-id/app-hash requirement applies):

$ tg init --test                # persists test: true
$ tg login --phone 9996621234   # test number for DC 2; the code is 22222
$ tg whoami