tg-cli

Topics in the source

• tg — the owner's personal Telegram from the command line
• Machine execution
• Installation readiness
• Telegram drafts
• Message permalinks
• Boundaries
• First setup
• Output

tg works with the owner's real personal account. A mistake here does not fail a test; it writes to a living person. One call, one action: connect, do it, print, exit. Read this skill, then discover only the commands relevant to the task. tg commands search messages --json describes one command; tg commands messages --json describes that group. Both include arguments, options, global options and exit codes. Use tg --help for a shorter explanation. Command words form one path, not a list of groups: inspect different groups in separate calls. tg commands --json returns the entire tree when you need an overview; do not read it in full before every task. effects.remote: "write" identifies a write to Telegram; effects.local: "write" alone, a write to this machine. commands --json connects to no account. Its contract field is the shared JSON contract version; it changes only when response fields change incompatibly, not with a package upgrade, so check that field rather than comparing whole outputs. This file holds the traps and boundaries. For a common task, tg guide lists scenarios — the commands in order and why each — and tg guide --json gives one as data; tg commands without --json i

This is an excerpt. Refer to the complete source and its current requirements.