tg-archive

A tool for exporting Telegram group chats into static websites like mailing list archives.

Runs with mockssource: GitHubPythonMITcommit b8f3febaad11

Python, MIT licensed. The project labels itself: exporter, static site, static site generator, telegram, telegram api and telegram export.

tg-archive runs, with stand-ins for the services it depends on. An Argusic agent installed it in 7 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

The tg-archive CLI installs, reports its version (v1.3.1), scaffolds a new site, and builds a static archive (valid HTML, RSS and Atom feeds, reply links) from a schema-correct SQLite database; only the live Telegram sync step could not be verified because it requires real my.telegram.org account credentials.

What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 56 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs with mocks
Argusic Score
56 / 100
cost of the verifying run
$0.04 (measured)
recorded runs
2
last tested
stars
1,172
forks
169
open issues
32
watchers
14
size
0 MB
created
last push

Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

Time lost to each failure while testing tg-archive, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • ImportError: failed to find libmagic when running tg-archive --build (system libmagic.so.1 missing; no root to apt install)6 minutes
Install time
7 minutes
Cold machine to finish
8 minutes
Errors hit and fixed
1 hit, 1 fixed with no human help
How the result was proved
tg-archive --version => v1.3.1; tg-archive --build on seeded data.sqlite exited 0 and logged 'published to directory site'; xml.etree.ElementTree.parse succeeded for site/index.xml and site/index.atom (3 entries); grep confirmed 'Hello world' and 'Reply to #1' in the rendered HTML
Model tokens used
49,376
Exact commit tested
b8f3febaad11
Container image
sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory
this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run
each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Behaviour against real services
this run was verified against stand-in services only

Watch the session

The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.

A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

- One error encountered and fixed: `ImportError: failed to find libmagic` (system `libmagic` missin…
- `--build` on a schema-correct seeded DB → published `2024-01.html`, `2024-02.html`, `index.html`,…
- `--sync` requires real Telegram API credentials — it reached Telethon's `client.start()` promptin…
exec
/bin/sh -lc "date; python3 -c \"print('started ~05:47, now', __import__('time').time())\"" in /work…
 succeeded in 0ms:
Sat Oct 10 05:53:57 UTC 2026
started ~05:47, now 1791611637.5616813
I have all the evidence I need. Here's my final report.
tokens used
49,376
I have all the evidence I need. Here's my final report.

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

  • Installed in 7 minutes.
  • Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What did not, or is not known

  • Only reached a running state against stand-in services, so nothing here proves it works against the real ones.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs with mocks92.000.04
Argusic Runner1/3Did not run20.000.17

Topics (from GitHub)

exporterstatic-sitestatic-site-generatortelegramtelegram-apitelegram-export

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/tg-archive.svg)](https://argusic.com/subject/tg-archive)

Questions

Does tg-archive run?
tg-archive runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 7 minutes, hitting 1 error on the way, and recorded the session.
How did Argusic test tg-archive?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b8f3febaad11. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test tg-archive?
The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does tg-archive take to install?
7 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does tg-archive need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing tg-archive?
1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for tg-archive?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion