Telegram messages sent as you,
not as a bot
tguser is a CLI that speaks MTProto from your own account,
so an AI agent can write to private chats, groups and channels like a person.
uv tool install git+https://github.com/yerza06/tguser-cli.git
tguser login # one interactive sign-in, done by a human
tguser chat add work -1001234567890 # save the chat under the name "work"
tguser send "Build finished" --to workA user account, not a bot
Bots cannot start conversations, cannot join arbitrary groups, and are visibly bots. tguser uses the MTProto protocol with your own account, so messages arrive from you.
Built for AI agents
Designed from the start for Claude Code, Codex CLI, OpenClaw, Hermes-Agent and the like. The agent runs one plain shell command and the message goes out.
Chat aliases like `git remote`
Name a chat once and forget the numeric ID: --to work instead of -1001234567890. Aliases live in a local SQLite database.
Runs from any directory
After uv tool install the tguser command is on your PATH with no uv run and no project root. An agent’s working directory is never known in advance.
Agent Skill in one command
npx skills add https://github.com/yerza06/tguser-cli --skills tguser teaches your agent the whole CLI — following the open Agent Skills spec.
Ten kinds of messages
Text, documents, photos, videos, audio, voice notes, video notes, stickers and contacts — with albums, captions and stable exit codes 0 / 1 / 130.
How it fits together
A human signs in once — tguser login is interactive and asks for a phone number, a code and
possibly a 2FA password. After that the session persists in ~/.config/tguser/, and every later
send runs unattended. The agent never handles your credentials; it only calls tguser send.
Everything stays on your machine: the session file, the alias database and the API credentials
live in ~/.config/tguser/, with .env at mode 600. There is no server component.