Use this page when you are an admin of a Telegram group and want help keeping it in order. You will learn how to find questions nobody answered, see who joined and who added them, sum up a week, remove spam by your own rules and keep a history of the member list. Reading marks nothing read, so checking on a group does not tell its members you looked.

Everything here works from your personal account, in groups where you are an admin. Some words on this page:

• An admin is a member with rights to manage the group. Some commands count only your answers and the admins' answers.
• The local store is the copy of messages that tg keeps on this computer. Reports and tasks use it, so they see only what was downloaded.
• A task is something that waits on you, such as a question nobody answered. tg opens and closes tasks in the local store.
• Rules say what tg personal chats moderate looks for, such as links or flooding, and what it may do.
• A member snapshot is the member list saved on one day. Snapshots over time show who joined and who left.

The full list of group commands is below. Details of each command are in groups and channels in the usage guide; every option is in the command reference.

Your AI agent (for example Claude Code, Codex, Cursor or Gemini CLI) can run these checks for you. An agent with a terminal needs the tg skill; an agent in an app without a terminal needs the MCP server. Below: what you say, what the agent runs, and what you get back.

The names, messages and results below are fictional. Commands are separate from the answer: the agent reads the data and presents it for you.

Start with questions that have been waiting for you or the admins.

Your request:

What in Hiking has been waiting for an answer for more than four hours?

Command:

tg personal review 'chat:Hiking' --unanswered 4h --json

Example agent answer:

3 questions are waiting for an answer.

Person	Question	Waiting
Lena	What time do we leave on Saturday?	6 hours
Sam	Are the tents shared?	12 hours
Ira	Who will bring the cooking pot?	15 hours

Open a question to check the surrounding conversation.

These are review rules: a question mark outside a link, or a reply to you/an admin, can open a question. Your or an admin’s reply or next message can close it. The statistics report counts linked direct answers and can give a different result. If Telegram does not expose the admin list, only your answers count and the result says so.

Review joining events. A new account is a reason to check, not proof of spam.

Your request:

Who joined Hiking this week? Show anyone worth reviewing.

Command:

tg personal chats events "Hiking" 'type:(join OR add) time>=7d' --json

Example agent answer:

Newcomer	How they joined
Kate	Added by Lena
Oleg	Joined himself

Review Oleg’s available profile information before drawing conclusions. Account age alone is not grounds for removal.

Events cover available history only. The current member list can be checked separately.

Replace an invite link only when you have asked for that change.

Your request:

The Hiking invite link leaked. Replace it and let only admins add people.

Replace the link:

tg personal chats link reset "Hiking" --json

Restrict member additions:

tg personal chats update "Hiking" --only-admins-add on --json

Example agent answer:

Setting	Result
Previous invite link	Replaced
Who can add members	Admins only

The new private link is in the requested result; share it only with intended recipients.

These commands change the group. The example request authorises both changes; a request to inspect a link would not.

First see what the rules suggest, without any action.

Your request:

Check Hiking for spam. Do not delete anything yet; show the suggestions.

Command:

tg personal chats moderate "Hiking" --dry-run --json

Example agent answer:

Suggested action: delete a message with an invite link.

Found	Suggestion	Status
Invite link	Delete the message	Preview only

Nothing was deleted. Confirm the exact message if you want the action applied.

Real actions need your request and the profile's permissions. A preview does not give permission to delete.

Ask for a short recap of decisions, commitments and open questions.

Your request:

Summarise the week in Hiking.

Command:

tg personal review 'chat:Hiking date>7d' --json

Example agent answer:

Decided: leave at 7:00 from the station.

Committed:

• Lena — food.
• Sam — tents.

Still open: who will bring the cooking pot.

I can show the source messages if you want to verify the recap.

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

0 9,21 * * * tg personal 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: see running on a schedule.

Only the group owner can enable topics. An existing supergroup needs no upgrade. Upgrading a basic group gives it a new chat id; the local store keeps older messages under the original id and does not merge the two histories.

In a forum topic, text, photo and file captions and scheduled sends all keep the topic, and an explicit reply must belong to that topic. A closed or missing topic is refused before anything is sent. When the outcome of a send is unknown, repeat it with the same --operation-id, chat and topic; for a scheduled send, check tg personal messages scheduled <chat> instead of repeating it.

An agent connected over the MCP server can run the same commands, as far as the profile's permissions allow.

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 (see the send guard).

review and serve keep a list of tasks in the local store. A question nobody answered, and a message that mentions you by name, opens a task; your answer closes it. A task points at its message and never copies it.

See what waits on you, oldest first, then only questions and mentions in one group:

tg personal tasks list state:open

tg personal tasks list chat:<chat id> "(kind:question OR kind:mention)"

Add what the rules cannot see, such as a promise you made, or close a task that needs no answer:

tg personal tasks add msg:telegram/<you>/<chat>/<message> --type promise --category other

tasks categories lists the categories a task can take. To change the list, edit the task_categories section of ~/.config/WireCat/config.json, a file tg, MAX and memo share. It holds only your changes to the default list: a name with its meaning and trigger words adds or replaces a category, and null drops a default one:

{
  "task_categories": {
    "garden": "plants | seedling, es:planta",
    "religion": null
  }
}

config set task_categories.garden "plants | seedling" and config unset task_categories.garden write the same file and keep its other sections; config unset task_categories brings back the default list. A store moved by MESSAGING_STORE reads the config.json beside it.

If the task may be the same job as an open one, tasks add refuses with exit code 2 and lists the candidates. Repeat with --into <task> to link the message to that task, or with --new to open it anyway. If it matches only a task closed in the last 14 days, tasks add opens it as a follow-up, linked follow-up-of the closed one. tasks duplicates lists the pairs the rules found, and tasks merge <task> --into <other> joins them:

tg personal tasks add msg:telegram/<you>/<chat>/<message> --type promise --category other --into <task>

tg personal tasks close <task> --as dismissed --reason no-reply-needed

An AI agent that closes a task states how sure it is with --certainty, from 0 to 1. Below the store's threshold (task_agent_close_min, 0.8 by default) the task stays open with a close suggestion; config set task_agent_close off makes every agent close a suggestion. tasks list close:suggested finds them. Confirm one with tasks close <task>, or refuse it with tasks reject <task>:

tg personal tasks list close:suggested

tg personal tasks reject <task>

Give a task a title, a due date and a date to look at it again, and link the messages and chats it belongs to. The next-check date is for you or your agent; tg never reminds anyone:

tg personal tasks plan <task> --title "Send Anna the contract" --due 2d --remind-time 1d

tg personal tasks link <task> msg:telegram/<you>/<chat>/<message> --chat "Hiking"

See what needs a look today: tasks overdue or due soon, chats where someone waits for your answer, and chats where you wait for theirs. It reads the local store, not the messages' text:

tg personal tasks agenda

tasks agenda and tasks duplicates take query fields:

• tag: and category: keep the tasks with that tag or category: tag:urgent, category:money.
• claimed: says whose claim a task is under: none, mine, others or any. Without it, the agenda shows tasks nobody claimed and your own; claimed:any shows all of them.
• decision: picks the duplicate pairs: review, the default, waits for the reviewing agent, and unsure waits for you: decision:unsure.

tg personal tasks agenda category:money tag:urgent claimed:any

tg personal tasks duplicates decision:unsure

tg skill show follow-ups prints a daily routine for an AI agent that drafts replies from this list and sends nothing.

See open tasks per chat, the oldest one and the median time to close:

tg personal stats tasks show

A closed task stays closed, and a dismissed one never comes back. Only your own answers close a task — an admin's do not — and a mention by @username is not seen. An agent connected over MCP gets the same commands.

A group's rules say what tg personal 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.

Show the rules. Until your first change, they are the defaults, marked as not saved:

tg personal chats rules show "Hiking"

Delete a message that has a link:

tg personal chats rules set "Hiking" links delete

Block these people by id…

tg personal chats rules set "Hiking" blocked 12345,67890

…and remove them when they write or join:

tg personal chats rules set "Hiking" blockedPeople remove

Delete without asking you first:

tg personal chats rules set "Hiking" consent.delete allow

See what the check would do, without doing it:

tg personal chats moderate "Hiking" --dry-run

Check what is new since the last run, and act:

tg personal chats moderate "Hiking"

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.

An agent connected over MCP 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.

If your bot is an admin of the group, it can run the same check: tg <bot> bot chats moderate. A person the bot removes cannot come back by the link unless you add --no-block. The bot judges only messages it saw or imported on this computer, and it does not judge joins. See moderating a group with a bot.

• 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 (see when Telegram asks to wait).

See the week’s activity: messages, people who wrote and replies. For more specific questions—who answers, who needs help and whether newcomers stay—open Statistics.

Your request:

Show Hiking’s activity this week and point out gaps in the history.

Command:

tg personal stats chats show "Hiking" --since-time 7d --offline --json

Example agent answer:

Metric	In available history
Messages	120
People who wrote	18
Replies	30

History is incomplete: these are observed counts, not the group’s full totals. This local request did not fetch joining or leaving events.

Without --offline, the CLI also fetches joining and leaving events. Saved daily member observations remain available locally. Recording start dates and gaps matter: the first report cannot reconstruct past member lists.

tg personal stats chats official <chat> --json

Telegram computes statistics for admins of large enough supergroups and channels, the same as the Statistics screen in its apps. tg personal stats chats official asks for them and prints one JSON object. Telegram picks the period, given as period. Each total comes with the value for the period before it.

• A supergroup (kind: "group") has members, messages, viewers and posters, the top posters, admins and inviters, and 8 graphs: growth, members, new members by source, languages, messages, actions, hours and weekdays.
• A channel (kind: "channel") has followers, views, shares and reactions per post and per story, how many followers have notifications on, the recent posts with their counts, and 12 graphs.

Each graph is a list of series over its x values: date (a day, YYYY-MM-DD), time (ISO 8601) or number. When Telegram cannot give a graph, it shows as { "error": ... } and the other graphs are still there. The command only reads: nothing is sent, marked read or changed. --jsonl is refused.

Telegram answers this only for a chat where it shows you statistics. In a basic group, in a chat you do not administer, or in one that is too small, the command fails with a permission or validation error. One run costs about 10 to 17 requests: the chat card, the statistics, and each graph Telegram sends later. Name the chat by @username or id: a title is first looked up in your chat list, which adds a request for each 100 chats. Telegram keeps statistics on a server of its own, so the first run adds a login key for that server to the session file; it is never printed.

tg personal chats members fetch reads members into the local store, recording profiles, changes, the day's member count and whether the read was complete. --max-pages caps pages. Nobody is recorded as having left after a partial read: that requires reading the whole available list and a known group count no greater than the number read. A larger budget cannot bypass Telegram's member-list limits.

--track adds the group to the tracking list. chats tracking list shows all tracked groups; show shows one group's tracking state and daily counts for the last 30 days. add starts tracking without fetching immediately; remove stops daily fetching and keeps the history already recorded. While tg personal serve runs, it fetches tracked groups one at a time, starting its first round a minute after connecting, and skips groups already fetched on the current UTC day. Tracking does not start serve; if it was stopped for several days, the next run records a new snapshot rather than filling missed days.

tg personal chats members history shows recorded joins, leaves and profile changes, oldest first; a query such as time>=7d limits the period. It never asks Telegram. A join uses Telegram's join time when known, otherwise the first time the person was seen. A leave is dated at the first complete snapshot without them, rather than their exact departure. The first fetch records the initial roster: those people did not necessarily join that day. chats members list --offline reads the last completely saved roster; partial reads do not replace it. Without a complete snapshot, this list can be empty even though some profiles and events have already been recorded. Profiles and history stay in the local store alongside messages.

tg personal chats members audit lists members with bot-like signals and reasons; --max-pages caps pages and a query such as score>=3 sets the threshold (score>=2 when not given). It removes nobody and excludes admins and the owner. meta.truncated means not every member was read. It is unavailable with --offline; scores need human review. Telegram supplies bot, scam, fake, deleted, photo, join and inviter metadata where available. “Never wrote” means no messages were found in the local history, not proof that the person never wrote in the group.

--deep <n> also checks the top n members in full, one person a second: their profile, their oldest profile photo, up to 1,000 stored messages each, and two public spam lists — Combot CAS and lols.bot. Each member's id is sent to those lists. The full check lands in check on each of those members.

“Hiking Club” below is a fictional example group. Download its messages with messages sync first if they are not already stored, then record the current roster and prepare the report:

tg personal chats members fetch "Hiking Club" --track --json

tg personal stats chats show "Hiking Club" --since-time 7d --by day --timezone Europe/Madrid --json

tg personal chats members history "Hiking Club" "time>=7d" --offline --json

tg personal chats tracking show "Hiking Club" --offline --json

tg personal chats members audit "Hiking Club" --json

Ask your agent to report messages, active senders, unanswered questions, membership changes and days with member snapshots. Keep missing entries, meta.truncated and gaps between snapshots visible in the report. Keep tg personal serve running or repeat member fetches for future reports; the first report cannot show departures that happened before the first recorded roster.