Changelog — Telegram
Read release notes and changes in the Telegram CLI, including fixes and new capabilities.
See what changed in releases: new capabilities, fixes and changes that may affect your commands. Start with your installed version, then use the linked guide for the feature you want to try.
Notable changes to @wirecat/tg-cli. One section per version, newest first; versions follow
semantic versioning, so before 1.0.0 the command interface may still change.
0.123.0 — 10.11.2026
Added
muted:in search and stats, from@wirecat/cli-core0.633.0.muted:falseleaves out the chats you muted, sostats messages show -- 'date>=30d muted:false'counts only what the sync still reads.stats messages responsesandstats messages waitingtake it too.store import, from@wirecat/cli-core0.633.0. Loads made-up chats, people and messages from a file marked synthetic into a test store, such as Desktop's sandbox; it refuses the owner's real store.
0.122.0 — 10.11.2026
Changed — may break callers
- Built on cli-core 0.630.0 (was 0.624.0). The store moves to version 63 on first open. Each person's kind is
kept on the person, and saving a chat's members leaves the rows of members who stayed, so memo's
people listfilters, counts and pages in SQL. People who wrote in a one-to-one chat or a small group now count as the owner's people, no rule joins anyone to the owner's person, and a name is matched across Cyrillic and Latin. A tool on an older cli-core that saves members clears the kept kinds, so tg, max and memo move together. What changed in between is in cli-core's changelog.
0.121.0 — 09.11.2026
Changed — may break callers
- Built on cli-core 0.624.0 (was 0.619.0). The store moves to version 61 on first open (people ties, additive). What changed in between is in cli-core's changelog.
search messages --timeout 30smay search for up to about 29 seconds. It stopped at 2 seconds whatever time the run was given, so a valid query over a large store failed in WireCat Desktop. Without--timeoutit stays 2 seconds, for agents and MCP too.schedule pause <name>andschedule resume <name>take a schedule off its timer and keep it;schedule runstill runs it.--atrepeats:--at 08:30 --at 18:00runs twice a day.
0.120.0 — 09.11.2026
Changed — may break callers
tg messages sync --allleaves out the chats you muted. An account with many muted groups no longer downloads them all. The answer counts them inlimited.muted, and a note says how to read them. Messages already stored stay, and a chat you name (tg messages sync <chat>) or keep with--full-historyis read as before. To read muted chats again, pass--with-mutedfor one run, or settg config set history_muted true. From cli-core 0.619.0 (was 0.618.0).- EmbeddingGemma is the default text model for search by meaning, not e5-small. A computer that already has
e5-small and not EmbeddingGemma keeps e5-small.
tg models downloadno longer asks to accept its terms;--accept-termsis ignored. tg contacts linkrun by an agent proposes the link instead of making it, and needs--reason. Only the owner decides; an agent'stg contacts unlinkis refused.
Fixed
bin/releasepublishes when main has onlychanges/fragments and no## Unreleased. With the version taken on npm it looked for## Unreleasedto put the next version under, found none and stopped before publishing. It now adds the new version's heading above the newest one and collects the fragments into it.
0.119.0 — 09.11.2026
Added
tg account remove --keep-data|--delete-datalogs the profile out on Telegram's side, then forgets it on this computer: its session files, its app id and hash and proxy password in the keyring, its bots' history sessions and what cli-core keeps for it.--keep-dataleaves its messages searchable;--delete-datadeletes them. A bot token stays, and so does every other profile. A run with moved folders forgets its own copy and never logs out for the owner.tg models setandtg models addfrom cli-core 0.609.0: choose the local embedding model every WireCat CLI uses, and add one of your own from Hugging Face. A question with a time in it (HH:MM,10:30) is searched by its words again.- tg ships
contracts/wirecat.json, which says which hosts it talks to over HTTP. WireCat Desktop reads it to show you, before you install, what tg touches:api.telegram.org(bots) andmy.telegram.org(registering your app), plus the proxy you set. Your account's own connection to Telegram (MTProto) is not HTTP and is not in that list. - A pull request adds its changelog entries as a fragment,
changes/<branch>.md. Open pull requests no longer conflict under## Unreleased.pnpm docs:checkchecks each fragment, andbin/releasecollects them into the version's section. An entry under## Unreleasedstill works during the move.
Changed — may break callers
- tg now writes the shared store at version 59, and an older WireCat CLI refuses it until it is upgraded. Run
<cli> upgradefor each WireCat CLI on the same store. From cli-core 0.615.0, whose message templates live in the store.
Fixed
tg serveexits when the build it runs is out of date, so its service starts the new one. Every minute it checks whether the shared store moved to a format this build can no longer write, or whether a newer tg is installed. If so it logsserve.outdatedand exits with code 3, and the systemd unit (Restart=on-failure) starts the installed version. Before, a serve could run for a day on the old build and store nothing.- After
tg store recover run, the next ordinary sync fetches again what the damage may have taken. The recovery marks what each chat held from a day before the last deep check that passed as not fetched, so a sync no longer jumps over a hole inside a chat. From cli-core 0.618.0 (was 0.616.0).
Security
- The chat with BotFather is kept out of search. It holds every bot token BotFather sent, so search over all chats
(
memo searchtoo), search by meaning andmemo contextleave it out;tg messages listand a search that names the chat still read it. Takes effect with the cli-core release that readsChat.searchable, at the next sync of the chat list; that release also masks bot tokens in every chat. - tg's HTTP reaches only the hosts it declares. Every Bot API call and every step of app registration goes
through cli-base's
hostFetch. It refuses any other host before a byte is sent, checks each redirect and drops theAuthorizationheader on a redirect to another site. Through a SOCKS5 or HTTP proxy the check still holds. It does not cover MTProto, which GramJS sends over its own sockets to Telegram's data centres, or an MTProxy. From cli-base 0.87.0 (was 0.80.8) and cli-core 0.615.0 (was 0.609.0).
0.118.0 — 08.11.2026
Added
tg config settakescrm.<provider>:<account>.linksandcrm.<provider>:<account>.company-types, the store settings a CRM tool's sync reads (cli-core 0.606.0).
Changed — may break callers
- tg opens the store that memo and the other WireCat tools now migrate, and moves it to store version 57. A store at version 56 or later is refused by tg 0.117.0 and older, and by every tool built on a cli-core older than 0.606.0, with a request to upgrade. Upgrade tg, max and memo together (cli-core 0.606.0, 0.607.0).
--offlineon a command that needs Telegram answerspermission_error(offline.refused), exit code 5.chats inspect,chats send-as,topicsandupgradeansweredvalidation_error, exit code 2. A script that checks for exit code 2 there needs the new code (cli-core 0.607.0).contacts contextandcontacts prepareread only accounts of the profile's own scope. A personal profile no longer shows a linked person's mail, messages, events or meetings from work accounts, and a work profile none from personal ones. The answer's newaccountslists every account read, with its scope (cli-core 0.605.0).- A name typed with е finds the chat or person named with ё. A name that matched one chat or person exactly may
now match two (
АленаandАлёна); tg then refuses it and lists both, as for any other ambiguous name (cli-core 0.601.0). - Searches read more queries as plain words. A
?that ends a word is a question mark, soinvoice?finds "invoice". Text with a colon, a URL, a bracket or an unbalanced quote (meeting at 10:30) is searched as words where it was refused (cli-core 0.602.0, 0.604.0).
Fixed
- A damaged store file stops writes and names
tg store recover. A run that hit SQLite's "database disk image is malformed" crashed asinternal_error; it now answersconfiguration_error(store.damaged), and later commands that write refuse until a deep check or a recovery passes. Reads still work (cli-core 0.605.0). - People you separated stay apart. A third identity with the same e-mail address could join two people again after you moved them apart (cli-core 0.605.0).
0.117.0 — 07.11.2026
Changed — may break callers
schedule agentandschedule commandtake--deliver-to <route>, no longer--to <route>. In tg--toalready names a message's recipient.schedule listnames the routesdeliver_to; schedules saved with--tokeep delivering (cli-core 0.600.0).
Fixed
- Opening the store no longer drops SQLite's file locks. It used to open the file with truncate, which released the POSIX locks other processes held, so two writers could overlap (cli-core 0.599.0).
- A write that Ctrl-C or Telegram's own server failure cut short ends as
outcome_unknown. A bot's write cut by a stop saidcancelled, and one answered with HTTP 5xx saidprovider_unavailable, as did an account write that Telegram failed with an internal error. Telegram may have carried each of them out, and a caller told "cancelled" could send the message twice. A read keepscancelledandprovider_unavailable. - An account write that Telegram fails with an internal error is sent once, not again and again. mtcute repeated
every request Telegram answered with 500, -500 or -503, with no limit, so a create, join, edit or delete could be
carried out twice. A write now goes once and ends as
outcome_unknown; a read is still asked again, and aFLOOD_WAITis still waited out. A -500 or -503 now reads asprovider_unavailable, not as a refusal. - A bot's refused request no longer repeats Telegram's own text. That text may quote a chat's title or
somebody's message, so the error now says what happened in fixed words, chosen by Telegram's error code, and names
a new supergroup id or a wait only from Telegram's documented fields. "chat not found" is now
validation_error, as Telegram answers it with 400; it wasnot_found, picked from the words. tg account updatethat Telegram failed with an internal error ends asoutcome_unknown. The name, bio or photo may have been changed, and it saidprovider_unavailable.
0.116.0 — 05.11.2026
Fixed
- A Bot API call no longer keeps the finished command in memory for 30 seconds. Its time limit was a timer that
ran to the end even after Telegram answered, and it held everything the command had loaded. A process making
many calls in a row, such as
tg bot watchortg bot mcp, grew by megabytes per call. tg account listno longer shows a bot as an account that is not signed in. A name that only the bot side uses is left out; a name that is your account and a bot too saysbot: true.tg mcp serve --profiles allleaves bots out the same way (cli-core 0.567.0).- A QR login says when the code was scanned. Telegram then takes ten seconds or more to move the login to the
account's data centre, and tg printed nothing until it asked for the 2FA password or finished. It now prints
scan accepted, finishing sign-in, with--jsonas the stderr line{"event":"progress","step":"scanned","message":"scan accepted, finishing sign-in"}, which WireCat Desktop shows.
Added
tg config migratewrites each setting the file lacks intodefaultsat its default, and every write tg makes to the file adds them too. You then find and editlimit,sends_per_hour,recordand the rest inconfig.jsonwithout the docs. Your values, their order and keys tg does not know stay;config unsetdoes not put back what it removed, and a plain read never rewrites the file.tg config showgives each setting's default and what it does (cli-core 0.563.0).- From cli-core 0.563.0:
config repairmends the settings file's JSON syntax;stats messages responsesandstats messages waiting;tasks status,tasks reviewandtasks acknowledge;tasks add --open-new. - From cli-core 0.564.0–0.567.0:
store chats statuscounts the chats the archive holds back to the first message, in part, or not at all;stats tasks showtakes a query and counts the tasks opened and closed in a period (-- created>=30d);has:transcriptfinds voice messages that have a transcription. tg bot listneeds no profile word (tg <profile> bot liststill works; cli-core 0.567.0).
Changed — may break callers
- A new error code,
conflict(exit 15), is intg commands --jsonand the MCP tools' error schema (cli-base 0.77.1). It means a write was refused because what it changes moved on since it was read. A change to a task that someone else changed since you read it now fails with it, notconfiguration_error, exit 3; the reason staystask.stale(cli-core 0.567.0). search allranks every source as one list, searches mail by meaning too, and finds records for a question typed as a sentence (cli-core 0.564.0). Before, each source's hits took turns, and a question found only records that held every one of its words.
0.115.0 — 03.11.2026
Added
wcat tgruns the tool, andwcat --helplists it. The package installswcat-tgbesidetg, andwcat-tg --wcat-describeprints the tool's name, version and description forwcat.
The entries below shipped in 0.114.0 and were missing from its notes, or described wrongly there.
Changed — may break callers
server installfails wheresystemctl --user(orlaunchctl enable) does not work, after it wrote the unit, instead of answering success. On macOSserver stoponly unloads the agent: it starts again at the next login, as a systemd unit does;server uninstallstops that. (cli-core 0.552.0)
Fixed
- The 0.114.0 notes said
--full-historyreads past the history limits for one run. It reads one named chat:messages sync <chat> --full-historyreads that chat past the limits and keeps it in full from then on. search messages --briefkeeps only the reference, chat, time, sender, excerpt and score. It printed every field. (cli-core 0.551.0)- An MCP call whose answer names a step only the person can take no longer fails as a bug. (cli-core 0.551.0)
0.114.0 — 02.11.2026
Added
projects evidenceandprojects statustake--purposeto pick the linked chats they read:--purpose sales,workor--purpose all. A chat left out is listed with its message count and the command that reads it. (cli-core 0.553.0)projects evidence --include-proposedalso reads chats and members proposed for the project and not yet confirmed, and marks what they brought.--compactnow prints rows forprojects evidence. (cli-core 0.553.0)servereads back what arrived while it was off. Telegram's own catch-up gives up on a gap it finds too long after a long downtime. 30 seconds after connecting,servenow reads back each chat that has newer messages than the store held when it started: at most 7 days back, 500 messages a chat and 5 minutes in all. After more than a week offline, runtg <profile> messages sync --allonce. (cli-core 0.552.0)server installenables the service, soservestarts at every login and after a reboot. A service an older tg installed is not enabled: runtg <profile> server installagain.server statussaysstarts_at_login. A service installed from a development checkout is written but not enabled. (cli-core 0.552.0)messages synckeeps to the history limits: by default it skips a group of more than 50 people (history_group_members_max) and reads a group 365 days back and a one-to-one chat 1095 days back (history_group_days,history_dialog_days), and says what it left out underlimited.--full-historyreads past them for one run; raise the settings to keep reading big groups. Live messages are never dropped. (cli-core 0.551.0)tg <profile> projects status <project>says where a project stands, from the store alone. (cli-core 0.551.0)--compactprints one line per item for an agent, from the same answer--jsonprints. (cli-core 0.550.0)messages listreads a window bounded on both sides, offline too. (cli-core 0.547.0)- A command that takes a chat or a message also takes the reference other WireCat tools print
(
msg:…,chat:…). (cli-core 0.546.0)
Changed — may break callers
projects evidenceandprojects statusread only work chats by default. A linked chat with no purpose counts as work; one linked forsales,supportorotheris now left out unless--purposenames it or--purpose allis given. (cli-core 0.553.0)- A search that runs out of time fails with
timeoutand reasonquery.time-limit, in about 2 s, instead ofvalidation_error/query.too-largeafter running far past the limit. The query was valid; addchat:ordate:to search less of the store. (cli-core 0.552.0) - A text of the form
<kind>:<no spaces>given as a chat is read as a reference, and a reference to another account or messenger is refused with its own reason. An option after--is read as an option. (cli-core 0.546.0)
Fixed
- A sync whose output reader goes away finishes its work. A closed pipe used to abort it. (cli-core 0.552.0)
messages deletewith no message id refuses before it connects. (cli-core 0.551.0)page.nextofmessages listruns as written, and an inclusive start keeps a message sent exactly at it. (cli-core 0.547.0)- A timer's run that finds the keyring locked is temporary, not a failed sign-in. A schedule that caught up at
boot, before the login unlocked the keyring, ended with
authentication_error(exit 4), as if the owner had to log in again. A run under a timer (TG_SCHEDULED) now ends asservedoes:provider_unavailable(exit 12) with reasoncredentials.unreachable, whichschedule exec(cli-core) tries again until the login. A command typed by hand still answersauthentication_error, and a profile that never logged in here still exits 4.
0.113.0 — 02.11.2026
Added
tg <profile> messages download --offlinecopies a file this computer already holds, without connecting;--attachment <n>picks one file of a message, and amsg:locator can stand for the chat and message. (cli-core 0.532.0)- The first run of a new version refreshes the agent instructions an older one installed. A stale
SKILL.mdcopy (Claude Code,~/.agents/skills, Hermes) is rewritten once, with one line on stderr; a missing, unversioned or symlinked copy is left alone.TG_NO_SKILL_REFRESH=1turns it off. (cli-core 0.544.0)
Security
- An agent can no longer loosen permissions from its own shell.
tg <profile> config set|unset permissions…run by an agent (Hermes, OpenClaw, Claude Code and others that mark their shell) may only tighten a level, never loosen it, andmcp.authorityandbot.apistay the owner's. So the read-only the desktop app sets holds, even when a chat message talks the agent into runningconfig set. Change permissions in a terminal outside the agent. (cli-core 0.544.0)
0.112.0 — 01.11.2026
Added
- A forum topic's icon:
topics create --emoji <emoji>andtopics edit --emoji <emoji>. The emoji must be in Telegram's default topic icon set, which every account may use, Premium or not;tg <profile> topics icons listshows it. Another emoji is refused, and the error lists the set.topics edit --emoji noneremoves the icon, and the topic shows its colored default again. (cli-core 0.531.0) - Tasks carry
project_key,project_nameandcreated_by, andschedulecommands gain real examples and argument help. (cli-core 0.531.0)
0.111.0 — 01.11.2026
Added
projects evidence --jsongives the sync command for each linked chat aslinked_chats[].sync_command: the line the text shows to sync a chat held in part, or null. (cli-core 0.517.0)
Fixed
projects evidenceno longer says "held from only" for a chat that reaches its first message: it says "held from its first message, behind since ", or "with gaps".messages syncprogress says how far back it got as a date ("back to "), not as a message key. (cli-core 0.517.0)- The agent skill starts a search with
search messages, and adds notes and Drive documents only when the owner asks (search all). It also says that over MCPaskdoes not ask: the owner turns on write approval in their client. ClawHub's review flagged both in skill 1.0.1.
0.110.0 — 01.11.2026
Added
tg <profile> projects evidence <project>(cli-coreprojectsCommand). It shows what this account's stored messages hold about a project: its name, key, aliases, words, contacts, confirmed members and confirmed linked chats.--sync-first(off by default, not on MCP) first syncs the linked chats the store does not hold back to--since-time, one at a time, inside--sync-time(3 minutes in all). A chat the time cuts stays partial, with itsmissingandnext. Themessagespermission guards it. (cli-core 0.511.0)messages sync --jsonprints its progress on stderr, counts only (cli-core 0.507.0). tg now needs@wirecat/cli-base0.68.1, as cli-core 0.507.0 asks.
Changed — may break callers
search messages --discoversearches by meaning when the query uses-,NOT,OR, groups, phrases orexact:(cli-core 0.506.0). Such a query ran strict search alone. Now its words still match the whole query (discovery.method: "lexical-strict"), and messages near in meaning to its wanted words join them. Every hit found by meaning, and every reply and follow-up added, matches every field of the query and every excluded word.
Fixed
search messages --discoverwith a narrow filter (chat:,date:) ranks that filter's own messages by meaning when it holds at most 100,000 messages, instead of the 100 nearest overall, so it fills its page (cli-core 0.506.0).search messages --discoverworks on a read-only store (cli-core 0.506.0).- A long rebuild in one process no longer makes another process's write fail with "database is locked" (cli-core 0.506.0).
0.109.0 — 31.10.2026
Added
search messagesandsearch notessay how many match in all:page.total(cli-core 0.501.0).--jsonaddspage.total: { value, relation }, shaped as Elasticsearch'shits.total:eqis the exact count,gtea lower bound (counting stops at 10,000). The terminal addsshowing 1–20 of 144under the hits.search messages --discovershows follow-ups, later messages that may cancel or change a hit, and no longer fails on a question with a time or a ratio ("until 22:00?") (cli-core 0.492.0, 0.496.0).messages list --offline,search messagesandsearch allsay when the store holds a chat only in part, with themessages syncstep that would fill it (cli-core 0.493.0).- Voice messages can be transcribed by OpenAI:
transcribeWith: "openai", with the key frommodels keys set openai(cli-core 0.499.0).
Changed — may break callers
- tg requires cli-base 0.67.0 (cli-core 0.501.0).
search messages,search allandmessages list --offlineanswermeta.complete: falsewhen a chat they read is held only in part, withmissingandnextnaming it (cli-core 0.493.0). A script that readmeta.completeas "every source answered" now also sees the archive's gaps.- An unknown
transcribeWithin a profile refuses to transcribe withvalidation_error, naming the four values; any value other thanlocalused to mean asking Telegram first (cli-core 0.499.0).
Fixed
search noteskeeps the query's fields for notes found by meaning, and ranks a narrow filter's own notes by meaning (cli-core 0.496.0, 0.501.0).
Security
- A run with moved folders no longer copies the owner's sign-in into the keyring when it refreshes a token (cli-core 0.494.0).
0.108.0 — 31.10.2026
Changed — may break callers
- Notes, documents, annotations and contact notes are found by part of a word, in any letter case.
tg personal search notes 'ontra'now finds «Contract», and a mixed-case Cyrillic word is no longer missed. The title is searched too, not only the text, and a search answers in milliseconds. A query of one or two characters is refused with "search needs at least three characters", as message search is. The first run after the update upgrades the store (version 40) and fills the new index in batches; until then older notes are matched as before. An oldertgdoes not index new notes in an upgraded store, so update every CLI that shares it (cli-core 0.491.0).
0.107.0 — 30.10.2026
Fixed
- Chat titles and contact names match in any case and any alphabet.
tg personal chats list 'title:*ТАРТ*'now finds «Тартус»; before, only Latin letters ignored case. The same holds for contact names and for the names of projects, tags, mail subjects, mailboxes and labels that the shared store keeps. The first run after the update upgrades the store (version 38) and fills the new lowercase copies of what it already holds. An oldertgkeeps working on the upgraded store, and tells you to update (cli-core 0.484.0).
0.106.0 — 29.10.2026
Added
contacts syncsaves each contact's phone when Telegram shows it, socontacts show --offlineanswers it. An onlinecontacts showsaves the phone it reads too. Needs cli-core 0.479.0 (store version 37).- A shared contact card shows its name and whole phone, online and from the store (
--offline).contacts showcarries the profilecontacts infogave, and--hide-phoneleaves the number out ofaccount show,account updateandcontacts show. Needs cli-core 0.477.0. tg <profile> reactions list <chat> <message>shows who reacted to a message, newest first, with the reaction and when.reaction:<emoji>keeps one emoji,--limitand--cursorpage it. It reads only, so a read-only profile and MCP can use it (permission keyreactions.list). Where Telegram hides the list — a channel (reactions.broadcast) or a chat that turned it off (reactions.list-hidden) — it fails with that reason instead of an empty list. Needs cli-core 0.477.0.
Changed — may break callers
- Phone numbers are shown whole, and
contacts infoiscontacts show.--show-phoneis gone: a script that passes it fails as an unknown option, so drop it. The MCP toolcontacts infois gone too;contacts showtakes its place, and a saved permissioncontacts.infois refused with theconfig unsetthat removes it.
Fixed
inbox,review,search messagesandsearch allanswers carrysender_is_me, as 0.473.0 promised, so a script can tell the owner's own messages from others in them too (cli-core 0.478.0).
0.105.0 — 29.10.2026
Changed — may break callers
- The agent skill is listed on ClawHub as
wirecat-tg. Install it withopenclaw skills install @wirecat/wirecat-tg. Thetg-clilisting is no longer updated.tg skill installstill writesskills/tg-cli/.
Fixed
- The help and the command reference show
tg mcp serve --profiles work,personalwithout a profile in front. 0.104.0 showedtg personal mcp serve --profiles work,personal, whichtgrefuses ("name one profile or --profiles, not both"); the--profiles allexamples ofmcp revokeandmcp confighad the same mistake. Aftertg upgrade, the hint to restart a background server of several profiles keeps its--profiles(cli-core 0.474.0).
0.104.0 — 29.10.2026
Changed — may break callers
- An MCP server serves only the profiles you name.
tg mcp servewith no profile now refuses (exit 2) and lists your profiles. Name one (tg work mcp serve), a list (tg mcp serve --profiles work,personal) or every profile (tg mcp serve --profiles all); the line on stderr at start names the profiles served. The same choice applies to--http,mcp revoke,mcp configandmcp server start|stop|status. An app entry that runstg mcp servewith no profile stops working: print it again withtg mcp config --profiles all, or name a profile. A background server of every profile started by an oldertgis stopped bytg upgrade; start it again withtg mcp server start --profiles all. The MCP Registry entry now runstg mcp serve --profiles all(cli-core 0.470.0).
Added
- Every message
tgprints hassender_is_me, true for a message you sent, inmessages list,show,context, search windows andinbox(cli-core 0.473.0). tg runs showkeeps the network's error code of a failed run (error.cause_code, such asETIMEDOUT), never the server's text (cli-core 0.473.0).
Fixed
--offline --transcribesays which voice messages it did not transcribe. They are inmissing, with thetg <profile> messages transcribe <chat> <id>command to run (cli-core 0.473.0).- Each MCP tool call has its own
run_idin its answer and intg runs(cli-core 0.471.0).
0.103.0 — 27.10.2026
Changed — may break callers
- cli-core 0.469.0 and cli-base 0.65.0. cli-core 0.469 accepts only cli-base 0.65, so both pins move together.
cli-base 0.65 knows the verbs
serveandrevoke, so their lint baseline entries are gone, and itscli-dev bundlefinds a server started with a flag beforemcp serve. From cli-core 0.468, an MCP server offers a command that only fetches into the store through its read tool.
Fixed
tg --versionanswers before any of the bundle loads. The bundle is now built by cli-base's sharedcli-dev bundleinstead of tg's ownscripts/bundle.ts; the chunks and every output are the same. A server started with a flag beforemcp serve(tg work --read-only mcp serve) now loads every chunk soon after it starts, as a plainmcp servedoes, so an in-place upgrade cannot pull a chunk from under it.
0.102.0 — 27.10.2026
Changed — may break callers
- Every run is now kept, the ones that worked too. A run that worked is kept 7 days
(
keep_successful_runs_for_days), a failed one 30 (keep_runs_for_days), and the runs folder stays under 200 MB (runs_size_limit_mb). Withrecord_inputon, as by default, asendthat worked now keeps what you typed (the message, a chat named by its title) in a run readable only by you, on this computer, for 7 days.record_input failedkeeps it only in a run that failed;record falsekeeps failed runs only;--no-recordkeeps nothing.watch,serveandmcp servekeep a run that worked only with--record. A run now says who asked for it: the command line, an MCP app (and its tool call), or WireCat Desktop (cli-core 0.467.0).
Added
tg runs showlists each request Telegram got, with its timing, retries and waits. A command's run now has a line for every call to Telegram, for an account and for a bot: the method (messages.getHistory,sendMessage), how long it took, and how it ended. When Telegram asks to wait (FLOOD_WAIT, or a Bot API429) andtgwaits and tries again, the run shows the refused call, then the retry as attempt 2 with the time waited. Message text, names, phone numbers and the bot token are never written.
0.101.0 — 27.10.2026
Changed — may break callers
- The MCP server is
tg <profile> mcp serve;tg <profile> mcpalone prints help. Browser logins are forgotten withtg <profile> mcp revokeinstead ofmcp --revoke. A bot's server istg <name> bot mcp serve. An app entry that runstg personal mcpmust change totg personal mcp serve: runtg personal mcp add <app>ortg personal mcp configagain.mcp server startand the entriesmcp configprints already run the new command (cli-core 0.463.0). tg skill show|status|install --jsonprint{ item, meta }. The skill's fields moved underitem; the Windows installer reads them from there (cli-core 0.462.0).- Search hits of every kind, and
tg topics show, name the fields an agent must read as data (untrusted, for example["title"]on a forum topic). A caller that checks them against an older, strict copy of the schema refuses the new field (cli-core 0.464.0). tg account listsays whether each profile is signed in on this computer (signed_in). A caller that checks the items against an older, strict copy of the schema refuses the new field (cli-core 0.466.0).
Added
tg search allalso finds calendar events in the shared store, marked as untrusted text for agents, andcontacts context|preparename one more field (cli-core 0.453.0–0.461.0).tg upgraderestarts the browser MCP server it started and names the agent sessions still on the old version. After an install, eachtg mcp serve --httpthattg mcp server startlaunched starts again on the same port, address and limits (mcp_servers, old → new version); one started by hand is left running and named. Agent sessions over stdio still on the old version are listed (stale_sessions): restart them from your agent app. This works from the next upgrade on (cli-core 0.464.0).
Fixed
tg mcp servewith no profile marks the profiles that are not signed in. It listed every profile with an account file, so an app could pick one with no session and fail. Each profile is now labelled (default — not signed in) in the app's menu and in the description, and a call for one that is not signed in answers how to sign it in:tg <profile> setup, or from WireCat Desktop. The MCP registry entry and the Glama image starttg mcp serve.- The login page of the browser MCP server says each code works for one login. After an app logs in, a new code
appears in WireCat Desktop and in
tg mcp server status; typing the old one again said only "Wrong code" (cli-core 0.466.0).
0.100.0 — 27.10.2026
Fixed
- Commands start about 0.2 s sooner: the package runs from a bundle. A command loaded about 1,110 module files
before doing any work; it now loads about 55 that hold the same code.
tg messages list --helpwent from 389 to 192 ms, and from 534 to 272 ms on the first run after an install or a reboot. A command that connects still loads Telegram's client library as before. Output is unchanged. The package is larger: 3.0 MB to download instead of 0.5 MB, 16 MB on disk instead of 4 MB. A runningtg serve,watchor MCP server loads all of its code a few seconds after it starts, so upgradingtgunder it does not leave it unable to find a file it had not used yet. - Tg's agent skill publishes to ClawHub as
tg-cliagain. ClawHub keeps skill names per publisher, sowirecat/tg-cliis tg's own name even though another publisher has atg-clitoo, and every WireCat tool's skill now uses its plain name.tg skill installstill writesskills/tg-cli/.
0.99.0 — 27.10.2026
Fixed
- With no session, the error and the MCP instructions also offer WireCat Desktop.
no session,not logged inand missing app keys now say: run the command in a terminal, or sign in from WireCat Desktop (Tools → Telegram → Manage). Over MCP the agent is told never to ask for codes or passwords (cli-core 0.452.0). - Tg's agent skill publishes to ClawHub as
wirecat-tg. The ClawHub nametg-clibelongs to another publisher, so tg's skill could not be listed under it.tg skill installstill writesskills/tg-cli/.
0.98.0 — 27.10.2026
Fixed
- Meaning search and
--discoverrun on the native ONNX Runtime on Windows too (cli-core 0.451.0). Aftertg <profile> models download, text models and the reranker use the native library on Windows x64 and arm64, as they already did on Linux and macOS: 2–3× faster than WebAssembly. The download takesonnxruntime.dllfrom theonnxruntime-nodenpm package (113.5 MB, once, checked by sha256). Picture models (CLIP, SigLIP2) now use the native library as well, wherever it is installed. Results are the same.
0.97.0 — 27.10.2026
Added
tg mcpwith no profile serves every profile, on stdio and with--http(cli-core 0.450.0). An AI app needs one connector for Telegram, not one per profile. Each tool (tg_tools_search,tg_read,tg_write) takes a requiredprofile(every profile here, no default) and the agent is told to ask when you did not name the account. The call runs in that profile's owntg <profile> mcp, started on first use and closed after 10 idle minutes, so each profile's permissions, session and audit log apply as before.tg mcp --revoke,tg mcp configandtg mcp server start|stop|statuswork without a profile too, with their own login.--public-urltakes a path,https://<name>.ts.net/tg, so the tools share one tunnel address. The MCP Registry entry startstg mcp.tg <profile> mcpis unchanged.
Changed — may break callers
- tg needs cli-base 0.63.0 (cli-core 0.450.0). Nothing tg uses changed in it.
0.96.0 — 27.10.2026
Fixed
- Every command spends less time getting ready (cli-base 0.62.0, cli-core 0.449.0). The check of shared commands now
describes each command once, not again for every group above it. A warm
run(["--version"])went from 49 to 29 ms. It catches the same changes as before. - Commands outside
bot apistart faster: its 185 generated Bot API commands are built only when needed.tg messages list,tg --helpand the other commands no longer load about 1.5 MB of generated code.bot api,bot --help,bot mcp,commands,complete,help,mcp,serve,configanddoctorstill build the group, and so does any command when the config saves abot.apipermission. Output is unchanged. - Search by meaning and
search messages --discover's reranker run 2–3× faster on Linux and Apple-silicon Macs after the nexttg models download(cli-core 0.448.0). The download installs a native ONNX Runtime, and the models run on it; without it they run as before. The reranker now reads only the start of the message a hit replies to (cli-core 0.447.0).
0.95.0 — 26.10.2026
Added
-
tg <profile> session start --json --answer-stdinsigns in without a terminal, for WireCat Desktop (cli-core 0.443.0). Each question is aneedsline on stderr ({"event":"needs","field","secret","prompt","hint"}:api_id,api_hash,phone,code,password) and its answer is one line on stdin; my.telegram.org is anopen_urlline. Without--answer-stdin, a run with no terminal still refuses, so an agent's shell never waits on a question. Answers are never printed and never kept in a run record. -
tg <profile> mcp server start|stop|statusruns the HTTP MCP server in the background (cli-core 0.445.0).starttakes--public-url,--portand--permissionasmcp --httpdoes and returns once the server listens;statusgives the port, the address, the one-time login code and the apps that logged in;stopends only the server it started. WireCat Desktop starts and stops it from the tool's Manage panel.
Changed — may break callers
- A run record keeps the command line as typed (cli-core 0.439.0 to 0.447.0).
runs showandrun.jsoncarryargv, the words aftertg, with secrets[redacted](a secret-named option, a password in a URL, a known token format, a random-looking string) and a phone number never kept.tg <profile> config set record_input falsekeeps[redacted]in place of every typed value that may be text. Recorded events still hold ids, never a chat's title or a message's text.
0.94.0 — 26.10.2026
Added
tg skill install --for hermesgives Hermes Agent the skill, andtg skill statussays what Hermes reads (cli-base 0.59.0). It adds~/.agents/skillsto Hermes'sskills.external_dirsthroughhermes config set, keeping the folders already listed, or copies the file into Hermes's home when that fails. With no Hermes installed it fails withnot_foundand writes nothing. A baretg skill installand--for allstill write only the Claude Code and~/.agents/skillscopies.skill status --jsongainshermesbesidetargets.- A run started by OpenClaw or Hermes Agent names that agent (cli-core 0.437.0).
runs showgivesagentasopenclawfor a command OpenClaw's agent ran, withfrom_chat: truewhen a chat message started it; a Hermes run carries its session, so a task claim from Hermes is held per session. - The
tg-cliskill tells OpenClaw and ClawHub that it needstg, and how to install it (metadata.openclaw:requires.binsand the npm package@wirecat/tg-cli). Withtgmissing from PATH, OpenClaw marks the skill not ready and offers to install the package. Claude Code and Codex ignore the block.
0.93.0 — 25.10.2026
Added
store reset --dry-runlists what a reset would empty and deletes nothing (cli-core 0.429.0): the store's files and bytes, every data table with its rows, whether a backup comes first, and whether a serve or another process has the file open.search messages --discoveralso finds messages close in meaning once e5-small is downloaded andconversations rebuildhas given messages their own vectors (cli-core 0.432.0). Each hit'sdiscovery.found_bysays which search found it. Until then discovery searches by words as before and says why. Nothing is downloaded and no text leaves the computer.search messages --discoverreranks its first 50 hits once a reranker is downloaded (cli-core 0.435.0). A local model reads the question with each hit, and its score is mixed with discovery's own; the hits after the first 50 keep their order. The default is mMARCO (136 MB,tg models download mmarco); the profile settingsearch_rerankerpicksbge-reranker-v2-m3(588 MB) oroff. Each reranked hit hasdiscovery.reranker_score;scorestays discovery's. Without the model, discovery keeps its order and saysnot reranked: …(in--jsonand MCP:missingandnext). A search never downloads a model and never sends text anywhere;--exact,--newestand strict queries are untouched.search allfinds messages by meaning too, once e5-small is downloaded and messages have their vectors (cli-core 0.435.0). The meaning hits are merged with the word hits into one messages list; each item'sfoundBysays which search found it. A query with NOT, or with a filter under OR or in a group, stays words only. Without the model or the vectors,search allreads words as before and says why.--exactand--backend serverstay words only.
Changed — may break callers
- A failed
botcommand's run names the Bot API call that failed.runs showandruns listgive itserror.httpthemethodandendpoint_templatebeside the status —{ "method": "POST", "endpoint_template": "/:token/sendMessage", "status": 400 }— where before they had only the status. The token is always written:token: Telegram puts it in the address, and the real one never reaches a run or a trace. Bot requests in--traceand in a recorded run carry the same two fields, and a pretty trace line shows them after the method's name (← getMe POST /:token/getMe 401 …). A script that parses--tracetext sees that extra column. - tg needs Node 22.19+ or 24+ (was 22.16+). The Bot API proxy support uses undici 8, which requires Node 22.19. Bun is unaffected.
- The shared store moves to version 34 (cli-core 0.434.0). Search by meaning ranks through a vector index kept in the store, built on the first open by this version. Once this version opens the store, a CLI on cli-core 0.433.0 or older refuses it and asks to be upgraded, so upgrade every WireCat CLI that shares the store together. When the index's SQLite extension is missing or does not load, opening the store fails with
store.vector-extension-missingorstore.vector-extension-failed: reinstall tg.store checkreportsvector_indexesand fails when an index is out of step. tg upgrade --helpshows onlytg upgrade --checkas its example (cli-core 0.433.0). The baretg upgradeexample is gone: copied and run, it upgraded.- Analysis through Anthropic sends the key as
Authorization: Bearer(cli-core 0.433.0). It used to sendX-Api-Key. A gateway at a custommodels.<purpose>.base_urlthat readsX-Api-Keymust readAuthorizationinstead.
Fixed
- Hermes Agent installs the
tg-cliskill without a security warning. Its install scan held the skill at "caution" because one sentence named the SSH folder by its path, although the sentence says tg refuses to send it. The sentence now says "SSH keys"; what tg refuses is unchanged. - A bot's file upload through a SOCKS5 or HTTP proxy sends the file. Before, the proxied request carried the text
[object FormData]instead of the form, so Telegram refused photos, documents and voice notes sent with--proxy. - A bare
--versionanswers before the program loads: the bin starts through@wirecat/cli-core/cli/start(cli-core 0.429.0). - A stored vector goes once no text in the store uses it (cli-core 0.435.0). An image whose picture changed and a purged chat (
store clear --left, a chat merged into another) left vectors behind, and no longer do.store rebuilddrops the ones older versions left (unused_vectors_dropped), andstore checkcounts them (vectors.unused). conversations embeddings clear --chatdrops the chat's message vectors too (cli-core 0.435.0), not only its conversations'.
0.92.0 — 25.10.2026
Changed — may break callers
- Permissions are checked under each command's full key (cli-core 0.421.0).
messages syncis checked asmessages.syncandbot messages syncasbot.messages.sync; a level onmessagesorbot.messagesstill applies to them. A saved key is read only as written, sochats.muteno longer coverschats unmute. - A saved permission key that names no command is refused, for bot commands too. For a key under a known resource, every command except
config show,setandunsetstops with aconfiguration_errorthat names the key and theconfig unsetthat removes it. tg <profile> search mailis an unknown command. Mail is searched withmemo search mail.doctor --jsonreports the config file's problems asconfig.issues(cli-core 0.423.0).config.erroris gone. Each issue has akind(invalid_json,unknown_setting,unknown_permission,missing_settingorinvalid_value), thefile, theprofileandkeywhere they apply,lineandcolumnfor invalid JSON, a sentence that says what the value has to be (never the value), andfix, theconfig unsetcommand that removes it.doctorlists every problem in the file, still exits 0, and still answers when the JSON is broken. A profile lock, a flag or an environment variable the settings refuse is reported insettings.error.default_profile,analysis_provider,analysis_modelandanalysis_base_urlare unknown settings, andTG_ANALYSIS_PROVIDER,TG_ANALYSIS_MODELandTG_ANALYSIS_BASE_URLare not read. A file that has one is refused like any unknown setting, with theconfig unsetthat removes it. Analysis is set withmodels.analysis.provider,models.analysis.modelandmodels.analysis.base_url(TG_MODELS_ANALYSIS_*);--modeland--base-urlofconversations links rebuildoverride those.- A command refused for a problem in the config file names the first problem and the command that removes it, and says how many more
doctorlists.config show,setandunsetrun on such a file, andconfig unsetremoves a setting no schema knows. An unknown permission key in any section of the file is refused, not only in the sections the command reads. config setsavesconfig.jsonreadable by you only (0600) (cli-core 0.428.0, cli-base 0.57.0). It used to rewrite the file as0644. Anything that reads the config as another user — a system-wide service, a container under another uid — can no longer read it after the next save; run it as the owner, or give it its own config.- A run record names how it was started and why it failed (cli-core 0.425.0).
run.json,runs list,runs showandsearch runsgaincli_command(the whole command,tg messages list),argvwith every value that may be content written[redacted],agent(the coding agent and its session, where it gives one) and, for a failed run,error. A run with no profile named leavesprofileout instead of recordingdefault(cli-core 0.424.0). - The first screen says zm and drive are "searchable with your other WireCat data" (cli-core 0.426.0), and
guide's example names a real scenario instead of<name>.
Added
tg skill statusandtg skill show --for claude|agents(cli-base 0.56.0, through cli-core 0.427.0).skill statussays, for Claude Code and for~/.agents, whether the installed SKILL.md matches this version;skill show --forprints the copy installed there.tg store tables listlists every table of the local archive with its kind and rows;--fulladds each table's size (cli-core 0.427.0).store infoalso says which tools opened the store, its journal mode, pages, migrations and last backup, and counts by provider, chat kind, account, year and attachment kind.
Security
doctorreports aconfig.jsonor config folder that other users can read, with thechmodthat fixes it (cli-core 0.428.0).files.problemslists the config file (wants0600) and its folder (wants0700), also whenTG_CONFIG_DIRnames the folder, and stderr printsto make it private: chmod 600 '<path>'.filesis in the answer also with no profile named and when the settings are refused. Nothing is changed on disk; Windows is not checked.
Fixed
- Every command starts faster: Telegram's client library is loaded only when a command connects.
tg --version,--help,config showandruns listloaded about 1,900 module files, 650 of them mtcute's; now about 1,100. - A deny saved on a sync command now stops it.
permissions.messages.sync: denycan be saved and is honoured, andpermissions.bot.messages.sync: denyis no longer ignored. A deniedbot.messagesalso stopsbot messages listandbot messages syncbefore they connect. - A crash in the middle of a command is reported like any other failure. It used to print Node's stack trace; now it prints the
internal_errorfailure (command.crashed) — one line at a terminal, the JSON error object otherwise — and still exits 1. A stack trace tells a script nothing it can act on, and can carry text that should not reach the screen. A script that read the stack trace on stderr reads the error object instead.
0.91.0 — 25.10.2026
Changed — may break callers
- The shared store moves to version 33 (cli-core 0.420.0). Once this version opens the store, a CLI on an older cli-core refuses it and asks to be upgraded, so upgrade every WireCat CLI that shares the store together.
0.90.0 — 25.10.2026
Changed — may break callers
tg <bot> bot store fetchis nowtg <bot> bot messages sync, and thebot storegroup is gone. It reads a channel's or supergroup's older messages into the bot's local copy, which is what the personalmessages syncdoes, so it carries the same name;storeis for the local database. The options are unchanged. The old path answers with a pointer to the new one. A savedpermissions.bot.store.fetchis refused until you rename it topermissions.bot.messages.sync.
0.89.0 — 25.10.2026
Changed — may break callers
-
A banned Telegram account returns
permission_error(exit 5). A new login cannot lift a ban; this uses the same reason/code contract as the other CLIs. -
Shared CLI contracts now require explicit provider overrides. Command discovery exports the inherited definitions, schemas, error reasons and exact accepted differences. Contact activity uses
scope:andat:queries; diagnostic run searches usestarted_at:bounds instead of time flags. Unknown chat rosters and unrestricted webhook type lists are omitted instead ofnull.
Security
- Dependency resolutions exclude vulnerable Zod and Vite versions. Local and fresh production audits use the fixed versions.
0.88.0 — 24.10.2026
Added
messages send --draftsaves text in the chat for you to review and send from Telegram. It supports formatting, replies and forum topics, uses the separatedraftspermission, and never sends a message. Empty drafts and send-only options are refused.
Fixed
watch --eventsandservereceive reaction snapshots delivered as message edits, including reaction removal. Reaction counts stay current even when Telegram does not send a standalone reaction update.
0.87.0 — 24.10.2026
Fixed
- The MCP guides describe permission-keyed writes and the separate opt-in for raw Bot API calls.
- The catch-up scenario uses
chats mark-readas a separate command. Installation guidance explains how to recover when pnpm's global bin directory is missing from PATH. - Permission-denied commands remain discoverable in CLI help and MCP with current availability, reasons and permission keys. Bot configuration stays bot-scoped, and calls still enforce current permissions.
chats members check --helpgives tg's description again: what--deepreads and that it sends ids to the public ban lists. Since 0.86.0 it showed the shared wording, which leaves both out.
0.86.0 — 24.10.2026
Added
- Send up to ten attachments as one album by repeating
messages send --photoor--file. Photos and videos can share an album; documents form a separate group. The caption belongs to the first item, and JSON includes every sent message. Each item counts toward the hourly send limit. Retrying an unscheduled send with the same operation id repeats the same per-item Telegram ids.
Changed — may break callers
- Shared commands have one name each, and the old names are gone (cli-core 0.406.0).
contacts profileiscontacts info,contacts timelineiscontacts events,contacts alias set|rmiscontacts aliases set|remove.chats link …ischats links …andchats link revokeischats links remove;chats members auditischats members check;chats requests accept|declineischats requests confirm|reject.metadata get|refreshismetadata show|sync,tasks planistasks update,tags autoistags rebuild,attachments text setisattachments update,store reindexisstore rebuild,store gaps planisstore gaps showandstats messages counters refreshisstats messages counters sync.conversations buildisconversations links rebuild,conversations embed status|clearisconversations embeddings status|clear,conversations batches nextisconversations batches showandconversations consents revokeisconversations consents remove.models audio listandmodels text listaremodels list kind:audio|kind:text,models audio|text downloadismodels download,models text keyismodels keys.doctor report createisdoctor reports createanddoctor reportisdoctor reports show.mcp setupismcp add,mcp doctorismcp checkandcommands schemaiscommands info. An old name stops with the new one in the message; CLI and MCP use the same paths. - The hidden old option spellings are removed. Use
--analysis-provider,--embedding-provideror--consent-providerfor--provider,--answer-modelonconversations links clear,--template-modeon reply rules,--claimontags remove,--text-fileoncontacts notes, andkind:in theinboxandreviewquery. - A saved permission key with an old path stops every command with
configuration_errorand names the key to rename it to, for examplepermissions.conversations.embedtopermissions.conversations.embeddings.config setandconfig unsetstop too, so rename the key by hand inconfig.json(where it is).
0.85.0 — 24.10.2026
Added
- The first command at a terminal asks three questions once for every WireCat tool (cli-core 0.404.0): which
languages you write and speak, which other WireCat tools to install, and whether commands and agents may only read.
Answered in any tool, they hold in all of them; "read only" caps every profile, over MCP too.
tg setupasks them again. Agents,--json,--no-input,CIandTG_READ_ONLYare never asked.
0.84.0 — 24.10.2026
Added
permissions.mcp.authoritydecides whether an MCP server offers the commands that change what a later run may do (cli-core 0.400.0):config set|unset,schedule command|agent|remove, reply rules and consents, recipient lists, chat rules,server install,skill install, model keys, media archive timers andflood clear. It isdenyby default, so an agent still cannot loosen its own limits until you runtg <profile> config set permissions.mcp.authority allowin a terminal (add--botfor a bot's server). Permissions and the MCP guide explain it.
Changed — may break callers
-
tg mcpoffers the writes that had no permission key before, eachaskby default (cli-core 0.401.0): store backup, restore, migrate, repair, reset, clear, decrypt and copy deletion, server start/stop/restart, model downloads,schedule run|exec,doctor report createandaccount sessions end; the bot server offersstore fetch. Over MCPaskgoes ahead, so set a key toreadonlyordenyto hide a tool.tasks duplicatesistasks duplicates list. -
tg <profile> events list --jsonwrites times as ISO 8601 and ids as strings (cli-core 0.401.0):starts_at,ends_at,deleted_at,created_atandupdated_at, as every other answer does. -
A bot's MCP server can offer
bot api, behindpermissions.bot.api(cli-core 0.402.0). It isdenyby default;tg <profile> config set --bot permissions.bot.api allowin a terminal turns it on. -
tg <profile> watch --jsonlprints{"type":"item","data":…}lines and a final{"type":"end","complete":true}. Read each message or event fromdata, and stop at theendline. Fields are snake_case. A timeout or a normal stop ends withcomplete: true; a failure ends withcomplete: falseand its exit code. -
runs searchis nowsearch runs. Filters are terms in the query:status:failed,error_code:timeout,operation:messages.download,profile:work, next to plain words. Saved MCP requests use the new command path. -
statsreports take their filters as query terms.--message-kindismessage_kind:posts|comments|all,--min-messages 5ismin_messages:5,--min-viewsand--max-repliesaremin_views:andmax_replies:,--older-than 24hisolder_than:24h, and--chatischat:<chat>on the rankings and reports; exact words useexact:in place of--exact. Update saved commands and MCP requests. -
Options have one meaning each (cli-core 0.399.0). Use
--analysis-providerfor analysis and--embedding-providerfor vector search (conversations build|embed|related|status,search conversations),--consent-providerforconversations consents revoke,--claimfortags remove,--answer-modelforconversations links clear,--template-modefor reply templates and--text-fileforcontacts notes add|edit.inboxandreviewtakekind:group,channelin their query. The old spellings still work, hidden, for one release.
Fixed
-
Voice-note search no longer finds a different real English or Spanish word for the one you typed (cli-core 0.402.0). A misheard spelling still turns up: "budget" finds "budjet", but "cost" no longer finds "cast".
-
Downloading media skips service events and keyboards (cli-core 0.400.0). A chat with a group event or an inline keyboard no longer makes
attachments downloadfail withprovider.invalid-response.
0.83.0 — 23.10.2026
Added
-
tg <profile> messages press <chat> <message> <button>,chats start <bot>andchats app <bot>work with bots.messages shownow numbers the inline buttons under a bot's message;presspresses a callback button by its number or text. A button that asks for your 2FA password is refused, never pressed.chats startstarts a bot as its Start button does (--start <param>, or at.me/<bot>?start=link), andchats appprints the address of its mini app, which signs you in. -
The skill tells an agent to search again in other words before saying something is not there. A search finds the words it is given, and a paraphrase shares none with its answer.
-
tg <profile> chats archive|unarchive|pin|unpin|mark-unread|mute|unmute <chat>: your own chat list from the command line. Telegram's archive, pinned chats, the unread dot and notifications, withmute --until 2hfor a time and plainmutefor good. They change only your list; nobody in the chat is told, and repeating one is safe. -
Verified media backups.
attachments download <dir>archives available files across chats with size and SHA-256 manifests;attachments check <dir>verifies them offline.attachments jobsmanages opt-in Linux daily timers. Completed copies survive interrupted runs and message-store deletion; interrupted files restart.attachments move <dir> <archive-dir> --before-time <time>moves older images into another verified archive, retaining relocation records so checks follow the copies and later downloads do not duplicate them. -
tg <profile> review --offlinereads the local store (cli-core 0.398.0) instead of refusing. It shows only what was already synced and says so (missingin JSON, a warning on the terminal). -
The MCP server offers more commands, each limited by the profile's permissions (cli-core 0.398.0):
runs,store status|info|check|export|reindex,store jobs,attachments move,attachments jobs status,config show,commands schema,guide,skill show,doctor report, themodelslists,replies status|test|consents show,schedule list,server status|logs, and on the bot serverwebhooks,commands set|clear,chats leaveandchats admins. The MCP guide lists the few it leaves out, and why. -
Saved voice-note transcripts match word forms and spellings that speech recognition may have garbled.
text:searches written text only;exact:disables expansion for that word.
Changed — may break callers
-
tg <profile> setup --json: the command map isitem.commands, notitem.next. The envelope'snextis reserved for structured continuation steps, so the map of follow-up commands (instructions,inbox,chats,history,history_status, andskill,mcpwhen no agent skill was installed) moved toitem.commands; the values are unchanged. Login details stay underitem.session. What to do: readitem.commands.<name>where you readitem.next.<name>. -
MCP message deletion takes
message, chat export takeschat, and duplicate-task operations taketaskand, for a pair,other_task. Update saved MCP requests usingmessages,chatsordup. CLI positional arguments keep their order. -
Command discovery (
commandsandcommands schema) rejects--jsonl; use--jsonfor its single document.
Fixed
-
The docs and the skill say
search allalso asks Telegram. By default it sends the query's words to Telegram's own search too (--backend both);--offlineor--backend archivekeeps the query on your computer. README, usage, search and the skill said it read only this computer. -
Installation explains npm's install-script warnings. npm 11.17 also prints
not yet covered by allowScriptsfor@wirecat/tg-cliandbetter-sqlite3; both are harmless, and the guide says why. -
contacts prepareis in the people guide and the skill, and the comparison page covers tlgr and mcp-telegram, links the maintained tgcli and marks tgcli's several accounts. -
A pasted
--helpexample runs (cli-core 0.398.0): an account command's example names the profile (tg personal messages list Team) instead of failing with "name a profile". -
search all --helpsays it asks Telegram's server by default and names--offlineand--backend archiveto keep the query local (cli-core 0.398.0). -
Message-search commands no longer list or delete saved meeting searches.
-
Command corrections preserve the chosen profile; help shows concise descriptions and concrete examples.
0.82.0 — 23.10.2026
Added
tg <profile> contacts prepare <person>: what to know before talking to someone (cli-core 0.394.0). Whatcontacts contextgives, plus the one-to-one chats where their message is the newest the store holds, open tasks assigned to them, accepted facts about them and their projects, your notes about them, and their recent meetings — each with its reference, under one size budget, withprepare.coveragesaying what each section left out and why. Tasks of another Telegram account, and facts on a project bound to one, stay out.contacts.notes.list: denyleaves the notes out and says so;messages: denyrefuses the command, as it doescontacts context.- Message search reads
"a b"~N: the words at most N words apart in one message (cli-core 0.391.0). bot watch --public-url <url> [--port <n>]receives a bot's updates by webhook (cli-core 0.391.0).
Changed — may break callers
- Reads never mark chats read (cli-core 0.391.0).
messages list,inboxandreviewno longer take--mark-reador--no-mark-read, and thecatch_up_marks_readsetting is refused. Why: a command that only read sent the other person a read receipt. What to do: removecatch_up_marks_read; runtg <profile> chats mark-read <chat>when you mean to mark a chat read. - An unknown key under
permissionsrefuses messenger commands withconfiguration_error(cli-core 0.391.0), typos such asmessages.sednincluded. It was a warning, and the restriction did not hold. What to do: correct the key or remove it withconfig unset.
Fixed
- A local read with an unknown profile lists the profiles on this computer (cli-core 0.391.0), instead of suggesting to link a new account.
0.81.0 — 22.10.2026
Added
- JSON answers of commands with a date filter say how they read the date (cli-core 0.385.0):
meta.windowgives the bounds used, in UTC, andmeta.timezonenames the zone a date typed without one was read in. This coversstore export,messages sync,stats chats show,stats chats retention,contacts context,search conversations,replies test,runs search,stats messages unanswered,stats contacts responses,stats chats newcomers,stats messages discussion, and atime:ordate:term inchats events,chats members history,inboxandreview.
0.80.0 — 22.10.2026
Changed — may break callers
- A time typed without a zone is read in your zone, and a date alone means local midnight (cli-core 0.379.0).
This covers
messages send --at-time,chats link createandchats link update --expire-time,chats mute --untiland date-onlytime>=queries, such aschats events Valencia time>=2026-09-20. Before, some of them read a date alone as midnight UTC. A time withZor an offset is read as before, and JSON and MCP output still give every time in UTC withZ.
Fixed
-
stats chats retentionandchats stats showread--since-time/--until-timein their--timezone, and a date alone in retention's--until-timecovers that whole local day (cli-core 0.380.0).stats charts,contacts timelineand the MCPstatstool name the zone inmeta.timezoneand give the UTC window inmeta.window. -
The QR login line names the zone of its time: "valid until 22:00:00 Asia/Vladivostok". Before, it gave the computer's local time without saying so.
-
A frozen account's deletion date says it is a UTC date: "deletes it on 2026-10-03 (UTC)". The
untilfield is unchanged.
0.79.0 — 21.10.2026
Fixed
- An action Telegram keeps for Premium accounts now says so ("that needs Telegram Premium on this account").
Before, every such refusal, for example a reaction from a free account, said that Telegram transcribes only for
Premium.
messages transcribekeeps its own message about Premium and the free trial. - A locked or unreachable Linux keyring now warns and falls back to the credentials file (cli-base 0.47.5). The keyring is read through the Secret Service only; before, a failure could end in silent storage in kernel memory, which is gone after a logout or reboot.
0.78.0 — 21.10.2026
Changed — may break callers
- Markdown headings are refused when sending (cli-core parser). Send text now goes through cli-core's shared
Markdown parser, as
maxdoes. A line that starts with#used to go out as typed; it now fails with a validation error, because Telegram has no headings. Write the line in bold instead. Nothing else changes. - A message that sends you to another command names it with your profile: after a send or an edit with no answer
from Telegram, "check
tg personal chats list" replaces "checktg chats list", so it can be pasted as it stands. The words now come from cli-core. - Telegram's account and login refusals, a stopped watch and an unanswered write carry their own error
reasoninstead of the generic one for their code:login.revoked,login.duplicated,account.deactivated,account.banned,account.frozen,account.limited(wereauth.failedoraccess.denied),updates.stopped(wasprovider.unavailable) andwrite.unanswered(wasoutcome.unknown). Codes, exit codes and messages are unchanged. Under--debug, the record'scausenow gives the failure behind it, not only its code.
Fixed
- Search queries keep an
@that is followed by a letter inside a term. E-mail addresses without a dot after the@and chat ids no longer need quotes:email:[email protected]works as typed.
0.77.0 — 20.10.2026
Added
- The store keeps a chat's history (store version 25, cli-core 0.366.0). A change to a chat's id, title,
membership or search visibility is kept in
chat_revisionswith the old and new value; a read by the id a chat was re-keyed from finds the chat it became. The store moves to version 25 when first opened; nothing is sent.
Fixed
- A chat you left is found by any of its ids (cli-core 0.368.0) in
store export,store status,messages thread, a search's--chatandchat:, tags, tasks and the other reads of its kept history.chats trackandstore gaps planrefuse it: "you left chat ". tg guidelists memo's scenario under the same title as memo and the other tools: "One person across every tool", capitalised. On cli-core 0.370.0 the scenario check in the tests also catches shell characters left outside quotes in a step.
0.76.0 — 19.10.2026
Changed — may break callers
- Without a terminal, the login QR code is printed as text for an agent to paste into the chat;
--qr-fileis gone. An agent wrote a PNG and opened it in an image viewer, a window you can lose. Nowtg <profile> session start qrandsetupprint the code on stderr as plain text (half blocks, no colours, drawn for a dark terminal theme), then tell the agent to paste it as a code block, exactly as printed, and to paste a renewed one and say the old one expired. With--jsoneach code is also one stderr line,{"event":"qr","qr":{"text","expires_at","scan"}}. In a terminal the code is drawn as before.--qr-fileis removed fromsession startandsetup. Without a terminal a login still needs stored app keys and no 2FA, and is refused before it opens a browser; a phone login needs a terminal. Login stays off MCP: run the command (when an agent runs the login).
Added
store clear --leftnames the chats it deletes (cli-core 0.353.0): the refusal without--allow-dangerouslists the first 20,--dry-runlists them all, and the answer carries aleftlist (id,title,messages).
Fixed
- From cli-core 0.351.0–0.362.0:
chats leaveandchats joinupdate the store, andchats showfinds a chat you left; a sent message is saved in the chat Telegram answered; a re-keyed chat keeps the stricter privacy of its two halves; a chat hidden from search stays out of every search that does not name it; a failed scheduled run'slast.jsonkeeps an error code, never a chat title; the firstserveafter an upgrade re-keys chats in short passes instead of locking the store. messages forwardanswers, and saves, the forwarded copy in the chat it went to. It took the first new message in Telegram's answer, which can belong to another chat; now it takes the one its send id names, in the target chat. Creating a forum topic reads its first message the same way.
0.75.0 — 19.10.2026
Fixed
setup's login step is headed "Link this device" and no longer asks you to scan a QR code before one is drawn. The line under the code says where to scan; a narrow terminal shows only the hint to widen it.- A terminal too narrow for the QR code no longer asks you to scan it (cli-core 0.350.0).
session startandsetupsaid where to scan in Telegram before the code; when the code did not fit, only the hint to widen the terminal or pass--qr-filefollowed. Now the scan line comes after the drawn code or the--qr-filenote, and a narrow terminal shows only the hint. tg <profile> setup --helpshows the Global Options block again. 0.74.0 dropped it when the usage line gained<profile>.- Hints in errors and notes name the profile: "the store is behind this build —
tg personal store migrate" instead oftg store migrate, which failed with "name a profile" when copied.
Added
- A next step in
--jsonoutput and in an error carriesline, the whole command to type with the profile (cli-core 0.348.0):"line": "tg personal mcp config"beside"command": "mcp config". A copiedcommandalone failed with "name a profile".commandis unchanged, and MCP answers leavelineout.
0.74.0 — 19.10.2026
Added
tg guidelists scenarios: the commands for a common task, in order, and why each. Four ship with tg —catch-up,find-what-was-said,searchable-filesandagent-without-send— and the list points at memo'sperson-brieffor one person across every tool.tg guide <name> --jsongives one as data. CI checks that every step is a tg command whose options and arguments parse.- Every command's
--helpends with Returns, Next usually and Example (cli-core 0.345.0), anddocs/commands.mdcarries the same lines. The usage line showstg <profile> ….
Changed — may break callers
npm install -ginstalls the agent skill only when asked. It wrote the skill into~/.claude/skillsand~/.agents/skillsby default, and npm hides a lifecycle script's output, so nobody was told. NowTG_INSTALL_AGENT=all(or an agent's name) installs it at install time; otherwisetg <profile> setupoffers it, ortg skill install --for all. The Windows installer passesallitself and is unchanged.tg --helpand a baretgshow a short first screen (cli-core 0.344.0): what tg is for, eight things it does that a plain client would not, the other WireCat tools, and where to go next. The full commander help with every command and option is attg --help-all; the options alone attg help options. A script that looked for a command or a global option intg --helpmust read--help-all.tg commandswithout--jsonprints a text list, by section, even when piped: one line per command — usage, what it does,(writes)when it changes something. It printed the whole JSON document.--jsonand--jsonlprint the same document as before; a script that parsed a baretg commandsmust pass--json.- A chat's
provider_metadatasaysnullfor a flag that is off or a username that is gone:isBot,isForum,pinnedandusernamewere left out instead. cli-core's store will soon keep a key that is left out, so an unpinned chat or a dropped username would otherwise stay in the store, and@oldwould still find the chat. Every reader in tg and cli-core treatsnullas absent, but JSON output now shows these keys asnull: a script that tests whether the key is present sees it.
Security
- The QR login is cli-core's
loginQr, as in max and wa.--qr-fileis written as a temporary file created with mode0600and renamed over the path, instead of being written and then chmodded, and it is removed when the login is cut off by Ctrl+C, a cancel or--timeout, not only when it ends on its own. A terminal too narrow for the code draws nothing and says to widen it or pass--qr-file. Without a terminal,session startsays "shows a QR code to scan — run it in a terminal, or pass --qr-file ". - Under the read-only lock and on a readonly profile, a write refuses before connecting; refusals appear in
sends list(cli-core 0.343.0).
Fixed
inboxandreviewdeclare their output, sotg commands schema inboxgives the message summary's fields and--json=<fields>refuses a name they do not have instead of printing empty items (cli-core 0.345.0).
0.73.1 — 18.10.2026
Fixed
- tg starts a little faster. Built on cli-core 0.342.0 and cli-base 0.45.0: a command no longer parses the rule tables that only development checks use, which saved about 7–12 ms per start in the measurement.
0.73.0 — 18.10.2026
Added
- Agents get every command the profile's levels allow over
tg mcp(cli-core 0.341.0). The server offered hand-written tools; it now builds them from the commands themselves and runs them in this process, 188 commands in all,messages sync,contacts sync,mentions confirm,conversations embedandimages embedamong the new ones. What an agent may not do is decided by the profile's levels: set the area toreadonlyordeny. The full list is pinned incontracts/mcp-catalogue.json. tg conversations rebuildbuilds again the conversations of chats that changed and embeds them with the model on this machine; it never asks Telegram, downloads no model and sends no text anywhere. It replaces the agent-onlyconversations_refreshtool.
Changed — may break callers
tg mcptool arguments are the command's options in snake_case:chat,limit,query,sync_firstand so on. An agent that remembered the old names askstg_tools_searchagain.- An agent's
search messagestakes the query as text only; the structuredastinput is gone. - An agent cannot mark read or act as the owner:
--mark-readonmessages list,inboxandreviewand--as-ownerare not offered, thecatch_up_marks_readsetting does not apply to its runs, and its--newcheckpoints are its own. - Under
TG_READ_ONLY, local writes that delete or overwrite what you saved are refused (cli-core 0.336.0, 0.337.0):searches create,searches delete,searches clear,contacts alias set|rm,contacts notes add|edit|remove,contacts link|unlink,tags add|auto|remove,mentions confirm|reject,attachments text set,chats tracking add|remove,conversations links add|clear,conversations consents revokeandtasks reject, and their agent tools, exit 5. What the store rebuilds itself, syncs,serveand task bookkeeping still run. - While Telegram holds the account, no write goes out (cli-core 0.334.0): reactions, marking read, quiet pins,
title and profile changes are refused too; reads work. A ban with no end holds writes until
tg flood clearortg doctor --onlinefinds the account well (until: nullin JSON). - A send blocked on another process's lock exits 9 (
timeout), not 1 (cli-core 0.338.0); nothing was sent, so it is safe to retry.flood cleartoo. tg upgrade --offlineexits 2 (cli-core 0.338.0) instead of asking npm anyway.conversations build,conversations embedandsearch conversationssay they can send text out (cli-core 0.334.0, 0.336.0): with--analyze,--provideror a remote embedding model. UnderTG_READ_ONLYthey refuse before sending; a local model still works. They never run throughserve.
Fixed
tg mcpanswers every call it received before stdin closed instead of exiting with one still running.tg bot mcpdoes not yet.- An agent is not offered
offlineon a command that refuses it (cli-core 0.335.0):topics,chats events,chats inspect,chats members audit,chats members fetchand thechats folderscommands. - A held lock no longer stalls
tg serve(cli-core 0.340.0) for up to 5 seconds. - Two changes to the recipient list at once no longer undo each other (cli-core 0.338.0).
tg store gaps repair --backgroundruns its job instead of failing at once (cli-core 0.339.0).- Hints from
serverand store maintenance commands name the profile (cli-core 0.339.0). tg upgrade --checkruns underTG_READ_ONLY(cli-core 0.338.0).- Model downloads never go through
tg serve(cli-core 0.336.0). - A store that failed to open is closed (cli-core 0.332.0), so its folder can be deleted on Windows.
0.72.0 — 18.10.2026
Added
tg tasks agendalists what others owe you (cli-core 0.328.0): open tasks someone else does, oldest first, with their assignees, in an "assigned" section and inassignedin JSON.
Changed — may break callers
- A command path given as one argument fails (cli-core 0.328.0):
tg 'chats list' --helpprinted the root help and exited 0; it now fails with the command line to run. - An interactive command without a terminal waits 5 minutes by default, not 30 seconds (cli-core 0.328.0), so an
agent's
tg session start --qr-fileis not cut off before the code is scanned.--timeoutandTG_TIMEOUTstill decide when given. - Under
TG_READ_ONLY, a write that asks first stops with exit 5 before asking, not exit 7 (cli-core 0.329.0):messages delete,topics delete,account sessions end,chats deleteandchats clearsaid "asks before it acts", as if--allow-dangerouswould let them through. They now say "this process is read-only", as every other write does. Without the lock they ask as before.
Fixed
- Fewer false duplicate suggestions from reply chains (cli-core 0.331.0): a reply that asks for something new no longer marks two tasks as maybe the same.
tg chats list --json | headends quietly (cli-core 0.328.0), through a runningservetoo, instead of printing a stack trace when the reader stops.
Security
tg session endno longer logs out a runningtg serve(cli-core 0.328.0): withserverunning for the profile,session endwas handed toserveto run. It logged out the connectionservewas using and deleted the session fileservestill had open. Nowsession start,session endandsetupnever run throughserve, andsession endstops with exit 2 and says to runtg <profile> server stopfirst. UnderTG_READ_ONLYall three still stop with exit 5, now with "it cannot log in or out".
0.71.0 — 17.10.2026
Changed — may break callers
- In a group tagged
watch-tasks, any member's reply closes a question (cli-core 0.325.0): a direct reply from someone other than the asker settles it; a later message that does not reply closes nothing. tg <bot> bot mcptools are the bot commands themselves (cli-core 0.325.0): an agent's arguments are the command's own, in snake_case —messages sendandmessages edittakemdorhtmlin place offormat,messages deletetakesmessages(a list),search messagestakesquery,chats members removetakesperson. New:chats rules show, andofflineon every read. Sending files,--allow-dangerousandchats moderate --max-actionsstay with the owner. The catalogue is pinned incontracts/bot-catalogue.snap.
0.70.0 — 17.10.2026
Added
tg <profile> contacts link <person> me(cli-core 0.323.0): say that a contact is you — for an account of yours the store cannot match by itself, such aszoom:<id>.
Fixed
- Mentions find fewer wrong names (cli-core 0.323.0). A word of a contact's name counts on its own only as a first name or a surname; a contact named like a company («Smart Agents») is found only by the whole name, and the polite «Ваш», «Вам», «Вас» never count. A saint's name in a place («Saint Michael's Bridge») and a city after «в»/«во» («во Владимире») are not names either.
- Your own accounts are you (cli-core 0.323.0): an account's own identity is linked to you on its next sync, so your name in your messages is no longer someone else's.
- An address keeps its city (cli-core 0.323.0): the same street in two cities is two places; an address written without a city still matches its place on that street.
After updating, read old messages again once: tg <profile> mentions rebuild person-name place.
Security
TG_READ_ONLYnow stops logging in and out, and changes to the message store:session start,session endandsetuprefuse withpermission_errorbefore they connect, and so dostore reset,restore,clear,migrate,repair,copies deleteanddecrypt.session endused to log out and delete the session under the lock.
0.69.0 — 17.10.2026
Changed — may break scripts
- An agent can no longer delete for everyone (cli-core 0.321.0). The MCP
messages deletetakes nofor_everyone, and passing it is refused as an unknown argument; the owner still hastg <profile> messages delete --for-everyone. mcp --permissiononly tightens (cli-core 0.321.0). An override that would loosen the profile's level, such asmessages.send=allowon a read-only profile, is refused at startup with the key it names; to allow more, change the profile's permissions.--permission messages.send=denyand other narrowing overrides work as before.
Fixed
- An agent's deny on
chats send-asandchats members listnow applies (cli-core 0.321.0). Over MCP these commands read their levels from other keys, sochats.send-asandchats.members.listdid not reach them.
0.68.0 — 17.10.2026
Changed — may break scripts
- Tasks open only where something is asked of you (cli-core 0.318.0). In a one-to-one chat every question you did not answer opens one, as before; in a group only a question in reply to your message and a mention of you; in a channel or Saved Messages nothing. On the owner's store, 300 posts of one channel would have opened 85.
tasks applyis nowtasks scan(cli-core 0.320.0); MCPtasks_scan, permission keytasks.scan.- No setting picks a profile any more (cli-core 0.319.0). A command names its profile with the first word or
TG_PROFILE. A config file that still hasdefault_profilestops a command that names no profile, with the profile to type andtg config unset default_profile;tg config set default_profileis refused. A profile calleddefaultis an ordinary name:tg default mcp confignames its servertg-default, nottg.
What's new
- Tasks have assignees (cli-core 0.320.0):
tasks addandtasks plantake--assignee sender(whoever sent the message) or--assignee person:<id>;noneclears it.tasks list "assignee:any state:open"is what others owe you. tg <profile> tags add --chat <group> watch-tasksrecords every question in that group as a task, whoever it is for.
Fixed
tg upgrade's "held back" hint names the package and keeps pnpm's release-age exemption (cli-core 0.320.0).
0.67.0 — 17.10.2026
Security
-
Internal attachment references stay out of JSON, JSON lines, MCP and live-event output (Core0.315.0); provider media keys and credentials remain inside the client.
-
WhatsApp state files cannot be uploaded as attachments (Core 0.314.0), including configured state paths and symbolic links. Ordinary neighbouring files remain allowed.
0.66.0 — 17.10.2026
Changed — may break scripts
- The first sync opens no task from history (cli-core 0.309.0). After an account's first sync, the task rules
open at most
task_first_pass_per_chattasks per chat, and the default is 0. The sync answer'staskscounts what it held back (held,held_chats), and a note namestasks apply. Later syncs still open tasks from new messages.tg <profile> config set task_first_pass_per_chat 50brings back the old behaviour.
What's new
-
tg <profile> tasks apply <chat...>(cli-core 0.309.0): the task rules over a chat's newest stored messages (--last, 50 by default), for a chat whose history you want as tasks. It lists what would open and changes nothing unless--yes. Local store only. MCP:tasks_apply. -
Mentions find street addresses, and names of people the store does not know yet (cli-core 0.308.0).
tg <profile> mentions placeslists confirmed addresses across every account. The store moves to version 18, with aplacestable, the first time a command opens it.
Fixed
tg upgradethrough pnpm installs the newest version (cli-base 0.40.2). pnpm 11 installs only versions a day old, so the upgrade could install an oldertgthan the one you had. It now exempts@wirecat/*from that wait; every other package keeps it.mentionshelp summaries fit the shared 80-character limit (cli-core 0.311.0).- The duplicate check compares tasks by when their messages were sent (cli-core 0.310.0), not by when a task was written. Tasks written from history in one go no longer all look alike.
- Old messages fetched into a quiet chat open no tasks (cli-core 0.309.0): a sync pass skips a chat with nothing sent since the last one.
- No
[client] cannot reach Telegramlines while tg cannot connect. 0.64.0 began printing each of mtcute's background errors as one line; while the network is down, that is one line per connection attempt. They show only with--verbosenow. A request that fails still reports its own error.
0.65.0 — 17.10.2026
What's new
- A closed task's card shows the task that follows it up (cli-core 0.305.0).
tasks showprintstask:<id> follow-up-of this task, and--jsonand MCP returnlinked_from. Before, only the new task named the closed one.
Changed — may break scripts
- The daily "a newer version exists" line also stays quiet for
--json=…,--timeout=…and the other quiet options written with=(cli-core 0.307.0). Before, only the bare option silenced it. tg now takes this notice from cli-core, shared with max and memo.
Fixed
-
tg setup --app autoreads the app keys from the redesigned my.telegram.org. The site now shows the api_hash as dots and keeps its value in the page's copy and show buttons, so 0.64.0 stopped with "could not read its keys". The keys are read from there now (checked on the real page), a create counts as done when the site answers OK, and the site's own error text is shown instead of its JSON. -
A broken config file is named in a short error (cli-core 0.304.0): the first bad key, never its value.
0.64.0 — 16.10.2026
What's new
-
Imported Drive documents retain their Google URL and edit time in shared search (cli-core 0.301.0).
--source drive:<profile>selects a registered Drive profile; chat document lists can show the imported title after Drive sync links the stored messages. -
The MCP server loads only when MCP is served (cli-core 0.300.0), so other commands start with about a tenth fewer files to load.
Fixed
-
tg setup --app autono longer tries to create a second app when the account already has one. It read the app's keys only from one exact page layout; when my.telegram.org showed the app's page in another shape, it took the account for one with no app and asked the site to create another (Telegram allows one per number). Keys are now read from the page's text, and an app page whose keys cannot be read stops with "use--app browser". An error from the site no longer quotes a whole page — which could hold the app'sapi_hash— only its title. The hint after a failed app step names the command that was run (tg <profile> setup --app browser), and too many tries at the site's code israte_limited. -
A login with a 2FA password no longer prints mtcute's "unhandled error: ConnectionClosedError" stack. When a login succeeds, mtcute replaces its connections on purpose. The old connection then reported itself closed, and with no listener mtcute printed that as a red stack trace, with the account id, right after the hidden password prompt. tg now listens for these background errors: the expected close shows only with
--verbose, and any other appears as one line in tg's own words. -
bin/releaserestarts itself once when the release brings a newerbin/release: folding the changelog and raising the version both fast-forwardmain, and the shell went on reading the old script from the byte it had reached, so the rest of the run was a mix of old and new text. It now starts the new script over with the same arguments; a second change during that run stops it withrun it again. The restart also works whenbin/releasewas started from another folder by a relative path. Only the repository's own release is affected; the published package does not change.
0.63.0 — 16.10.2026
What's new
messages deletetakes message ids separated by commas as well as spaces (cli-core 0.299.0).- tg starts about a fifth faster after its first run. It keeps Node's compiled code in a cache, in the
system's temporary folder (
NODE_COMPILE_CACHEmoves it):tg --helpwent from about 0.60 to 0.49 seconds. - The task category list lives in one file tg, MAX and memo share (cli-core 0.298.0):
~/.config/WireCat/config.json, sectiontask_categories. It holds only your changes to the default list:"garden": "plants | seedling, es:planta"adds or replaces a category,"religion": nulldrops a default one, and categories a later release adds still arrive.tasks categories(MCPtasks_categories) names the file infile, andconfig showmarks the categories that come from it. A file that is not valid JSON or names a bad category is refused with its path. A store moved byMESSAGING_STOREreads theconfig.jsonbeside it;WIRECAT_CONFIG_DIRmoves the file.
Changed — may break scripts
config set task_categories.<name>andconfig unset task_categories.<name>now write~/.config/WireCat/config.jsoninstead of the store, keeping the file's other sections;config unset task_categoriesdrops the section. A list that an older tg saved in the store moves into the file on the nextconfig setorunsetof a category; until then the store's list still applies. Older tg builds do not read the file.
0.62.0 — 16.10.2026
What's new
- An agent's close can wait for you (cli-core 0.295.0):
tasks closerun by an AI agent (AI_AGENTorCLAUDECODEset) states its certainty with--certainty <0..1>. Below the store's threshold (config set task_agent_close_min, 0.8 by default), or withconfig set task_agent_close off, the task stays open with a close suggestion;tasks list close:suggestedandtasks agendashow it. Confirm it withtasks close <task>or refuse it with the newtasks reject <task>.--as-ownercloses as you. - A new task about a task closed in the last 14 days opens as its follow-up, linked
follow-up-ofthe closed one, instead of being refused as a duplicate. It is still refused while an open task may be the same job. tasks categoriesnames categories that left the list while tasks still carry them, with open and total counts (unlisted);tasks agendalists the ones open tasks carry (unlisted_categories).
Changed — may break scripts
- An agent's
tasks closemust pass--certainty(MCPtasks_close: the requiredcertainty), or it fails withtask.certainty-required. Below the threshold the answer hasstate: openandclose_suggestionset instead of a closed task. A script run from an agent's terminal that closes tasks needs--certainty, or--as-ownerwhen the owner asked for the close. tasks addmay now refuse a task whose message shares words with an open task's message (exit code 2,task.duplicate-candidates): the duplicate check also reads a task's source message and its newest linked messages, so a rule's task with an empty title is compared by its message. Repeat with--into <task>or--new.- 59 default task categories instead of 7, such as
bills,health,travel,fitnessandsubscriptions;tasks categoriesprints each with its meaning and trigger words. The old seven keep their names, so stored tasks stay valid, but a rule now picks the narrower name: a utility bill isbills, notmoney. A filter such ascategory:personaltherefore catches fewer new tasks. A store that saved its own list keeps it;config unset task_categoriestakes the new default. A list holds up to 80 categories.
Fixed
- Spanish task text is read better: a rule's category matches other forms of a Spanish trigger word
(
pagueshitspagar), and the duplicate check reads Spanish due dates such asmañanaorel viernes.
0.61.0 — 16.10.2026
Changed — may break scripts
tg mcpandtg bot mcpno longer take the retired access flags--allow-send,--allow-mark-read,--allow-delete,--allow-moderate,--confirm-send,--allow-dangerousand--http-confirmation(cli-core 0.292.0). An app entry that still passes one stops starting with "unknown option": remove the flag; the profile's permissions decide, as they already did.
Fixed
-
Release scripts report observed lock holders separately from stale release labels. Shared diagnostics no longer attribute a live lock to a previous run; wait for the holders to finish, then retry.
-
A login that fails while opening no longer leaves the Telegram client open: when loading the logged-in user fails, the adapter closes the client and the session file before the error reaches the command.
0.60.0 — 15.10.2026
Changed — may break scripts
- Task and server commands take the shared vocabulary's names, with no alias (cli-core 0.288.0, cli-base 0.33.0):
tasks similar→tasks related;tasks duplicates unsure→tasks duplicates defer(permission keytasks.duplicates.defer; the stored decision is stillunsure);tasks add --attach→--into;tasks claim --for→--lease;tasks agenda --due→--due-within;server logs --lines→--limit(-nstays). The MCP tools follow:tasks_related,tasks_duplicates_defer,into,lease,due_within. tasks agendaandtasks duplicatesfilter with query fields, not flags:tasks agenda --tag <name>→tag:<name>,--category <name>→category:<name>,--claimed→claimed:any;tasks duplicates --unsure→decision:unsure. Over MCP,tasks_agendaandtasks_duplicatestakequeryinstead.
0.59.0 — 15.10.2026
Changed — may break scripts
- Flags take the shared vocabulary's names, with no alias (cli-core 0.287.0):
chats members audit|fetch --budget→--max-pages;messages sync --estimate→--dry-run;contacts context --refresh,bot contacts show --refreshandtags auto --refresh-metadata→--sync-first;search conversations --refresh→--catch-up;attachments show --if-sha256→--expected-fingerprint;replies edit --chats|--not-chats|--people|--not-people→--allow-chats|--deny-chats|--allow-people|--deny-people;schedule agent|command --once→--at-time;bot chats moderate --no-ban→--no-block;chats mark-read --until→--until-id;tasks add|plan --check→--remind-time;store export --to→--output-dirand--kind→--include;bot store fetch --from→--until-id. The MCP tools' inputs follow:max_pages,until_id,expected_fingerprint,sync_first,remind_time.
0.58.0 — 15.10.2026
What's new
- Tasks that may be one job (cli-core 0.285.0):
tasks similar <task>scores the tasks that may be the same job;tasks duplicates [--unsure]lists the pairs the rules found,tasks merge <task> --into <other>joins them andtasks unmergeundoes it;tasks duplicates reject|unsuredecides a pair.tasks agendatakes--categoryand--tag, andconfig set task_categories.<name>edits the category list for the whole store. - Mentions (cli-core 0.285.0):
mentions domainslists the sites links point to;mentions list --newshows what was found since the last look;mentions confirm|reject <id> --all-in-chatdecides a name in the whole chat; at.melink names its chat or person.config set phone_countries es,rureads numbers written without+. - Store version 16: the mention rules also read the text of notes and stored documents, and one
mentions rebuildreads the ones stored before;mentions liststill lists mentions in messages only. The upgrade adds triggers only, so an older tg still opens the store.
Changed — may break scripts
tasks addrefuses a task that may be the same job as an open task, or one closed in the last 14 days (cli-core 0.285.0): exit 2, reasontask.duplicate-candidates, with the candidates indetails.candidates. Repeat with--attach <task>to link the message to that task, or--newto open it anyway; the same holds fortasks addover MCP.phone:andvalue:also match a stored number that ends with the typed number's national digits (8 or more; cli-core 0.285.0), so a number saved beforephone_countriesis found either way. A Russian landline written in groups,(812) 000-00-01, is now stored as+78120000001, not the bare digits.- tg no longer searches mail (cli-core 0.285.0, cli-core#1121):
tg search mailand the MCPsearch_mailare gone, andsearch allreads messages and notes but never mail;--only mailis refused.tg search mail …answersmail is memo's: install @wirecat/cli-memo, then `memo search mail …`.search notes, tasks, notes and tags stay.
Fixed
- A title with Cyrillic capitals is found by a lowercase query (cli-core 0.285.0).
- A hostile HTML attachment no longer stalls the reader (cli-core 0.285.0): a page of unclosed tags or comments is read in time linear in its size.
0.57.0 — 15.10.2026
Changed — may break scripts
bot api --allow-any-filesits onbot apiitself, not on each operation that takes files: put it once, before or after the method name, and every@pathfield of the call may come from a protected place. Without it,@pathfiles from credential places,tg's own folders and the local store are still refused before connecting.tasks addneeds--category <name>(cli-core 0.282.0): money, documents, meeting, delivery, access, personal or other;tasks categorieslists them. Tasks get readable keys such asQ-15, andtasks claim/tasks releasehold a task for one agent session.permissionsis the only access setting (cli-core 0.282.0): a config file that still holdsread_onlyorallowis refused as an unknown setting, andconfig migrateis gone. Settings are read only under their snake_case names;config setno longer accepts camelCase names.- One search language (cli-core 0.281.0):
--languageand--regexare gone fromsearch messagesandsearches create; write a Lucene regex such asbody:/.*invoice.*/instead.conversations embed --workersis gone. A search saved in the old language is refused when replayed: save it again. - No folder move at start: folders left in
~/Libraryby a release before the WireCat folder are no longer moved.
What's new
messages syncopens tasks from what it stored (cli-core 0.282.0): a question nobody answered, a mention of you; closed once you answer.- A title match comes first in
search notesandsearch all(cli-core 0.281.0).
Fixed
- The update notice names
tg upgradeand stays quiet only whileupgraderuns (cli-base 0.29.0), sotasks updateno longer silences it. - Nested
--jsonfield paths work through lists (cli-base 0.31.1, cli-core 0.283.0).
0.56.0 — 14.10.2026
Changed — may break scripts
store exportwrites files in the shape it prints (cli-core 0.276.0):--outputfiles and--tofolders hold the same items as the screen (chat_id,sender_name,ref…). A folder from an earlier version is refused with "export into a new folder".bot apirefuses@pathfiles from protected places: known credential files and folders,tg's own folders and the local store are refused before connecting, asbot messages send --filedoes;--allow-any-fileon an operation that takes files sends one anyway. A file over 256 MiB is refused instead of read into memory.
What's new
config setandconfig unsetaccept camelCase setting names (cli-core 0.279.0):tg <profile> config set senderColors falseis saved assender_colors, the same as the snake_case spelling.- Resumable syncs (cli-core 0.276.0): a sync that is killed keeps what it saved, and the next run continues from there.
Fixed
- A send Telegram refused for flooding says it may be repeated: when
messages send,messages forwardorpolls createget FLOOD_WAIT before Telegram took the message, the error'sretry.safeistruewithafter_ms. Once Telegram took it — a lookup after the send hit the limit —retry.safestaysfalse.
0.55.0 — 14.10.2026
What's new
- Files go up from disk as they upload (cli-core 0.272.0).
messages send --file,--photo,--voice, the profile photo andtg botno longer read the whole file into memory first, and the refusal for files of 2 GiB or more is gone: Telegram's own limit applies.
Changed — may break scripts
- An unheard voice message is named in
missing(cli-core 0.274.0):review,inboxandmessages listadd{field: "transcript", step: "messages.transcribe"}for each voice message with no kept transcript, so an answer whose only content is a voice message no longer reads as complete. tasks link <task> task:<id>records a relation between two tasks (cli-core 0.274.0), with--kind blocked-by,follow-up-oforrelated-to.- A next step to a command that only changes this machine is never run unasked (cli-core 0.273.0):
server restartandstore reindexsteps carrysafe_to_auto_execute: false. mentions rebuildtakes its kind as an argument:tg <profile> mentions rebuild person-name, not--kind(cli-core 0.272.0).
0.54.0 — 14.10.2026
What's new
-
tg images embed: find pictures by what they show (cli-core 0.268.0). Off untiltg <profile> config set picture_search true; download the model once withtg <profile> models image download clip-b32(about 155 MB), thentg <profile> images embed [--chat] [--limit].search messagesthen returns apictureslist beside its hits. Picture queries must be English. -
tg mentions: phones, e-mail, links and Google documents found in stored messages (cli-core 0.264.0, store version 7).mentions list kind:phone,mentions list domain:google.com; a bare word is a value written any way, so89001234567finds+79001234567.mentions show <id>gives the text around one. Messages stored before this version need onetg <profile> mentions rebuild; new ones are read as they are stored. -
Mentions in a message's files and voice notes (cli-core 0.269.0, store version 10). The text
attachments extractread and a voice note's transcript yield mentions too, withfieldfile_textortranscript. Attachments with text from before version 10 need onetg <profile> mentions rebuild, which now also countsattachments. -
tg mentions confirm <id> [person:<uid>|organization:<id>]andmentions reject <id>decide who owns a phone or an address, or dismiss it for good. An organization can own a phone or address apart from any person (store version 11; older builds keep working). -
phone:,email:,url:anddomain:in a message search find messages by what their text mentions:phone:"8 900 000-00-01",email:"[email protected]",domain:docs.google.com. Mail has no mentions yet. -
A failing schedule is said before every other command with one stderr line, until the next run succeeds;
schedule listshows the streak.
Changed — may break scripts
contacts timelinepages like every other list: a list cut at--limitanswerspage.has_more: true,page.cursorand apage.nextstep (--cursorcontinues);meta.truncatedstays for changes still queued. The stderr "cut at --limit" note is gone.- Built on
@wirecat/cli-core0.269.0 and@wirecat/cli-base0.27.2. - Every answer is an envelope with snake_case keys. A list is
{items, page: {limit, has_more, cursor?}, next?, missing?, meta}, one thing{item, next?, missing?, meta};meta.run_idnames the run. This covers every command: messages, chats, contacts, writes ({item: {operation_id, send_id, message}}), inbox, review, search, stats, store, account, doctor, config, runs,upgrade,bot *, and tg's ownsession start|endandsetup(app_keys,already_logged_in,chats.has_more). What to run next is anextstep in place of fields such asnextBeforeId,nextOffset,nextCursorandhasMore. MCP answers are the same envelopes, and MCP tools refuse arguments they do not take. - Lists take a query, not filter flags.
chats list kind:group unread_count>0,chats events "Hiking" time>=7d,messages list "Book club" id<4242,contacts list notes:<text>,attachments list chat:<id> is:needs_text,store jobs list state:failed,inbox date>2h,review date>3d chat:<id>,search messages 'chat:"Book club" lease'.--search,--kind,--unread,--type,--since-time,--before-id,--after-id,--before-time,--after-time,--topic,--search-notes,--min-score,--revoked,--link,--answer,--needs-text,--state, review's--chatand search's--chatare gone from those commands.messages evidenceandchats mediacontinue with--cursorfrompage.next.contacts list name:needs stored contacts. doctor's Telegram block is snake_case:app_credentials,keyring_moved_by_environment,proxy.bot_api.- Error details are snake_case:
provider_error(wasproviderError), a group that became a supergroup saysmigrated_chat_idin the Bot API refusal, a forum upgrade that may have happened saysprevious_chat_idandchat_id. - Config file settings are snake_case (
keep_runs_for_days,sends_per_hour,read_only,default_profile, …). An existing file moves by itself on its first read. - Run logs are snake_case (
duration_ms,error_code,error_class,provider_error); runs written before are still read. - Statistics reports refuse
--jsonl: a report is one object.stats chats shownames its chat as achat:reference;stats tasks showanswers one item withopenandrows. --json=<fields>replaces--fieldsand--agent-json, which are gone.--json=id,textkeeps those fields of each item. CLI JSON keeps message text as written; MCP answers still show invisible characters.tags list,tasks listandconversations listtake a query instead of filter flags.tags list tag:work type:chat,tags list sources:auto;tasks list state:open kind:promise chat:<id>;conversations list <chat> started_at>=7d.--tag,--type,--source,--state,--chat,--before-timeand--since-timeon these lists are gone. Items are the shared entities: a tag names what it is on astarget, a conversation saysmessages_count,started_at,first_message.- Run records keep only listed attribute keys. A message id under
ids.messageis dropped for now, soruns search <message id>does not find it (reported to cli-core).
Fixed
- MCP prompts name only arguments the tools take.
reviewpasses its window asquery(date>"…"). tg <profile> bot messages deletetakes more than 100 messages. It sent every id in one call, and Telegram takes at most 100, so a longer list failed. It now sends them 100 at a time; if a later call fails, the error says how many were already deleted.
0.53.0 — 14.10.2026
Changed — may break scripts
- Built on
@wirecat/cli-core0.262.0 and@wirecat/cli-base0.26.0.@wirecat/cli-coreis the new name of@wirecat/cli-messaging; its 0.262.0 follows 0.261.0. The parity command iscli-core-parity. Machine output keys are snake_case:error.detailssaysoperation_id,send_id,retry_after_ms;commands --jsonsaysglobal_options,inherited_options,exit_codes,takes_valueandcontract: 1. A query tree in the MCPastargument haslower_inclusive,upper_inclusiveandmust_not. - HTML files are read as their main text (cli-core 0.262.0): menus, footers and banners are dropped, headings,
lists, tables and links kept. HTML attachment text already stored is read again on the next
attachments extract, and it changes.title:,site:,lang:,author:andkeyword:search notes and files.
Fixed
tg config set defaultProfile <name>andconfig unset defaultProfilework without naming a profile. They asked for one first and failed when several existed (cli-core 0.262.0).tg default mcp configandmcp installname the profile. The entry left out a profile nameddefault, so its MCP server stopped on its first call, since tg no longer assumes a profile (cli-messaging 0.260.0).
0.52.0 — 13.10.2026
What's new
- Built on cli-messaging 0.259.0 and cli-base 0.24.0.
store fetchis nowmessages sync(same arguments, options and JSON).store fetchstill runs as a hidden, deprecated name; the docs and the skill usemessages sync.bot store fetchkeeps its name. --debug: on a failure, the whole record — cause and stack — follows the error: after the✗line in a terminal, as a second JSON line otherwise.runs listandruns searchread a per-day index, so they answer in milliseconds on thousands of runs.
Fixed
- The skill warns about three mistakes an agent made while testing. It compared a plain word in one tool with
content:in another, readrefwhere a search answerslocator(oritemswhere notes answerhits), and reported a bug fixed in a newer version; a zsh loop over$cpassed a command path as one argument.
Changed — may break scripts
- The local store and the speech models move once into the WireCat folder,
~/.local/share/WireCat/(Windows:%LOCALAPPDATA%\WireCat\Data\), on the first start, from~/.local/share/cli-messaging/and~/.cache/cli-common/models/. The move never overwrites: if both places hold a different store,tgstops with exit code3and names both files.WIRECAT_STATE_DIRreplacesCLI_COMMON_CACHE_DIRand moves the whole folder. Upgrademaxandmemotogether withtg: an older one would create a new store in the old place. Where tg keeps its files. - One error object:
{"error":{"code","reason","message","details"}}. What used to sit at the top oferror—candidates,sendId,operationId,permission,retryAfterMs— is now inerror.details.reasonis a dotted id (output_limit→output.too-large,input_limit→input.too-large);retryableappears only where the failure sets it, andactionsonly on the failed items of a partial result. Exit code1isinternal_error(wasgeneric_failure), and its message no longer carries the fault's own text;--debugshows it. runs showlists only what went wrong (failed responses, warnings, the crash) and addseventCount;-vshows every event, as before.tgnever picks a profile for you. A command that uses an account and names no profile (no first word, noTG_PROFILE, nodefaultProfilein the config file) stops with exit code2instead of usingdefault, also whendefaultis the only profile. This breaks every existing one-profile setup:tg chats listnow fails. The error lists the profiles here, so the fix is in the message:tg default chats list,export TG_PROFILE=default, or"defaultProfile": "default"in the config file. On a new computer the first login istg personal setup(any name).--help,--version,commands,skill show,account listandconfig showstill run without a profile. MCP clients and scheduled jobs that starttg mcportg servewithout a profile need one added. A bot'sstore fetchuses only its own profile's app credentials and personal session, neverdefault's.
0.51.0 — 12.10.2026
What's new
-
--briefand--fullon every command.--briefkeeps a found message's reference, chat, time, sender, excerpt and score;--fullkeeps everything. -
tg search allnames who wrote each hit and how it was found (by words or by meaning). -
tg schedule: run a command or an agent on a timer, through systemd (Linux), launchd (macOS) or Task Scheduler (Windows).tg schedule command <name> --every 2h -- messages list <chat>runs a tg command; a read saves what it reads.tg schedule agent <name> claude "<prompt>" --at 08:30starts an agent (claude or codex), at most hourly. The agent runs withTG_READ_ONLY=1and cannot send; its answer is kept aslatest.mdbeside the schedule and a desktop notification says it is ready.--once 2hruns once and then removes the schedule.tg schedule list,runandremove. -
tg server installsuggests the command for a daily follow-up review, and turns nothing on. -
TG_READ_ONLY=1refuses every write of the process, above the config file and--permission.
Changed — may break scripts
tg search messagesanswers an excerpt, not the whole text. Each hit carriesexcerpt, about 240 characters around the first query word, instead oftext;--fullortg messages show <ref>gives the whole message. NulleditedAt,replyTo,forwardedFromandreactionsare left out of machine output. A script that readtextfrom search hits readsexcerptor adds--full.
0.50.0 — 11.10.2026
What's new
- Tasks get a plan, links and a daily agenda (shared store 0.247.0, version 4).
tg tasks addtakes--title,--description,--dueand--check;tg tasks plan <task>changes them later,noneclearing a date. The next check is when an agent should look at the task again, not a reminder: nothing reaches the owner.tg tasks linklinks a task to messages, chats, people, documents and URLs;tg tasks showprints the plan with its links.tg tasks agendalists, without one message's text, the tasks overdue or due soon, the chats owed an answer (owed), those waiting on others (waiting) and those whose newest message is not stored (unsynced).tg skill show follow-upsis the daily routine for an agent: drafts only, it never sends.
Changed — may break scripts
- Shared store 0.247.0: a meeting context records facts with
fact.add;memory.addno longer takes the kindfact.
Fixed
- Pin shared package 0.248.0, which includes the task follow-up parity entries. Release checks now recognize task plans, links, cards, agenda and their options.
0.49.0 — 11.10.2026
What's new
- Search takes the colon spelling of a comparison.
date:>=2026-01-01(and:>,:<,:<=) is the same asdate>=2026-01-01; before, it failed withinvalid_syntax. A refusedafter:orbefore:now names its replacement:after:2026-09-01says to usedate>=2026-09-01.
Changed — may break scripts
- Shared store 0.246.0 checks new labels against canonical names and aliases before creation. Similar names require owner review; reuse an existing label or its explicit alias. Existing labels and data remain, and canonical/alias automatic matches share one claim.
0.48.1 — 11.10.2026
What's new
- Shared store 0.242.0: existing project and task ids stay; new projects get short keys, and the store can check which tasks depend on which.
Fixed
- npm installs the packages side by side again. Built on
@wirecat/cli-messaging0.241.0, whose@wirecat/cli-meetings0.4.2 accepts cli-core 0.20.0. With 0.240.0, npm put cli-messaging in a nested folder with a second copy of cli-core.
0.48.0 — 11.10.2026
What's new
--sourcetakes a list of accounts and groups insearch messages,search mailandsearch conversations:--source group:work,tg:mila,email:[email protected]searches exactly those. An entry is a group,app:account(a profile of any app —max:defaultworks from tg — the account's id or its name) or a bare--sourceword.config set accountGroups.<name> <list>saves a group for every app.- The shared store upgrades to version 2 the first time tg opens it. Facts — what was said, asked, decided or
promised — get their own table beside memories; memories saved as kind
factmove there, and task assignments are copied into their own table. An older tg, max or memo still opens the upgraded store.
Changed — may break scripts
- On macOS tg keeps its files where it does on Linux:
~/.config/tg-cli,~/.local/share/tg-cliand~/.cache/tg-cliinstead of~/Library/…. The first run moves the old folders there, with the shared store and the speech models, and points an installedtg serveragent at its new log. While atg serveor MCP server is running it prints one warning, keeps using the old folders for that run and tries again next time. Linux and Windows are unchanged. - Purging an account also removes the people only that account had seen. A person stays while another account, a tag, a note or any other record points at them.
- Mail is searched by meaning thread by thread. The first index pass after the upgrade cuts every thread again and embeds the mail once more; search by words is unchanged.
Fixed
- Purging an account that held meetings no longer fails, and a purge drops the vectors only it used.
- On
@wirecat/cli-messaging0.238.0.
0.47.0 — 11.10.2026
What's new
messages list --limitreturns as many messages as asked for. Telegram hands out at most 100 a request, and--limit 500used to stop at 100 withhasMore: true; it now reads on page by page (cli-messaging 0.235.0).- A poll in
messages listcarries its question, answers and total votes underproviderMetadata.poll, so a channel's polls read without onepolls showper message.
Fixed
messages comments --limit 100(or more) says when older comments remain. It asked Telegram for one comment more than the limit to find out, but Telegram returns at most 100, so a thread of 1,600 comments answered 100 withhasMore: false. It now asks for at most 100 and reads a full page as more to come.polls showgives a poll's total votes before you vote. Telegram sends the total either way; only each answer's count waits for your vote. The total used to benulltoo.- On
@wirecat/cli-messaging0.235.0.
0.46.3 — 11.10.2026
Changed — may break scripts
- Joining a chat and importing contacts count toward
sendsPerHour. A join counts as one, an import as one per number;tg contacts importsends 10 numbers a request. When the limit stops an import part way, the error says how many numbers went and that importing again is safe.
What's new
tg bot watchprints and keeps an update once, even when Telegram delivers it again after a restart: each update is recorded by itsupdate_idand skipped once handled. With--events --jsonl, each line carriesupdate: { id, kind }.tg search all --backend archive|server|bothand--server-time, as onsearch messages; they apply to messages only, mail and notes are always searched locally. The default isboth.tg search mail --account <address>searches one mailbox; without it, every mailbox. Mail is also searched by recipient, folder and subject (to:,cc:,bcc:,mailbox:,subject:), and attachments by meaning.
Fixed
tg store fetch --allwaits out a short FLOOD_WAIT on the chat list (up to 5 minutes, as message pages already did) instead of failing at once withrate_limited; a 21 s wait ended every fetch of an empty store. Shipped in 0.46.2, not listed there.- Paging through the chats (
store fetch --alllists them 100 at a time) reads each dialog from Telegram once. Each page used to walk every dialog from the top again, so about 1,400 chats cost over 100 requests back to back instead of about 15. chats members list --allwaits 1 s between pages of 200 members. It used to ask for up to 50 pages back to back, although the limits page said it was paced.
Security
- Search no longer answers another account's messages.
search messages --backend serverwith--source allorin:allcould return another account's message with the same chat and message ids, and a chat id without its account matched that chat in every account; both are fixed. - On
@wirecat/cli-messaging0.233.0.
0.46.2 — 11.10.2026
Fixed
- Archive discovery now handles permission questions such as “Can contractors access production?” without treating the final question mark as a wildcard. Strict search and filters keep their behavior.
- Mail searches and linked-person context also read dedicated mail storage, alongside older imports. Mail supports sender and thread filters; search results list each email locator once.
- Background history fetches no longer stop at the default 30-second deadline; an explicit
--timeoutstill applies.
Changed — may break scripts
- A permanent history-fetch failure before the first saved page now exits with an error instead
of exit code
0with anissue. Bot history without a starting message exits with code2and requests--from. Failures after progress still report partial results.
0.46.1 — 11.10.2026
Fixed
- Package references, documentation and fixtures use the WireCat namespace throughout.
Changed — may break scripts
- Independent file or history-page failures retain successful work and return
complete: false,batchorissuewith exit code0. Scripts must check completeness; partial download JSONL addsbatch_summary. Errors include recoveryactions. Resuming downloads retries failed checkpoint IDs. - Batches stop new requests after ten attempts when failures exceed 50%;
MESSAGING_BATCH_MAX_ERROR_PERCENTadjusts the percentage, with 100 disabling that percentage stop. Throttling and authentication failures stop earlier; writes with unknown outcomes are never automatically replayed.
What's new
- Set extraction and retained-file transfer size through
MESSAGING_ATTACHMENT_MAX_MIB(default 50). PDF previews now allow 4000 pixels per side and 8 MiB per page;MESSAGING_PDF_PREVIEW_MAX_PIXELSandMESSAGING_PDF_PREVIEW_MAX_MIBadjust those budgets. Larger values need more memory; external OCR and decompression budgets remain separate. tg runs search, also theruns searchcommand in MCPtg_read, searches safe diagnostic records by text, status, error code and time without connecting to Telegram.
0.46.0 — 11.10.2026
Changed — may break scripts
- The store prunes its growing logs on open, at most once a day: agent tool calls older than 90 days are deleted, and a handled bot update older than 30 days keeps its row but loses its payload. Upgrade max-cli and cli-memo at the same time, as they share the store.
What's new
tg store resetfor a store this build cannot migrate: it backs the store up beside itself, deletes it and starts an empty one. It asks first;--yesskips the question and--no-backupskips the copy.tg search all --meetings [provider:account]also searches one meeting account's transcripts, chat and summaries;--max-meetings <n|all>sets how many meetings it looks through (100 by default).
Security
- The old
messages.dbis deleted when the store opens at its default path: the unencrypted file used beforewirecat.db, with its-waland-shm. One line on stderr names it. It is kept whenMESSAGING_STOREis set, and while another process still has it open. From@wirecat/cli-messaging0.222.0.
0.45.0 — 10.10.2026
Changed — may break scripts
- The local store is a new file,
wirecat.db, and starts empty. It sits beside the oldmessages.db, whichtgleaves as it is: not read, not converted, not deleted. Runtg store fetch --allto bring messages back from Telegram. What exists only on this computer — for example notes, aliases, tags, tasks and transcriptions — stays inmessages.db. The login stays. Upgrade max-cli at the same time, or the two see different archives.
What's new
tg contacts timeline <person>, also over MCP as thecontacts timelinecommand oftg_read: everything one person took part in, in every messenger linked to them, newest first, from the local store.--scope personal|work,--since-time,--until-timeand--limitnarrow it.
0.44.1 — 10.10.2026
Fixed
- Local PDF text extraction and page previews accept documents beyond 20 pages; extraction follows command cancellation rather than a separate 30-second cutoff. File and image budgets remain.
- Local transcription accepts complete mono or stereo Ogg Opus recordings beyond ten minutes. Long recordings need more memory and processing time.
- Attachments from ordinary hidden working folders are allowed. Known credentials, CLI folders and the message store remain protected.
- Markdown exports preserve message formatting. MCP write arguments preserve original Unicode while returned text still exposes invisible controls; configured model gateways support normal redirects.
- Windows update and MCP setup support ordinary relative PATH entries and custom command-processor environments. This patch keeps the existing message-store schema.
- Search troubleshooting distinguishes archive-only discovery/offline requests from ordinary server-backed word search, so an empty local archive does not imply Telegram was searched.
0.44.0 — 10.10.2026
What's new
- Message search can discover partial word matches and eligible direct replies with
--discoveror MCPdiscover: true, using the local archive without model downloads. Strict search remains the default; matched/missing terms help agents check evidence before answering.
0.43.1 — 10.10.2026
Changed — may break scripts
- The project is now licensed under Apache License 2.0. See
LICENSEfor the terms.
0.43.0 — 10.10.2026
Changed — may break scripts
-
The package is
@wirecat/tg-cliand its repository belongs to WireCatLabs. Use this package for installations and updates. -
Local transcription accepts complete mono or stereo Ogg Opus recordings up to 10 minutes. Split longer recordings first. PDF text extraction supports at most 20 pages and 30 seconds.
-
MCP text results and write arguments expose invisible controls, including decoded formatting. Subdivision flag emoji stay intact; ordinary CLI machine JSON preserves original strings.
Fixed
- After an upgrade, server restarts invoke Node directly with separate arguments and preserve the selected environment, including installation paths with spaces on Windows. Invalid profile names in lock files are skipped.
Security
- Attachment directory extraction and retained-file transfer refuse hidden paths, CLI-owned folders and the message store, including symlink targets. MCP extraction downloads also refuse those locations.
- DOCX extraction applies the bounded office archive reader before loading document content.
0.42.0 — 09.10.2026
Changed — may break scripts
- Auto-replies answer everyone your rules match, unless you limit the audience; the separate
testerslist is gone.tg replies audience --reply listed --allow-people <ids>answers only selected people;--deny-peopleand--deny-chatsleave some out. Nothing is sent untilpermissions.replies.sendisallow, and a new rule is off until you turn it on. A rules file that still hastesterskeeps answering exactly the same people: they become the allowed people (only those the audience also allowed, if it was alreadylisted). Allowed chats in such a file are dropped, because they would open replies to everyone in those chats; deny lists stay. The file is rewritten withouttesterson your nexttg repliesedit. tg replies status --jsonno longer hastesters; theaudiencecounts say who may be answered. Intg replies testandserve, a sender outside the audience is skipped with "not on the allow list" instead of "not a test account".
0.41.0 — 09.10.2026
Changed — may break scripts
- The message store drops the copies kept for older versions (store version 28, cli-messaging 0.212.0). Notes, contact notes, relations and entities written before the notes refactor are copied into their new tables once, during the upgrade. After it, an older tg, max or memo refuses the store with "upgrade this tool" — update all three together.
0.40.1 — 09.10.2026
Fixed
tg search allfound nothing on a fresh store. It searched only accounts already in the store, so before the first save it looked nowhere; it now always includes this profile's account and asks the server the waytg search messagesdoes.tg search mailwith no mail imported answers an empty result with a note on stderr, instead of failing.- Notes found only by a weak match in meaning are dropped, so a rare word no longer returns every note.
0.40.0 — 09.10.2026
What's new
tg topics show <chat> <topic>shows one forum topic: its title, whether it is closed or pinned, unread messages and last activity.tg messages forward --topic <id>forwards into a forum topic of the--togroup. The topic is checked first, as withmessages send --topic; topic 1 is General.tg attachments show --page 1returns a retained PDF page as PNG. Remote agents whose clients cannot open an embedded PDF can read it page by page as images; rendering needs the optionalunpdfand@napi-rs/canvaspackages.
Changed — may break scripts
-
Statistics
--answereraccepts stored names, aliases and @usernames. Resolution stays local to the selected history’s accounts; ambiguous names return scoped candidates. Unknown names now fail instead of producing a fabricated zero-answer identity. Useperson:provider/account/idto explicitly select an unseen opaque ID. Response rows addidentityKnown; an ID without observations hasidentityKnown: falseandstatus: unknown. Zero observed answers do not prove inactivity (statistics). -
Every search moved under
tg search. The old commands are gone:For agents the tools moved the same way:
search messages,search conversations,search topics, and the newsearch allto start with. -
tg search messagesnever returns mail. A saved search that namesin:emailnow asks fortg search mail. -
Permissions named after the old paths (
messages.search,conversations.search,topics.search) stoptg searchuntiltg config migraterenames them, keeping their levels.
0.39.1 — 08.10.2026
Fixed
- Pin the shared messaging library to 0.205.0, matching Memo and MAX for coordinated installation.
0.39.0 — 08.10.2026
What's new
tg polls create --close-time 5mcloses the poll by itself that long after sending, from 5 seconds to 10 minutes.tg polls voters <chat> <message> [--answer <id>]lists who voted for what in a poll that is not anonymous. When Telegram answers that you must vote first, or that a channel hides its voters, the error says so.tg chats link update --expire-time nevertakes a link's expiry away. The group's own link can be changed too; the help no longer says otherwise.tg store jobs list --state <state>lists only the background jobs that are running, done, failed, cancelled or died.
Changed — may break scripts
tg chats link createandupdaterefuse--approvalwith--max-uses. Telegram dropped a use limit when approval was turned on, without saying so; now you choose one.- Latin words are searched by their English and Spanish stems at once. Before, only Spanish, so English
word forms ("budgets" → "budget") matched worse.
Watch for: after the update the stem index rebuilds by itself — a small store on open, a large one bit by
bit:
tg servefinishes it in the background,tg store migrateat once. Until it is ready a search matches exact word forms, says so on stderr, andquery.stemming.appliedisfalsein JSON. The stem index of Latin text is about twice as large. AsearchStemmers.latinyou set yourself stays, andtg store reindexstill applies it. Updatemaxtoo: an older one, opening the rebuilt store, answers a stemmed search with "upgrade this tool" (archive). - Notes about a person (
tg contacts notes) show in every profile that sees them. Before, only in the profile where they were written. Why: notes are yours, not one account's; the shared store now keeps them apart from messages, together with notes frommemo. Watch for: with several Telegram profiles, a person's notes from all of them now show together. Aliases (contacts alias) still apply only in their own profile.
Fixed
tg polls voters --answer <id>names the answer of each vote; it listed them with no answer. Without--answer, it no longer says more voters remain when it has shown them all.
0.38.0 — 08.10.2026
What's new
tg account listshows every profile on this computer, the account each is logged in as and its name. It asks Telegram nothing.
Fixed
tg session startsays "Already logged in" when the profile's session still works and nothing was asked, withsession endto log in again; it used to look like a login without a code.--jsongainsalreadyLoggedIn.tg session start phone --smsno longer aborts the login when Telegram has no SMS to send (SEND_CODE_UNAVAILABLE): it says so and asks for the code Telegram already sent to the app.tgor a command group with no subcommand (tg account,tg chats) shows its help again at a terminal, instead of✗ (outputHelp). A script or--jsongets avalidation_errorsaying to give a command.
0.37.0 — 08.10.2026
What's new
-
Agents can read one folder's chats by name over MCP, as
tg chats folders showdoes (tg_read, command:chats folders show). -
tg chats link update <chat> <link> [--approval | --no-approval] [--expire-time] [--max-uses]changes one of your extra invite links; only what you give changes. -
Retained files for remote agents:
attachments showtransfers bounded chunks with whole-file SHA256. MCP returns complete images or binary resources, with a JSON/base64 fallback. Transfer performs no OCR or index write; the agent reads the file and saves literal text (attachments). -
The shared dependency also adds observed retention cohorts and counter observations with per-field freshness; unknown values remain explicit.
Changed — may break scripts
- Ranking and evidence JSON includes per-field counter observations and freshness; evidence also accepts retention-cohort selections. Inspect each field and selection kind before interpreting the result; unknown values and incomplete archives do not mean zero.
0.36.0 — 08.10.2026
What's new
-
tg polls create --quiz --correct <n> [--solution <text>]sends a quiz: one right answer, by its position from 1, and a vote that is final. -
Stored administrator reports find questions without observed answers, selected responder latency, known-join newcomer help and viewed posts with little discussion. Reports provide coverage/evidence; saved runs retain parameters and selections.
-
tg chats folders show <folder>lists one folder's chats by name, with its pinned and excluded chats. Names come from the local archive; Telegram is asked only for chats the archive does not hold. -
tg metadata refresh --only-missingreads descriptions only for groups and channels that have none stored yet; without--chatit takes every stored group and channel, up to--limit. -
tg store jobs retry <job>starts a failed or died background fetch again with the same options;--failedretries every chat whose newest job failed or died.tg store jobs clearforgets finished jobs and their logs. -
tg session start phone --smsasks Telegram to send the login code by SMS when it would go to the app. Telegram decides: the note after the request says how the code was really sent. -
tg topics delete <chat> <topic>deletes a forum topic and every message in it, for everyone. It asks first by default;--allow-dangerousskips the question. -
Attachment text can be read locally: ODT, ODS, XLSX, PPTX, EPUB, BOM-marked UTF-16 and high-confidence legacy encodings. No model is called; formulas are not calculated and images remain for the agent. Search explains the limits.
-
tg chats folders create|updatetake rules:--includecontacts, non-contacts, groups, channels or bots,--skipmuted, read or archived chats,--exclude-chat,--pinand--emoji.folders listshows them.
Changed — may break scripts
tg chats folders joinsays plainly when a link is invalid or expired (exit 6), andfolders orderanswers only each folder's id and title.tg chats folders create|updateanswer with the folder as Telegram stored it: an--emojithat is not one of its folder icons is dropped by Telegram, and tg used to report it as set.
0.35.0 — 08.10.2026
What's new
tg chats requests list --search <name>or--link <link>narrows the requests — by name, or to those that came by one link; Telegram cannot do both at once.tg polls showsays whether a poll is a quiz (quiz), whether a vote may change (revote), and whether you made it (creator) — only its maker can close it.tg polls voteandtg polls closerefuse what Telegram would refuse, before sending: a closed poll, two answers in a one-answer poll, a changed or retracted vote where the vote is final,--retractwith no vote, and closing someone else's poll. Telegram's poll refusals now say what to do instead of "Telegram refused: X", and a timeout while reading the poll no longer says the vote may have gone.tg chats requests accept|decline <chat> --all [--link <link>]answers every pending request at once, andtg chats link list/tg chats link revokeshow and stop your invite links. An--allaccept is counted against the hourly limit before anyone is let in.- Rankings retain Telegram reply links and linked channel discussions, so conversation measures use those links when available; ambiguous forum-topic links remain unknown.
- The ranking guide explains measures, scores, coverage, saved selections and evidence. Replaying a saved selection now preserves exclusive date boundaries.
tg store fetch --alldownloads every chat — the last 90 days of each, most recently active first;--backgroundruns it as a job. Search needs it: prepare your archive.- Your own names and notes for people:
tg contacts aliasandtg contacts notes, kept on this computer only;contacts show --with-notesandcontacts list --search-notesshow and search them (people). - Automatic tags for groups and channels:
tg metadata refreshandtg tags auto, from title and description, never touching your own tags (search).
Changed — may break scripts
-
Every search says what it searched. One line in the terminal — messages and chats searched, chats never fetched or behind, and the command that fixes it;
coverage.nextin JSON tells an agent what to run. -
The search guides now correctly describe the existing default (
--backend both). Word search asks Telegram as well as the local archive, as it already did in 0.34.0. Use--backend archivefor local-only searches. Counting withstats, topic search and queries the server cannot answer still read only the archive. -
tg chats jointo a group whose admins approve who joins answersrequested: trueand exits0, instead of exit11: the request was sent all along. A script that treated exit 11 as "request sent" now readsrequested.
0.34.0 — 07.10.2026
What's new
-
tg stats messages topandtg stats contacts toprank stored messages and their authors, andevidenceunder each shows the messages behind a place in the ranking. They read only the local store and ask Telegram nothing;searches create --selectionsaves such a ranking as a search. -
Every profile now has one request pace, shared by all
tgprocesses using it. Two commands at once, backgroundstore fetchjobs,mcpandserveused to pace themselves separately, so running several multiplied the request rate; now they share one allowance — a burst of 20, then one request a second. A wait Telegram asks for holds the whole profile, and a request that would wait more than 5 minutes fails at once with exit code8. Bulk work run in parallel takes longer.requestsPerMinuteorTG_REQUESTS_PER_MINUTEchanges the pace; the limits page explains all of it. -
tg messages send --htmlandtg messages edit --htmlread Telegram's HTML —<b>,<i>,<u>,<s>,<a href>,<code>,<pre>,<blockquote>,<tg-spoiler>— with line breaks kept as typed (usage). -
tg messages send --file … --filename <name>sends the file under the name others see. -
tg messages list <chat> --topic <id>reads one forum topic, back from its newest message or--before-id. -
tg chats folders orderputs folders in the order you name, andtg chats folders join <link>adds a folder someone shared by at.me/addlist/link, joining every chat in it. -
tg chats link create <chat>makes another invite link —--approvalto make whoever joins by it ask first,--expire-timeand--max-usesto limit it — andtg chats update --join-approval on|offmakes everyone ask first. Both work in a private group as well as a public one. -
tg chats requests list <chat>shows who asked to join a group that needs approval, andtg chats requests accept|decline <chat> <person>answers one. Only admins see the requests; an accepted one counts toward the hourly limit like an added member. -
tg messages search --backend bothasks Telegram as well as the archive. Telegram's results are saved and checked by the same query, soexact:,-wordand the ranking keep their meaning; each message says whether it came from the archive, Telegram or both.--backend servershows Telegram's results alone;--server-timebounds the wait (5 s). The default isboth(search). -
tg chats mark-read <chat> --topic <id>marks one forum topic read, up to--untilor its newest message, and leaves the rest of the chat as it is. -
tg topics edit <chat> <topic>renames (--title), closes or reopens (--closed on|off) and pins or unpins (--pinned on|off) a forum topic, and hides or shows the General topic (--hidden on|off);tg topics order <chat> <topic...>puts the pinned topics in order. Repeating either is safe. -
tg messages send --spoilerblurs a photo or video until tapped, and--caption-aboveputs the text above it. A spoiler on a document or voice message is refused. -
tg chats send-as <chat>lists who you may post as in a group, and--send-as <id>posts as one of them — ontg messages send(files included),tg messages forwardandtg polls create. The list always includes you and marks the group's saved choice; reading it changes nothing. An id not in the list is refused.
Changed — may break scripts
- A send, forward or poll with no
--send-asto a group that posts as a channel by default is refused (exit2), instead of going out as that channel. The error names--send-as <your id>to post as yourself and--send-as <channel id>to post as the channel.
0.33.0 — 07.10.2026
tg contacts profileandtg contacts checkestimate the age of accounts made up to August 2026. The table that guesses a sign-up month from an account id ended at November 2025, so the newest accounts got no estimate. Late-2025 ids now read up to four months later than before, closer to when they were really made. Estimates for 2026 are off by about three months;source: "estimate"still marks every guess.- Attachment OCR through the shared gateway. Agents normally read images/scans themselves and
write text through
attachments text set. Explicit bulk processing usesattachments extract --ocr,models.ocrand bounded--concurrency; complete text enters the existingcontent:index. Hash/model caching avoids repeated calls, and failures preserve agent text and old indexed text.
0.32.0 — 07.10.2026
What's new
tg messages comments <channel> <post>reads the comments under a channel post, andtg messages send --comment-to <post>writes one. Comments live in the channel's discussion group; a post without one is exit6.tg contacts profilelists earlier names and usernames underaliases, oldest first, with at.melink for an old username. The local store now keeps a name or username when it changes. See People.
0.31.0 — 07.10.2026
What's new
-
File extraction through MCP, explicit directories and
messages download --extract; changed files are checked by content hash. Optional bounded local preparation follows history fetches, off by default.store gaps planandstore gaps repairinspect recorded interior gaps and explicitly repair them with bounds and resumable jobs; unknown edges and ambiguous pages remain pending. -
tg stats chats official <chat>: Telegram's own statistics for a supergroup or channel you administer, as its apps show them — totals against the previous period, top posters, admins and inviters (supergroups), recent posts and notification share (channels), and every graph as JSON series. Read only. Works where Telegram shows you statistics; elsewhere it fails with a permission or validation error. See Groups you run. -
cli-messaging 0.162.0 also brings
store gaps repair, the catch-up options ofstore fetch,messages download --extractandattachments extract --from-dir/--cursor. -
Configuration, permissions and profiles have separate guides. Setup starts with file locations and common tasks; the full settings reference remains available.
Changed — may break scripts
-
Configuration is split into a short guide and full key/type/default/scope/environment reference. The public CLI contract describes headless execution, schemas, bounds, previews and retry rules.
-
Validate portable skill metadata, installed version, command paths and configuration-key coverage in CI. Native login and optional setup questions respect the shared no-input policy.
-
First settings resolution creates config.json. Existing files are preserved; environment and flag overrides are not saved. config show may now create the file, and common values report file defaults as their source.
-
Word and phrase searches include word forms. Scripted queries may return more messages. Use exact: or --exact for the previous exact-form behavior; explicit text: still matches forms. Archive language settings affect matching.
Fixed
-
Search catch-up honors readonly or denied
conversations.linksbefore fetching or queueing preparation, including gap repair. Explicit--no-catch-upstill permits authorized history reads. -
Person context finds private dialogs without recorded members when the dialog ID is the person's ID, restoring direct messages and the last message each way in existing Telegram stores.
-
Interrupted writes preserve their unknown outcome, operation ID and retry information; check the result before retrying a Bot API write that timed out.
0.30.0 — 07.10.2026
Changed — may break scripts
-
tg mcpoffers an agent three tools instead of one per command:tg_tools_search,tg_readandtg_write. The agent finds a command by words and runs it as{ "command": "messages list", "arguments": { … } }, with the same arguments and the same answer its old tool had.tg bot mcpworks the same way:tg_bot_tools_search,tg_bot_read,tg_bot_write. Why: an agent read about 80 tools' descriptions before its first question. What to watch for: the old names (tg_messages_send,tg_statusand the rest) no longer work, and neither do client rules that name them; allowtg_read, andtg_writeif you want, in your client (MCP). -
Writes over MCP show no confirmation form: the profile's permissions decide alone. A level of
askacts likeallowover MCP, over stdin/stdout and--httpalike. Why: forms broke in many clients and got in the way. What to watch for: with the default permissions an agent may now delete your own messages; settg config set permissions.messages.delete readonlyto stop it. Actions a group's rules want confirmed are left for you.--confirm-send,--allow-dangerousand--http-confirmation(from 0.30.0) are accepted with a warning and change nothing;tg mcp configno longer writes them. -
Statistics use
stats messages show,stats chats showandstats tasks show. Legacymessages stats,chats statsandtasks statspaths are removed. Update commands and exact permissions tostats.messages.show,stats.chats.show,stats.tasks.show. MCP: usetg_readwith the same command path. -
Parser errors return exit 2 with a structured validation_error. Scripts expecting prose or exit 1 must update their error handling.
What's new
-
tg setupis easier to follow. Each step is a heading,[1/5] This computer, with what happened indented under it; the questions and the QR code sit under their step, with a blank line around the code. The closing summary lines its labels up, the command to try first on top.--jsonoutput and its keys are unchanged;--quietstill hides the steps. -
A list of what waits on you. Since 0.29.0,
reviewandservekeep a task in the local store for a question nobody answered and a message that mentions you by name, and close it once you answer; now you can see them.tg tasks listshows each with the message it points at;tg tasks add <message> --type promiseadds what the rules cannot see;tg tasks close <task> --as done|dismissedcloses one for good;tg stats tasks showcounts them per chat. Nothing is sent by these commands. MCP: usetg_readortg_writewith the same command path. -
Reply rules can be edited from the CLI and use Liquid templates with optional ai blocks.
replies add|edit|on|offchanges rules andreplies audiencechanges profile allow/deny lists.models.repliesselects the provider;replies consentsgrants profile/endpoint consent with native-chat opt-outs. Ordinaryreplies testpreviews instructions/fallback without calls;--aiexplicitly submits stored data. Legacy templates retain their literal fallback with warnings. Sending remains limited to testers and replies.send; see archive. -
MCP writes can run from web clients without server forms. The profile's permission levels apply to HTTP and stdio alike;
askandallowpermit the requested MCP write. Repeat--permission key=levelto override permissions for this server process without editing config. App approval is separate and cannot be verified by the server. Browser setup. -
Charts can be saved as PNG.
tg stats charts <chat> --output activity.pngwrites a dark-theme chart to a new file; SVG stays available. MCPtg_readwithcommand: "stats charts"andformat: "png"returns an image and JSON without connecting to Telegram or writing a file. -
The open-tasks MCP prompt lists pending tasks. It calls review to refresh tasks, then lists them with an optional
chatfilter; closes tasks only after approval and sends nothing. -
Browser setup covers Windows, macOS and Linux. The guide separates PowerShell and terminal commands, temporary send permissions, Codex web login, two simultaneous servers and stopping individual tunnels. Browser setup.
Fixed
-
Estimated registration dates are closer for accounts made in 2022–2025. When Telegram does not give the month,
contacts profileestimates it from the id; the estimate now rests on 212 real sign-up dates. Accounts from 2022 no longer look about nine months younger than they are: estimates are off by one to two months in the middle case. Ids up to November 2025 now get an estimate; newer ones still get none. -
tg serveandtg watchstopped with SIGTERM or Ctrl-C end cleanly. They exited 1 withdatabase is not open, and the updates and contacts that were still arriving were lost: the Telegram library closed the login file on the signal, before the command had finished with it. Now the command closes it, once, after saving what arrived. -
chats showgives a supergroup's real member count, which Telegram's chat list showed as missing or out of date, and a group's card or invite link gives a basic group's count instead of 0. The member list now carries the group's count too, sochats members fetchcan tell who left a supergroup once tg moves to the next shared library.
0.29.0 — 06.10.2026
What's new
-
Long messages are searched by meaning in full. A message longer than about 1200 characters is split into overlapping pieces before it is embedded, so
messages searchby meaning reads all of it, not only its start. Chats built before read as outdated, andconversations buildorsearch --refreshrebuilds them (cli-messaging 0.153.0; the store moves to version 21, which older builds still write). -
A person's profile.
tg contacts profile <person>shows what Telegram says about someone — every username, bio, birthday, Telegram's own marks (bot, verified, premium, scam, fake, restricted, deleted), when they were last seen (recently,weekandmonthare no longer shown as hidden), whether you are each other's contacts, when the account was made (Telegram's own month, or an estimate from the id, always labelled), whether they have a photo of their own — and, for each chat you share, how many of their messages are stored, the first and the last. The phone shows its last four digits unless--show-phone. It asks Telegram nothing more thancontacts showdoes. MCP:tg_contacts_profile. -
Record group membership over time.
tg chats members fetch <chat>saves profiles, membership changes and a daily count;--budgetlimits pages, and nobody is recorded as having left after a partial read.--trackstarts daily fetching whiletg serveruns.chats tracking list|show|add|removemanages the tracked groups; stopping tracking keeps recorded history.chats members history --since-timereads recorded joins, leaves and profile changes without contacting Telegram. The first snapshot records a baseline, not proof that every person joined that day; missed days are not reconstructed.chats members list --offlinereads the last complete saved roster. Uses cli-messaging 0.152.0. -
tg contacts context <person> --chat <chat>(repeat it for more) gives their newest messages in each chat, as time and text only, for an agent to summarise;-vadds ids and links,--limitis per chat, and--refreshasks Telegram first with one search by sender per chat. -
Is this account a bot?
tg contacts check <person>scores one person from Telegram's own marks, their profile and oldest photo, what the store holds that they wrote, and the public spam lists Combot CAS and lols.bot, which are sent their id;--no-registriesskips the lists.tg chats members audit --deep <n>runs the same check on the top n members, one a second. Every reason says where it came from; a hint, never a verdict.
Fixed
- Help explains what member checks read and where they connect.
--no-registriesskips public ban lists but still requests the person's profile and photos from Telegram;--offlineis the local-only mode. Deep checks inspect at most 1,000 stored messages per person and make individual requests for selected members.contacts context --chat --refreshexplicitly connects before reading the store. contacts profileno longer guesses a registration date for the newest accounts. The id table ends at December 2024 and cannot tell a newer id from 2025 from one from 2026; such ids now get no estimate rather than a date that may be years too early.tg mcp --http: Claude and ChatGPT can finish logging in. The login page made the browser send its form as coming from nowhere, andtgrefused it with "Origin not allowed". Now the login works (cli-messaging 0.152.0).
0.28.0 — 06.10.2026
What's new
-
Search the text inside files.
attachments extractindexes retained plain text, Word and PDF text layers forcontent:queries. Word/PDF need optionalmammoth/unpdf; an agent reads scans and photos and saves their text withattachments text set.--download --output-direxplicitly fetches missing files. -
Refresh before searching and follow replies.
--sync-firstfetches within defaults of five chats, 500 messages and 30 seconds; incomplete refresh keeps local results and reports stale coverage.--threadfollows a bounded stored reply graph with link provenance, falling back to time context when absent. -
Filter conversations and choose account scope.
--filteris strict Lucene and applies before ranking; one message must match the entire filter.--sourcewidens scope explicitly. MCP now offers agent-linking batches, link write-back, rebuilding and thelink-conversationsprompt. -
Configure embeddings and analysis separately by profile. Local embeddings and the owner's agent remain defaults. Remote providers receive text only when chosen;
build --analyze --chatrequests and remembers account/chat/provider consent until revoked. A remote embedding setting also sends MCP search query text. -
tgconnects through a proxy: SOCKS5, HTTPCONNECTor MTProxy. Set it per profile withtg config set proxy <url>— ortg config set proxy -to paste one with a password or an MTProxy secret, which is kept in the OS keyring, never in the settings file — or for one run withTG_PROXY. Bot API commands use the same SOCKS5 or HTTP proxy; with an MTProxy they go direct, andtg doctorsays so. A proxy that refuses or cannot be reached fails at once withconfiguration_error(exit 3), so it never reads as Telegram being down. -
tg doctorsays what it really checked. The login shows asnot checkeduntil you add--online, and each private file or folder other users can read is named with thechmodthat fixes it;doctornever changes a mode itself.tg doctor --onlinealso reports this computer's clock against Telegram's (a warning past 10 seconds), and whether the account is active, frozen (with its dates and the appeal link), banned, deleted or logged out.tg doctorandtg server statusshow the waits Telegram asked this profile to keep, and any hold on its writes, asflood. -
tg flood clearforgets those waits and lifts the hold on writes, once Telegram no longer limits the account. It never connects. Agents get no MCP tool for it, on purpose. -
Tags: your own labels on a chat, a person or one message, kept in the local store and never sent.
tg tags add <tag…> --chat <chat> | --contact <person> | --message <message>,tags removewith the same target, andtags list.tag:<tag>in a search finds what is tagged. MCP:tags_list,tags_add,tags_remove. -
Saved searches and a search history.
tg searches create <name> [query]saves a search without running it;tg messages search --saved <name>andtg messages stats --saved <name>run it — more words are added with AND, and options you type replace the saved ones.searches list,show,history,deleteandclearmanage them. Every search and count that succeeds is kept in the history: its query and options, never a message or a result, the newest 1,000.--no-recordkeeps a run out of it; for MCP,tg mcp --no-recordorrecordset tofalse. Saved searches and the history are shared with max-cli, which uses the same store. -
tg contacts context <person>: what the store holds about one person — shared chats, the last message each way, their recent messages, where others mentioned them — across every messenger linked to them. It never connects, andpermissions.messages: denyblocks it like other message reads.tg contacts link <person> max:<person>records that a Telegram and a MAX account are one person;contacts unlinkundoes it. -
Reply rules can answer test accounts.
tg serveanswers with the rules inconfig/<profile>.replies.jsononly to the accounts in itstesterslist, and only whenpermissions.replies.sendisallow— it isdenyby default, and an empty list answers nobody.tg replies testshows what the rules would have answered in the stored messages and sends nothing;replies pausestops every rule at once, a runningservetoo;replies resumeundoes it;replies statussays whether the rules may send and to whom. -
tg store repair [--dry-run]brings every table of the store to this build's shape, deleting nothing: a table of the wrong shape is kept as a copy beside the new one, andtg store copies delete <name>removes a copy once you have looked. It repairs a store where reading a message failed onmessages.mentions. -
The store gains tables for tags, saved searches, member history and word stems the first time this version opens it; older
tgbuilds still open the file.tg store migrateandtg store reindexalso build the word-stem index (on a large store, runtg store migrateonce), andtg config set searchStemmers.cyrillic(russianornone) andsearchStemmers.latin(spanish,englishornone) choose the stemmers for the whole store. Searches do not use the stems yet. -
chats members auditjudges with everything Telegram's member list carries. Each member now brings when they joined, who invited them, and whether the account is a bot, deleted, marked scam or fake, or has no photo — so bursts of joins, mass invites and marked accounts show up, with no extra request per person. -
chats statscounts comments on channel posts, beside views and forwards. -
A file whose upload drops is tried again, up to three times, before anything is sent. If it still fails, the error says nothing was sent, instead of exit
14"it may have gone". The message itself still goes once, with its send id. -
Search has three guides. Message search is everyday searching by words, people, dates, files, links and tags; topic search explains conversations, vectors, freshness and what a remote model sends; query language is the reference.
-
tg mcp doctorshows the last lines of the server's error output when it fails to start, with your home folder, long numbers and anything like a token hidden.
Changed — may break scripts
-
Local e5-small meaning results require cosine similarity above 0.80 before combining with words. Exact word matches remain eligible. Results may be shorter and a combined hit may become words-only.
-
The shared archive gains attachment text and analysis consent tables. Opening it migrates local schema while retaining existing messages; back up a large archive before upgrading.
-
A wait Telegram asked for is remembered. After a
FLOOD_WAIT(exit 8,rate_limited, withretryAfterMs), the same call — and, when it named a chat, the same call in that chat — fails at once with exit 8 anddetails.remembered: trueuntil the wait has passed, without asking Telegram. A script that retried at once after exit 8 now gets exit 8 again, sooner.tg flood clearforgets the waits. -
A frozen or spam-limited account's writes are held. After Telegram refuses a write because the account is frozen or limited as spam (
PEER_FLOOD), every send-type write fails with exit 5 (permission_error) that says until when; reads, reactions and marking read still work. A spam limit holds for an hour, set again by each new refusal; a frozen account until Telegram's end date, or a day.tg doctor --onlinesets a frozen hold and lifts it once the account is active again; it never lifts a spam hold —tg flood cleardoes, once you know the limit is gone. -
PEER_FLOODexits with code 5 (permission_error), not 11, and points to @SpamBot: retrying makes it worse. A frozen account's refusal is also apermission_errorpointing totg doctor --online, not a rate limit to wait out. A banned or deleted account no longer tells you to log in again. -
A one-shot command waits out a FLOOD_WAIT of up to 10 seconds twice at most, not five times, and says so on stderr; the next one ends it with code 8 (
rate_limited) andretryAfterMs.serveandwatchwait up to 2 minutes, three times. -
tg serveandtg watchexit when Telegram ends the login while they listen, with code 4, within about 15 minutes; the service does not restart on it. If the updates stop for another reason, or Telegram does not answer within 30 seconds when asked, they exit with code 12, which systemd restarts. Before, they stayed up and received nothing. -
Telegram's
AUTH_KEY_DUPLICATED(a login ended because two connections used it at once) is nowauthentication_error, exit 4, notprovider_error. The message says to log in again and names overlappingtgprocesses as the cause. -
Pin, unpin, react, mark read, delete, vote, poll close, folder and contact changes end in exit
14(outcome_unknown) when Telegram does not answer, instead of a timeout or network error that the send journal recorded as failed. The message says whether a repeat is safe; for a folder creation it is not — checktg chats folders listfirst. -
tg inbox,inbox --new,reviewandchats list --unread(also with--searchand--kind) look at every chat, not only the newest 100 or 200, so an unread chat further down the list is no longer left out. This costs one request per 100 chats.partialnow means only that Telegram could not list every chat; chats past the 20-per-run cap are named in askipped N chatsnote. -
tg messages list --after-id,--after-timeand--before-timeno longer stop at a page shorter than--limit. Telegram leaves deleted messages out of a page, so a short page in the middle of a chat answeredhasMore: falseand dropped the hint for the next page. They now say there is more until Telegram returns an empty page, as plainmessages listalready does: the last page may say there is more, and following its hint returns an empty page. -
tg messages searchtakes its query as optional, since--savedcan stand alone; with neither it still refuses.
Fixed
-
Account-qualified context locators reject another account before reading. MCP also accepts
offline: truefor ordinary stored context. -
Stopping
tg servewith Ctrl-C or a signal exits 0. The session database closes once, avoiding the previous "database is not open" error on shutdown. -
messages deletechecks the ids belong to the chat first. In a private chat or a basic group Telegram numbers messages per account and deletes by number alone, so an id from another chat — or the other side's number for the same message — deleted a message there. Now any id that is not in the named chat stops the whole delete with exit 2, and nothing is deleted. -
text:/…/in a strict search folds letters as the word index does, sotext:/Квартир.*/andtext:/счёт/find the words they missed. A search error says what to do instead:~points to--language legacy, a prefix too short to expand names a longer one, and an index still building gives the exacttg store migrate. -
Two
tg serves started in the same instant for one profile can no longer both run.
0.27.0 — 04.10.2026
What's new
-
tg mcp --http --public-url https://<name>.ts.netserves behind your HTTPS tunnel with its own owner-code OAuth login. Every HTTP write needs a form;tg mcp --revokeforgets browser logins for the profile. -
tg chats stats <chat>counts stored group/channel activity and asks Telegram for joins and leaves. Offline and MCP results omit membership; incomplete counts are lower bounds. -
tg chats members auditlists suspicious member signals without removing anyone; unavailable signals are reported inunknown. MCP inbox/review acceptkindsandnewwith their own checkpoints. -
Personal MCP uses the matching shared catalogue adopted by MAX. Photo previews accept
index, and direct transcription acceptsmodel. The SDK also adds archive statistics, conversation readiness and bounded local refresh; models are never downloaded automatically.
Changed — may break scripts
-
Search/statistics coverage uses actual inventory and fetch timestamps; each completeness entry adds
fetchedAt. Old stores gain these facts after the next whole chat list and history fetch. The/catch-upprompt takeskindandmodeinstead ofsince. -
config set permissionsrefuses unknown command keys, including keys inside a whole object, with exit 2. Existing files warn and continue;config unsetcan remove an old unknown key. -
store fetch --page-sizeabove 100 is refused before connecting. Runstore fetch <chat>again to repair an incorrect history-start mark when older messages exist. -
tg serveexits with code 12 (provider_unavailable) when a saved session exists but the app credentials are unavailable, for example while the login keyring is locked. Systemd retries after 30 seconds; macOS needstg server start. Other commands and profiles without a saved session still exit 4. -
tg serveandtg watchrefuse to start with code 4 (authentication_error) if the session was already revoked. They check the login before reporting readiness. A session revoked after startup still needs a separate check. -
The background service no longer restarts on that code. On systemd, exit 4 prevents a restart. On macOS, launchd cannot exclude one exit code, so the agent no longer restarts after any failure. Run
tg server installagain to update the unit; aftertg session start, runtg server start. -
Unknown personal MCP arguments now fail before execution. Use the advertised schema, including
at_timefor scheduling. Approved schedules execute at the absolute time displayed in the form. -
tg messages listcan answerhasMore: true, with theolder messages: --before-idhint, on a page shorter than--limit. Telegram leaves deleted messages out of a page, so a short page is no proof of a chat's first message. Even the last nonempty page may say there is more; following its hint can return an empty page.
Fixed
-
Legacy, regex and filters-only search report the actual word-index readiness.
server statusreports the last normal unit exit and a stopped-login hint when the unit deliberately stays down. -
tg store fetchno longer stops early and counts a chat as complete when a page comes back short. Telegram leaves deleted messages out of a page, so a page can be short in the middle of a chat; the fetch now goes on until Telegram has nothing older. For a chat already counted as complete with older messages missing, runtg store fetch <chat>again: it reads below what is held.
0.26.0 — 04.10.2026
What's new
-
The bundled agent instructions explain how to find agreements, prepare meetings and recommend contacts. Agents check archive coverage, compare group and personal chats, distinguish people with the same name, and retain a draft when sending is refused.
-
tg messages linkand read-only MCPtg_messages_linkreturn a message permalink and locator. Channels and supergroups preserve thread context; private links require access and grant no membership. Dialogs, basic groups and Saved Messages return a locator. Offline validates the stored message without connecting; locators for another account are refused. Singularlinkdiffers from conversation-graphlinks.
Changed — may break scripts
-
Unpin uses its own permission,
messages.unpin, in CLI and MCP. Previously the shared guard checkedmessages.pin. Profiles with explicit canonical permissions should review their unpin rule; legacyallow: ["pin"]continues to cover both actions. -
tg commands [path...] --jsoncan describe one command or group. For example,tg commands messages search --jsonincludes global options and exit codes alongside that command. Without a path the full tree is unchanged; scoped responses addscopeandinheritedOptions. Inspect different command paths in separate calls.
Fixed
-
Unanswered reviews consider retained voice transcripts and requested new transcripts before filtering. Add
--transcribeto recognize voices that have no retained text. Unrecognized voices leavecompletefalse: keep the previous review boundary rather than treating an empty result as proof that nothing needs an answer. -
Commands opening the local archive together wait briefly for initialization instead of failing immediately when another process holds its write lock. Persistent locks still fail normally.
-
Voice transcription downloads use the history connection and close it before local recognition, avoiding a second connection for
messages list --transcribe,inboxandreview.
0.25.0 — 03.10.2026
Fixed
chats showexplains that differing listed-member and participant counts may reflect self omission or a partial list, rather than claiming incomplete loading. JSON data stays unchanged.
What's new
-
The README and bot guide make the complete native Bot API surface explicit: all 185 methods of the pinned Telegram Bot API 10.3, alongside the convenient bot commands and use-case MCP tools.
-
config migrate --dry-runpreviews legacy access settings as canonical permissions without writing or connecting;config migrateapplies it explicitly while preserving effective levels. Other configuration values stay unchanged. -
tg <bot> bot api <method>covers the pinned Telegram Bot API schema using cli-core generators and the common MAX/TG command builder. Native field flags, JSON/stdin bodies and nested multipart uploads share validation and write guards. Destructive methods ask by default; unanswered writes are never retried. Managed bot credentials require an explicit--store-token <profile>destination and stay only in the OS keyring; stdout contains a storage receipt.
0.24.0 — 03.10.2026
Changed — may break scripts
--mduses Telegram's own formatter for personal and bot send/edit/captions. Nested styles, underline, spoilers, links, code fences and quotes are supported.__text__means underline; a single*text*now means bold. MAX has different syntax. Invalid nesting and unsafe links are refused before writing.
0.23.0 — 03.10.2026
Changed — may break scripts
-
Local message search defaults to a strict Lucene profile: groups, typed fields/date ranges,
--timezone, bounded wildcard/regex and coverage on empty results. Write prefixes explicitly asword*; use--language legacyfor previous discovery behavior. The search guide and agent skill explain migration. JavaScript--regexruns in an isolated worker with size and time limits. -
tg upgrade --jsonalways includesrestarted, including checks and no-op updates. Previous fields remain; successful upgrades retain the managed-server restart policy. Scripts validating the exact key set should accept the empty array when no server restarted.
What's new
-
tg mcplets go of the search model after 10 minutes without a search: an agent'sconversations_searchno longer keeps about 1 GB in memory for the whole session. The next search loads the model again, in about a second. -
tg <bot> bot meand MCPtg_bot_meshow the bot profile's id, name and username. This read uses the bot token, refuses offline mode, and sends no message. -
Global npm installation installs the agent skill before login when its lifecycle hook is allowed. On Windows it saves the npm command folder to user PATH and keeps the
.cmdlauncher usable under restricted PowerShell policies. The one-call Windows installer also updates its current shell, installs skills when scripts are skipped and verifies baretgwithout account access. -
Setup is discoverable immediately after installation: root help and first-run errors point to
tg setup; setup and session help include examples, agent instructions and Windows advice. Quick-start, installation, MCP and security pages consistently explain the guided first run.tg skill showworks before login and setup completion points agents to it. -
tg topics enableenables forum topics, andtg topics createcreates a named topic. Basic groups require explicit--upgrade --yes; their chat id changes and the result returns the new address. CLI and MCP check rights and report a partial result if upgrade succeeds before enable fails. Topic creation uses--send-idas an attempt identity; its journal refuses reuse after a sent or unknown outcome. Never retry an unknown topic creation. Existing archive rows keep their original chat ids. -
tg messages send --topicandtg polls create --topicsend to a named forum topic. Text, media captions, replies and scheduled messages preserve the topic; missing or closed topics and replies from another topic are refused before sending. MCP accepts the same address astopic. -
tg setupguides the first run: local checks, automatic or browser app registration, QR or phone login, a check of five chats and an optional agent skill. It reuses existing sessions, explains the five-minute wait and leaves history downloads as a separate choice. Windows instructions include.cmdwrappers and an npm exec fallback when PATH is missing. -
tg mcp setup codex|claude-codeandtg mcp doctoradd the local server to a client and check its handshake and tools. Setup requires--allow-writeswhen the profile offers writing tools; doctor does not check the Telegram login. -
tg <bot> bot store fetch <chat>imports older channel and supergroup messages into the bot's local copy, without sending or marking read. Use--from <message link>for a first run without a known message number; later runs continue backwards. Private chats and basic groups are refused. See the bot page.
Fixed
-
A truncated
tg runs list --limitsuggests increasing--limit, instead of the unsupported--pageoption. JSON still reportshasMore; reading recorded runs creates no new record. -
Early bot command failures use bot recording settings, and an unknown subcommand no longer blames a valid leading profile. The shared runner now applies these rules consistently.
-
Login completion shortens Windows home paths correctly. Release documentation checks recognize Windows path separators. File-mode tests apply Unix permissions only on Unix; Windows access follows inherited ACLs, now stated in the security page.
0.22.0 — 03.10.2026
What's new
-
tg messages evidence <chat>andtg_messages_evidenceover MCP prepare a bounded packet from the local archive for an agent’s chat brief, without connecting or marking read. Source locators, fingerprints, explicit coverage and an older-page cursor keep citations and paging precise. Whole messages fit within 64 KiB of JSON items;--limitaccepts 1–100. -
tg <name> bot contacts show --refreshsays the same as inmax: its help no longer names the messenger (cli-messaging 0.109.0). -
The bot page is complete (the bot guide): how to find a chat's id, sending files and their limits, and the exit codes a script sees.
-
tg <name> bot contacts show,bot messages searchandbot messages betweenread what the bot kept on this computer. See the bot page. -
tg <name> bot chats moderateandbot chats rules: a bot judges a group's new messages by its rules and acts as they allow. It judges whatbot watchkept, since Telegram gives a bot no history. See the bot page. -
tg <name> bot mcp: the bot for an agent, over MCP. It offers the tools the bot profile's permissions allow; a deletion asks in a form first. See the bot page. -
tg messages searchtakes a query language:"a phrase",-word,a OR b, and the filtersfrom:,chat:,after:/before:andhas:. A typo is corrected, and stderr says so.--context <n>shows the messages around each hit (2 in the terminal).in:max,in:allor--sourcealso search the other accounts kept in the same store, MAX ones included. See the archive. -
Search a group's conversations by meaning:
tg conversations embed --chat <chat>computes a vector for each conversation on this computer, andtg conversations search "<question>"finds the nearest ones, in one chat or every one you embedded.tg models text list|downloadfetches the model once into the folder the speech models share. With your own key,--provider openai(or--base-urlfor Ollama, LM Studio and the like) computes them instead, after telling you what goes out and what it may cost. See topic search. -
tg store fetchno longer runs for ever when Telegram keeps answering with messages it already gave. -
tg bot watch: what happens in the bot's chats as it arrives, kept in the bot's history on this computer before it is printed;--eventsfor edits, buttons and people joining and leaving.tg bot callbacks answer,tg bot commands list|set|clearandtg bot webhooks list|set|delete, the same commandsmax bothas. See the bot page. -
tg bot chats admins list|add|removeandtg bot chats members remove [--block]: the bot's admins with their rights and title, making one with--canand--title, taking the rights back, and taking a person out of a chat, for good with--block. See the bot page. -
tg bot messages send|list|show|edit|delete|pin|unpinandtg bot chats show|leave|action— the bot writes to a chat by id or title, or to a person asuser:<id>, with--md,--html, a file or a photo. Telegram gives a bot no history, solistandshowanswer from what this bot sent and received on this computer. A delete asks first;--allow-dangerousanswers. -
Your own AI agent can link a group's conversations, when you ask it to:
tg skill show link-conversationsis its guide. It says how much text it would read and waits for your yes, then answers the chat a batch at a time (tg conversations batches next,tg conversations links add);tg conversations links cleardrops its answers. tg calls no model itself. See the archive. -
tg mcpserves this tool's guide as the resourcetg://skill, and names it in what it tells the agent on connecting, so an agent can read it without runningtg skill show.
Changed — may break scripts
tg messages searchputs the best match first, not the newest;--newestgives the old order. When no message has every word, it now takes any of them, then a piece of a word. The JSON keepsitems,limitandhasMore, and addsmatchandscoreto each hit, pluscorrections,completeness(per chat: held in full or not) andwordsReady. A query of one or two letters is searched instead of refused.- tg needs Node 22.16 or newer (or Bun, as before). When a Linux Node uses a system SQLite too old
for the message store,
tgrestarts itself on its own SQLite from@wirecat/cli-messaging-sqlite, before it reads or sends anything. Official Node and Bun builds notice nothing.
Fixed
-
A refused bot write names a working config command with
--botand the permission key (cli-messaging 0.111.0). The former hint placedconfigunderbot, where it does not exist. -
Commands that change only this computer no longer say they change Telegram.
config setandunset,chats rules setandunset,recipients add,removeandclear, and the bot'sauth set,auth removeandrecipients add,removeandclearwrite the config file, the group-rules file, the recipient lists or the keyring. The command reference now says "Changes something on this computer only." under them. They are still listed as writes intg commands.chats moderateandsession endstill say they change Telegram. -
tg contacts showlists the one-to-one chat with the person among the chats you share, newest first. Before, it listed only the groups, because Telegram's list of common chats holds groups only.
0.21.0 — 01.10.2026
What's new
tg bot— a Telegram bot, through the official Bot API and its token:bot auth set|show|remove,bot list [--check],bot chats list,bot recipients list|add|remove|clearandbot sends list, the same commandsmax bothas. Several bots, each under its own name; the token lives in the keyring asbot:<name>, or inTG_BOT_TOKEN. See the bot page.tg conversations batches status|next --chat <chat> [--size <n>]: a group chat in batches for your own AI agent to link into conversations.statussays how many messages and batches are left before you start;nextprints the next batch. tg itself calls no model.tg skill install [--for claude|agents|all]writes tg's guide for AI agents where Claude Code and other agents look for it. When an agent runs tg and no copy is installed, tg says so once a day on stderr;tg config set skillHint false --defaultsturns that off.tg store clear --leftdeletes the chats you have left from the local store, with their messages. It asks for--allow-dangerousand otherwise says how much it would delete.tg conversations build|list|showandtg messages links, with the MCP toolstg_conversations_listandtg_conversations_show: the conversations inside a group, found in the stored messages by replies, mentions and who wrote next — no Telegram request, no AI. Nothing is built until you runbuild. See the store.- A mention by name is kept: when someone is mentioned by name rather than by @username, the stored message remembers whom, so conversations follow it.
tg chats rules show|set|unsetandtg chats moderate, with the MCP toolstg_chats_rules_showandtg_chats_moderate: a group's rules say what to look for — links, invite links, forwards, floods, blocked people — and how far a run may go: deny, report only, ask (the default), or act. Nothing runs in the background. See groups.tg messages list --before-timereads back from a moment: ISO 8601, or2h/1dago.tg contacts add|remove|block|unblock|rename|importandtg account update,tg account sessions end --others, with the MCP toolstg_contacts_add|remove|block|unblock|renameandtg_account_update.contacts importreadsnumber, namelines from a file and prints only counts and who Telegram knew. Ending other sessions logs your phone out too: it asks first, and no agent is ever offered it.tg chats folders list|create|update|delete, with the MCP toolstg_chats_folders_list|create|update|delete. Changing a folder's chats keeps the others in it; "All chats" is not listed, since nobody can change it.tg chats members add|removeandtg chats admins add|remove, with the MCP toolstg_chats_members_add|removeandtg_chats_admins_add|remove.--cantakes members, admins, info, pin, link, post, edit and delete; Telegram has no separate right to read. Adding answers who could not be added; each person added counts toward the hourly limit.tg chats update <chat>—--title,--description,--all-can-pin on|off,--only-admins-add on|off— andtg chats link show|reset, with the MCP toolstg_chats_update,tg_chats_link_show,tg_chats_link_reset.tg chats showadds a group's description, invite link and settings.tg chats create <title> [person...],tg chats join <link>,tg chats leave <chat>, and the MCP toolstg_chats_create,tg_chats_join,tg_chats_leave. A new group is always a supergroup (--channelmakes a channel); people who cannot be added are listed in the answer. See usage.- Permissions: one level per command, for you and for an AI agent alike. A profile's
permissionssetting gives each command path a level:deny(not even reading),readonly,askorallow; the most specific key wins —tg config set permissions.messages.delete allow. By default everything is allowed except deleting messages and ending other sessions, which ask.askasks y/N in the terminal;--allow-dangerous(deleting) or the new--yes(any other write) says yes in a script.readOnlyandallowstill work. See security. tg messages send --voice <file>sends an Ogg Opus file as a voice message, and a.mp4or.movgiven with--filenow plays in the chat as a video;--as-filekeeps it a file to download.tg messages list --mark-readmarks the chat read up to the newest message shown. Nothing else that reads marks anything read.--modelbeside--transcribeontg messages listandtg inbox, andtg review --transcribe: voice messages in a review come with their text.tg store fetch --last <n>stops once the newest n messages of the chat are held, so a later run with the same--lastasks Telegram for one page and stops.tg polls create --revotelets people change their vote.tg store export --output <file> --since-time <time>. The export goes into a new file only you can read, never over one, and can start from a time.tg account showprints the phone's last four digits, and the whole number with--show-phone. The MCP tooltg_account_showalways prints only the last four.tg messages forward --send-id. A forward that got no answer is repeated with the send id from the error, and Telegram keeps one copy, as with a send. The--jsonanswer carriessendId; MCP'stg_messages_forwardtakessend_id.tg messages edit --mdformats the new text asmessages send --mddoes; MCP'stg_messages_edittakesmarkdown.- Looking after the message store:
tg store info,check,migrate,backup,restore.infosays wheremessages.dbis, its size, its schema and how many rows it holds.checkreports whether it is healthy — integrity, foreign keys, the search indexes, free disk — and names every chat whose stored history stops before the chat's newest message; it repairs nothing.migratebrings the file up to this version and normalizes the messages stored before it.backup <file>copies the store while it is in use, readable by you alone, never over a file.restore <file>puts a backup in place and keeps the store it replaces beside it; it refuses whiletg serveruns or any process has the store open. The same file serves max-cli, so restart any runningserveormcpof either CLI afterwards. - Every write has its own id,
operationId. A send, edit, forward, deletion, pin, reaction, mark-read and poll vote prints it in its--jsonanswer and MCP result, and the send journal and--tracename it, so one write can be followed from the answer to the log. A send'soperationIdis itssendId. - About 16 MB less to install: cli-messaging 0.60.0 bundles its database layer instead of depending on it.
Changed — may break scripts
tg server status --jsonanswers the fields both tools share:sinceisstartedAt,listeningisconnected,listeningSinceisconnectedAt; new arecliVersion,log, andstalewhen aservethat is gone left its lock behind.tg server startanswersstartedAtandconnectedAtthe same way, andtg server stopsays who had started it (by). The lines say "connected" where they said "listening".tg messages send --atis now--at-time, as every option that takes a time names it.- The MCP tools' arguments carry their option's name:
tg_messages_listtakesbefore_id,before_time,after_id,after_time;tg_messages_contextbefore_n,after_n;sinceissince_timeintg_inbox,tg_reviewandtg_chats_events, whoseeventistype;tg_messages_sendtakesmdandat_time. - Options name the kind of value they take. The old names are refused as unknown options; there
are no aliases. The MCP tools' arguments do not change.
tg messages list --beforeis now--before-id;--afteris--after-idfor a message id and--after-timefor a time, so an id is never read as a time.tg messages context --beforeand--afterare now--before-nand--after-n.--sinceis now--since-timeintg inbox,tg review,tg chats eventsandtg store fetch.tg messages download --outputis now--output-dir.tg chats events --eventis now--type.
tg review --unansweredtakes a duration —4h,1d— not bare hours;--unanswered 4is refused. Without a value it is 24 hours, as before. MCP'stg_reviewstill takes hours.tg chats events --jsonprints{ items, page, limit, hasMore, chatId, since }:eventsmoved toitemsandmoretohasMore.tg server logs --jsonmovedlinestoitems.--jsonlis unchanged.- A
.mp4or.movsent with--fileplays in the chat as a video; it arrived as a file before. Add--as-fileto keep it a file to download. tg mcpoffers tools by the profile's permissions, not by flags. With the default settings an agent can now send, edit, forward, react, vote and mark read without--allow-send, and without a form; deleting shows you a form first (tg mcp --allow-dangerousskips it). To keep an agent read-only, give it a profile withreadOnly— mcp shows how.--allow-send,--allow-mark-readand--allow-deletedecide nothing now and print a warning;--confirm-sendstill shows every write in a form.tg messages deleteasks in the terminal when--allow-dangerousis missing, instead of refusing; with no terminal it is refused as before.tg store fetch --max <n>is gone;--limit <n>caps a run instead, in messages (1000 by default, as before), and--page-size <n>sets how many one request asks for (100 by default). The same names as max-cli's.--maxis not kept as an alias.- A poll made without
--revoteno longer lets people change their vote, as in max-cli; Telegram allowed it by default. Add--revoteto keep the old behaviour. tg polls voteandtg polls close --jsonprint{ operationId, poll }instead of the poll alone; read the poll from.poll. The MCP toolstg_polls_voteandtg_polls_closeanswer the same.tg runs list,tg sends listandtg recipients list --jsonprint{ items, page, limit, hasMore }instead of a bare array, as every other list does; read the rows from.items.--jsonlis unchanged.
Fixed
-
tg chats listno longer lists a pinned chat twice. With archived chats included, Telegram's pages brought the pinned chats again further down; on one account 8 of 1361 chats appeared twice. A pinned chat's title also matched itself as two chats, so typing it could be refused as ambiguous. -
tg server stopand Ctrl-C endserveandwatchcleanly. The serve went down before it could clean up, sotg server statusreported a leftover lock (stale) after every stop. -
tg serverin a development checkout leaves the installed tg's systemd unit alone. A checkout with its ownTG_STATE_DIRor store gets a unit of its own name; the installed tg keepstg-serve-<profile>.service. -
A chat you have left no longer shows in
chats list --offline. It drops out the next timetg chats listreads your whole chat list; its messages stay untiltg store clear --left, and a chat you rejoin comes back. -
Two refusals say what to do. Adding back someone who left or was removed, when you are not each other's contacts, now says to send them the invite link (
tg chats link show <chat>); naming a person by an id this account has never seen now says to use an @username, or to read a chat they are in first. -
An argument Telegram's library refused no longer repeats what you typed. The error said the library's own words, which could quote a chat's title or a link. It now says what kind of input was wrong where tg can tell — a chat you have not joined, a message or invite link, a phone number, a login code or password — and otherwise that Telegram refused an argument.
-
A conversation reads in English. Your own messages are
you, and day headings read26 September 2026; they were Russian. -
A chat or message tg cannot find is
not_found, and a chat of the wrong kind for the command isvalidation_error. They were an unknown failure with exit code 1 and the library's own words, which could repeat a chat's title. -
The "not logged in" error names your profile:
tg <profile> session start, as the other login hints already did. -
Downloads and exports get your usual file permissions again. Since the first release, opening a session made every file tg wrote afterwards readable only by you. The session file and its companions stay owner-only.
0.20.0 — 30.09.2026
What's new
- A message's sender keeps their @username in the local store, so
--from @nameand the coming conversation view can match a mention to the person. Takes effect with cli-messaging 0.57.0 or later; history already downloaded gains it the next time it is fetched. tg store fetch <chat> --since <time>stops once it reaches messages older than the time:2026-09-01, or2h/1dago.
Changed — may break scripts
Commands follow one naming standard: a noun, then a verb. The old names are gone, with no aliases — a script that uses one now fails with "unknown command" or "unknown option".
tg export <chat>istg store export <chat>,tg sync status [chat]istg store status [chat],tg backfill <chat>istg store fetch <chat>, andtg backfill list|status|cancelistg store jobs list|show|cancel.store fetchfetches by default;--estimateonly estimates.--paceis--pausethere and intg messages download --all.--maxkeeps its name: it counts messages.tg messages replyis gone:tg messages send <chat> [text] --reply-to <id>answers a message, and every send option (--file,--photo,--silent,--at, …) now works with it. Themsg:telegram/…form has no replacement; give the chat and the message id.tg chats readistg chats mark-read; the MCP tooltg_chats_readistg_chats_mark_read.tg recipients offistg recipients clear.tg update [--check]istg upgrade [--check], and the daily line about a newer version namestg upgrade.tg messages search <words…>names its argument<text…>; the search is unchanged.
0.19.0 — 30.09.2026
Fixed
- tg always exits once a command has finished. Once, a download printed its answer and then stayed
running for half an hour,
--timeoutor not. If anything is still open five seconds after a command is done, tg now names it on stderr and exits with the command's own exit code. Output still being written is waited for.
0.18.0 — 30.09.2026
Fixed
- A supergroup or channel first seen through one of its messages no longer loses messages to a deletion
in a private chat (cli-messaging 0.54.0). 0.16.0 left such a chat exposed because the store did not know
its kind yet; its
-100…id now says enough. - Messages a deletion elsewhere marked deleted by mistake come back the next time their chat is read
(
messages list,messages context, or an edit arriving live). A deletion newer than the read stays.
0.17.0 — 30.09.2026
What's new
tg messages download <chat> --allsaves every file of a chat — photos, documents, videos, voice notes — into--output, newest first. Cut short by--timeoutor Ctrl-C, it continues where it stopped the next time, and picks up newer messages too; where it got to is kept in a.download-<chat>.jsonbeside the files. Telegram's "wait N seconds" is sat out up to five minutes, and--pace(1 s) spaces the pages. A file name another message already took gets the message id in front; nothing is overwritten. (cli-messaging 0.53.0)
0.16.0 — 30.09.2026
Fixed
- A message deleted in a private chat or a basic group no longer marks other chats' messages deleted (cli-messaging 0.52.0). Telegram reports such a deletion without the chat, and the local store marked every stored message with that number deleted — channel and supergroup messages included. Messages already marked that way stay marked; their text is kept.
0.15.0 — 30.09.2026
Fixed
- A speech model on this machine no longer drops quietly spoken words. A quiet stretch in the
middle of a voice message was taken for silence and left out of the text; now it is heard, by
Parakeet and GigaAM alike. Voice messages a local model heard before are heard again the next time
--transcribeasks for them; Telegram's transcripts stay. (cli-messaging 0.51.0)
0.14.0 — 30.09.2026
What's new
Changing messages other people see — each through the send guard, as messages send is: a
read-only profile refuses, allow must name the permission, the recipient list and the hourly limit
apply where they count, and tg sends list records it without the text.
tg messages edit <chat> <id> [text]: the new text of your own message. Repeating the same edit changes nothing.tg_messages_editwithmcp --allow-send.tg messages forward <chat> <id> --to <chat> [--silent], checked against the chat it goes to. After an unknown outcome, look in that chat before forwarding again.tg_messages_forward.tg messages pin|unpin <chat> <id>, quiet unless--notify; in a one-to-one chat the pin is on your side only.tg_messages_pinandtg_messages_unpin.tg reactions add <chat> <id> <emoji>andtg reactions remove <chat> <id>; a reaction never counts toward the hourly limit.tg_reactions_addandtg_reactions_remove.tg chats read <chat> [--until id]marks a chat read — the other side sees it. Its tool,tg_chats_read, comes only with the newtg mcp --allow-mark-read, which--allow-senddoes not turn on.tg messages delete <chat> <id…> --allow-dangerous [--for-everyone]: at most 10, for you only unless--for-everyone, and nothing without--allow-dangerous. In a supergroup or a channel Telegram has no "for me only", so there it needs--for-everyone. The newtg mcp --allow-deleteofferstg_messages_delete, which only ever deletes your own copy.tg polls show|vote|close|create: a poll with its answer ids, a vote by those ids (never by position) or--retract, closing your own poll, and a new one — public unless--anonymous, with--send-idfor a safe retry.tg_polls_showreads;tg_polls_vote,_closeand_createcome with--allow-send.
0.13.0 — 30.09.2026
Changed — may break scripts
- The shared message store moves to version 6 (cli-messaging 0.49.0). The first
tgrun upgradesmessages.db; amaxolder than the one released the same day then refuses it and asks to be upgraded —npm install -g @wirecat/max-cli@latest. Nothing intg's own commands changes.
0.12.0 — 30.09.2026
What's new
tg chats inspect <link>andtg_chats_inspect: what an invite or public link leads to — title, members, description, whether you are in it and whether joining needs approval — without joining.tg topics list <chat>andtg topics search <chat> <text>, andtg_topics_list: a forum group's topics, paged, with the id each message in a topic carries asthreadId.
0.11.0 — 30.09.2026
What's new
- Voice messages carry their text in
tg messages listandtg inbox. A transcript heard once is kept per profile in tg's cache and shows on every later read —transcriptin--json,🎤 …under the text for a person.--transcribehears the rest, by Telegram or the model on this machine, within two minutes for the whole list; what is left is inunheard. The same astranscribeontg_messages_listandtg_inbox. tg chats members list <chat>andtg_chats_members: a group's members, paged, each with a role and when Telegram last saw them — up to Telegram's own 10 000.tg contacts lookup: who has a phone number, where their privacy lets you find them. The number is piped in or typed when asked, never an argument. Alsotg_contacts_lookup.tg contacts sync: your Telegram contacts into the local store, answering how many were new or changed.tg account sessions listandtg_account_sessions: every device and app logged in to the account, without their IP addresses. It ends nothing.
0.10.0 — 29.09.2026
What's new
-
Voice to text on this machine.
tg models audio listandtg models audio download <id>fetch a speech model once — Parakeet v3 (25 languages, the default), GigaAM v3 or GigaAM v3 CTC (Russian) — into~/.cache/cli-common/models/audio, a folder every CLI of the family shares.tg messages transcribeasks Telegram first and falls back to the local model when the account has no Premium;--localor--model <id>skip Telegram. The profile'stranscribeWith(auto,messenger,local) andspeechModelset the defaults. Nothing downloads a model by itself. -
tg messages send --photo <path>or--file <path>, the text as the caption, andphotoandfileontg_messages_send. Hidden files and folders,~/.ssh, tg's own folders and the message store are refused unless the owner adds--allow-any-file; over MCP there is no way around it. The send journal records the attachment's kind and size, never its name. A retry with the same--send-idsends one message (measured on a photo). -
tg updaterestarts a running server with the new tg, so it stops running the old code; a serve started by hand is named, for you to restart.tg server statussays when the running serve is older than tg, as max-cli's does. -
tg chats events <chat> [--since] [--event]andtg_chats_events: who joined, left, was added or removed, and by whom — plus a chat created, renamed or a message pinned — from the chat's service messages, seven days back by default. At most ten pages of history a run;moresays there was more.
0.9.0 — 29.09.2026
What's new
tg session startsays who logged in, where the session file is, where the app keys are read from and what to run next, in sentences;--jsongainssessionandappKeys(environment,keyringorfile— never the keys).tg chats list --search <text> --kind <kind> --unread, and the same ontg_chats_list. The filters combine over the newest 200 chats;--searchtakes at least 3 characters.tg messages list --after <id-or-time>reads a chat forward: the oldest messages newer than a message id, or than a time (2h,1d, ISO 8601).afterontg_messages_list.tg messages send --silent --no-preview --md— without a notification, without a link's preview card, and with**bold**,_italic_,~~struck~~and`code`as Telegram formatting. The MCP send tool takessilent,no_previewandmarkdown. The send journal still holds only the length.tg messages send --at <time>hands the message to Telegram to send later —2h,1d, or2026-10-01T09:00in local time — andtg messages scheduled <chat>(MCPtg_messages_scheduled) lists what waits. A scheduled send is never repeated:--send-idis refused with it.
Changed — may break scripts
tg service …is nowtg server …—start|stop|restart|status|logs|install|uninstall, as in max-cli — andtg serve statusis gone:tg server statusanswers.tg server startwithout a unit runs serve in the background. A unit written bytg service installis still found. From cli-messaging 0.40.0.
0.8.0 — 29.09.2026
What's new
tg review: every message, yours too, in each chat that changed since--since(three days without it) — for sorting out who owes what. It ends by saying where the next review starts.--chatreads one chat,--unanswered [hours]keeps the questions nobody answered — a group's admins answer for it too — and--alltakes in muted and archived chats. The MCP tooltg_reviewand thereviewprompt do the same.
0.7.0 — 29.09.2026
What's new
tg messages transcribe <chat> <id>and the MCP tooltg_messages_transcribeturn a voice or video note into text with Telegram's own recognition — on a Premium account, or within Telegram's weekly free trial. Telegram usually needs a few seconds; tg asks again for up to a minute, then answers"pending": true. Refusals say why in plain words: not a voice message, too long, no Premium.- The MCP tool
tg_messages_photohands an agent a message's photo as an image to look at, up to 512 KB. A larger photo, a file, a video or a voice note is refused with thetg messages downloadcommand that saves it.
0.6.0 — 29.09.2026
What's new
tg inboxleaves out muted and archived chats unless they mention you or reply to you;--all(andallontg_inbox) shows them too. On a busy account most unread chats are muted, and they took the 20 chatsinboxreads at once. The JSON'squietcounts what was left out.- A chat carries
muted,archivedandunreadMentionsin--json.archivedmoved out ofproviderMetadata;mutedis absent when the chat follows the account's default.
Fixed
tg messages send --silent,--no-previewand--markdownrefuse the send instead of sending without them: they came with cli-messaging 0.32, and tg does not carry them to Telegram yet.
0.5.0 — 29.09.2026
What's new
tg service install|uninstall|start|stop|status|logsrunstg serveas a systemd user unit (Linux) or a launchd agent (macOS), one per profile.installonly writes the file; nothing starts untiltg service start.tg backfill <chat> --backgroundruns a backfill as a job that outlives the command;tg backfill list,status [job]andcancel <job>follow it. Ctrl-C orcancelstop a backfill after the page in hand, and it keeps that page.tg backfill <chat> --estimate— how many messages, requests and seconds a full backfill would still take, from the store; it asks Telegram nothing.tg export <chat> --format markdown— a chat as a transcript a person reads.tg messages search --regex '<pattern>'— a regular expression over the stored text.tg doctor report createwrites a problem report — versions, paths, the failed run, the recent send attempts — with no message text, and every chat, message and account id replaced by a label.tg session start --qr-file login.pngwrites the login QR code as a PNG instead of drawing it, so an agent can pass it on, and removes it after the login. With the app already stored it needs no terminal.tg messages download <chat> <id> [--output dir]saves a message's photo, file, video or voice note into a folder — the current one unless--outputnames another — and answers its path and size. A name the sender chose cannot leave the folder or hide the file, and a file already there is never overwritten. The message is fetched again each time, so an old one still downloads.
Fixed
tg messages list --jsonlandtg messages search --jsonlprint one message per line, as their--helpsays. They printed the whole page as one JSON line; a script that read.itemsfrom it must now read each line as a message.
0.4.0 — 29.09.2026
What's new
tg inbox— other people's unread messages in every chat;--newshows only what arrived since the last check, each message once. The MCP server offers it as thetg_inboxtool and thecatch-upprompt.tg skill showprints the instructions an agent is given for this tool.- MCP prompts and a chat resource: the
replyandfindprompts, andtg://chat/{id}.
0.3.0 — 28.09.2026
What's new
tg mcpserves a profile to an agent over MCP, on stdin and stdout. Read-only by default;--allow-sendoffers the send tool, and--confirm-sendshows the owner every send first.tg mcp configprints the entry for an MCP client's settings.
Changed — may break scripts
- A failure before a command runs is kept as a run — a usage error, a configuration that will
not load.
tg runs listshows it;--no-recordturns it off.
0.2.0 — 28.09.2026
What's new
tg updateupdates tg with the package manager that installed it;--checkonly looks.- A daily line on stderr when a newer version is on npm, at a terminal only and after the
command.
TG_NO_UPDATE_CHECK=1turns it off.
0.1.0 — 27.09.2026
The first release on npm.
What's new
- Log in by QR code or phone number (
tg session start); the app credentials from my.telegram.org are fetched by opening the site or by filling it in for you (--app auto), and kept in the OS keyring. - Read:
account show,chats list|show,contacts list|show,messages list|show|context. - Send with
messages sendandmessages reply, through a send guard: a recipient list, read-only profiles, a journal of every attempt (tg sends), and--send-idto repeat a send whose outcome is unknown without sending it twice. - A local archive: every read is kept in a store shared by the messenger CLIs;
--offlineanswers from it,messages searchsearches it,backfillfills it,watchandservekeep it current,sync statusandexportread it. - Run records (
tg runs),config,doctor,commandsand shell completion (complete).