Groups you run

tg helps the admin of a group: it shows the questions nobody answered, who joined and who added them, and what a week in the group came to. It reads without marking anything read, so checking on a group does not tell its members you looked.

Everything here works from your personal account. The commands in full: usage.md; every option: commands.md.

With an agentCopy Anchor Link

An agent with a terminal (Claude Code, Codex) needs the skill; one without (Claude Desktop, Cursor) needs the MCP server. Below: what you say, what the agent calls, and what you get back.

An admin's morning: who is waiting for an answerCopy Anchor Link

You:    What is still unanswered in "Hiking"?
Agent:  (tg review --chat "Hiking" --unanswered 4h --json)
        Unanswered for more than 4 hours — 3 questions:
        · Lena, 08:12 — "What time do we leave on Saturday?"
        · Artem, yesterday 22:40 — a reply to your post about the route: "Are the tents shared?"
        · Ira, yesterday 19:05 — "Who brings the pot?"
        You or the admins answered the rest.

A question is a message with ? in it, or a reply to you or to an admin; a ? inside a link does not count. It is answered when you or an admin replied to it, or were the next to speak after the person who asked. When Telegram does not say who the group's admins are, only your answers count, and the command says so.

Newcomers this weekCopy Anchor Link

You:    Who joined "Hiking" this week?
Agent:  (tg chats events "Hiking" --type join,add --json)
        Five people:
        · Kate — added by Lena, Tuesday
        · Oleg — joined by the link, Wednesday
        · …

chats events reads the group's service messages, so it sees what Telegram kept in the chat's history: who joined, left, was added or removed, and by whom. tg chats members list gives everyone in the group with their role and when they were last seen.

A link that leakedCopy Anchor Link

You:    The invite link to "Hiking" ended up in a public chat. Replace it, and stop members adding people.
Agent:  (tg chats link reset "Hiking" --json)
        (tg chats update "Hiking" --only-admins-add on --json)
        Done: the old link no longer works, the new one is https://t.me/+…, and only admins can add
        people now.

link reset answers the group as it now stands, new link included; chats update answers the same, so the agent can say what changed without reading the group again.

A weekly reportCopy Anchor Link

You:    Sum up the week in "Hiking".
Agent:  (tg review --chat "Hiking" --since-time 2026-09-20T00:00 --json)
        Decided: we leave on 4 October, at 7:00 from the station.
        Taken on: Lena — food, Artem — tents.
        Open: who brings the pot — asked three times, no answer.

On a scheduleCopy Anchor Link

No agent is needed for a list of open questions: it is an ordinary command.

0 9,21 * * * tg review --chat "Hiking" --unanswered --json >> ~/hiking-open.jsonl 2>> ~/tg-cron.log

cron has no terminal and often no XDG_RUNTIME_DIR, without which tg cannot reach the keyring: recipes.md.

What there isCopy Anchor Link

An agent without a terminal gets the reading half as MCP tools: tg_review with unanswered, tg_chats_events, tg_chats_members, tg_chats_inspect (mcp.md).

create, join, leave, update, link reset, members and admins change something the group's members see: a new group tells the people added, and a join or a leave shows in the chat. Each goes through the profile's permissions and the send guard, and each person added counts toward the hourly limit (security.md).

RulesCopy Anchor Link

A group's rules say what tg chats moderate looks for and what it may do about it. They live in a file of this profile, never in Telegram, and nothing watches the group in the background: a rule acts only when you run chats moderate.

tg chats rules show "Hiking"                       # the defaults, marked not saved, until the first change
tg chats rules set "Hiking" links delete           # a message with a link is deleted
tg chats rules set "Hiking" blocked 12345,67890    # these people…
tg chats rules set "Hiking" blockedPeople remove   # …are removed when they write or join
tg chats rules set "Hiking" consent.delete allow   # delete without asking
tg chats moderate "Hiking" --dry-run               # what it would do, doing nothing
tg chats moderate "Hiking"                         # judge what is new since the last run, and act

Each rule's action is report, delete or remove. Whether a delete or a remove happens is the group's level for it, consent.delete and consent.remove: deny never, readonly only reports, ask asks you about each one (the default; --allow-dangerous says yes to all), allow does it. Every action still goes through the send guard and its hourly limit, and a run stops after --max-actions (10). The next run starts where this one stopped; --since-time looks at a moment of your own and leaves that point where it is.

Over MCP, tg_chats_moderate acts only where a level is allow; what asks is listed for you, not done. newAccount is not offered: Telegram does not say how old an account is.

LimitsCopy Anchor Link

• Telegram's history is the record. chats events and review see what the chat's history still holds; a service message an admin deleted is gone for them too.
• Admins are known only where Telegram says. Without them, review --unanswered counts only your answers, and says so.
• Nothing watches a group by itself. A check runs when you, an agent at your request, or your schedule runs it.
• Telegram's rate limits apply. Reading every member of a large group is many requests; a FLOOD_WAIT answer says how long to wait (troubleshooting.md).