Telegram RegisterThe public register of Telegram
Telegram profile photo for SimpleAGI

Channel

SimpleAGI

@simple_agi

On this record: Topic · Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry

296subscribers

+10 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002601386160
TypeChannel
Username@simple_agi
CreatedBetween 1 March 2025 and 31 July 2025 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live19 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/simple_agi

Topic

Memes & entertainment — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 23 September 2026 and assigned it the closest of 31 fixed categories, at 64% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.

Growth

2862962916 August 2026 — 286 subscribers6 August 2026 — 286 subscribers13 August 2026 — 288 subscribers21 August 2026 — 289 subscribers27 August 2026 — 291 subscribers3 September 2026 — 293 subscribers11 September 2026 — 292 subscribers19 September 2026 — 296 subscribers6 August 202619 September 2026
8 measurements spanning 44 days, net +10. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 285–298 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
19 Sept 2026, 07:38296+4
11 Sept 2026, 20:39292-1
3 Sept 2026, 21:58293+2
27 Aug 2026, 18:24291+2
21 Aug 2026, 02:08289+1
13 Aug 2026, 03:27288+2
6 Aug 2026, 23:17286no change
6 Aug 2026, 04:32286first reading

Engagement

20 posts held, back to 9 June 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 5 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

77 reactions across 19 posts, in 12 distinct kinds. The most used accounts for 32.5% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤2532.5%
🔥1924.7%
😁1722.1%
custom 522674883727564138745.19%
custom 522422240007317930833.90%
😱22.60%
🤩22.60%
custom 546781030632968080511.30%
❤‍🔥11.30%
🤡11.30%
🤣11.30%
🤬11.30%

Custom emoji. 3 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 77 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 9 June 2026 to 5 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Telegram Stars

Stars received
1
across the posts below
Posts paid on
1
of 20 we hold a reading for · 5%
Most on one post
1
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @simple_agi. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 20 most recent posts we hold for this entry, published 9 June 2026 to 5 August 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

5 Aug 2026, 10:49 UTC72 views6 reactions1 Starread 6 August 2026
Photo

Когда неделя начинается не в Понедельник ⌨️

😁4❤1🤣1

4 Aug 2026, 01:10 UTC97 views7 reactionsread 6 August 2026
Photo

Всё же как любопытно переносить со сферы на сферу типовые модели рассуждений. Это работает очень хорошо и комично) у меня почему-то флешбеки🐆 #meme

😁6custom 54678103063296808051

1 Aug 2026, 19:33 UTC136 views4 reactionsread 6 August 2026

Ревью своего кода субагентом - это ревью самим собой. Просто с чистым контекстом. Контекст свежий, да. Модель та же. Училась на том же, ошибается там же. Слепые пятна автора она наследует целиком - потому что она и есть автор. Ага. А ревьюер другого вендора - нет. В claude-code-harness v1.20.0 добавил интеграцию с Codex CLI. Он подключается к Claude Code как MCP-сервер. Кит отдаёт не совет «позови вторую модель», …

❤4

31 Jul 2026, 15:33 UTC139 views2 reactionsread 6 August 2026
Photo

Подключил codex через mcp к Claude code и теперь у меня полноценно отрабатывает Review этап с не то, что агентом с чистым контекстом, а другим семейством моделей. Нужно будет оформить этот апдейт в claude-code-harness

custom 52242224000731793082

30 Jul 2026, 19:52 UTC153 views2 reactionsread 6 August 2026
Photo

Открыл рядом два окна с лимитами подписок. И залип. OpenAI: "Осталось 72%". Anthropic: "25% used". Смысл один, формулировка зеркальная. И полоска работает наоборот: у OpenAI закрашено то, что ещё есть, у Anthropic - то, что уже сжёг. Один и тот же синий прямоугольник означает противоположные вещи. Стакан наполовину полон против стакана наполовину пуст, только в биллинге. Просто забавный момент, как ребята старают…

😁2

27 Jul 2026, 13:38 UTC176 views1 reactionsread 6 August 2026
Photo

Появилась возможность потрогать Codex с нормальными лимитами. У меня он совсем ванильный и без всяких harness примочек. Дай, думаю, попробую переписать архитектурные блоки проекта из состояния "Нужно, чтоб работало хоть как-то" в приличную модульную структуру, чистенько. Сессии 2 ушло на формирование плана и всяких особенностей. Потом несколько сессий на подготовительные работы и сбор анамнеза пациента😫 И вот он с…

❤‍🔥1

26 Jul 2026, 00:29 UTC165 views1 reactionsread 6 August 2026

Продолжение истории с effort и WebSearch. В claude-code есть issue #79798: alwaysThinkingEnabled не превращается в thinking: {type: "adaptive"}. Сессия молча идёт без thinking, а на xhigh WebSearch падает с 400. Весь тред до этого был про Opus 4.8, Windows Desktop и macOS. Написал туда большой комментарий. Что он добавляет: Opus 5 в scope. Теперь у мейнтейнеров есть репро на текущей дефолтной модели и на 2.1.220 -…

❤1

25 Jul 2026, 20:38 UTC257 views3 reactionsread 6 August 2026

На Opus 5 любая сессия выше high(effort) теряет WebSearch — включая ultracode и /effort max. Держу в курсе

❤2😁1

20 Jul 2026, 18:25 UTC171 views7 reactionsread 6 August 2026
Forwarded from @evilfreelancerPhoto

Как и обещал, выкладываю самый полный курс про Cursor AI Собирал несколько недель. 14 модулей, почти 70 уроков. Начинается с установки и оплаты из России, заканчивается автономными агентами, которые сами доводят задачу до конца. Что разбираем: - как устроен агент, токены, контекст, цикл с инструментами; - работа в IDE, Tab, Ctrl+K, чат, композер, режимы и модели; - контекст, правила проекта, MCP-серверы; - скиллы, …

🔥4❤2🤡1

17 Jul 2026, 17:49 UTC215 views5 reactionsread 6 August 2026

Posted without readable text

custom 52267488372756413874❤1

17 Jul 2026, 05:52 UTC210 views13 reactionsread 6 August 2026
Photo

Давно обещаю выложить наработки по harness для Claude Code. 🥺 Два плагина. Одна репа. claude-code-harness - проектирует и аудирует .claude/ в проекте. Удаляет так же охотно, как добавляет: показываешь ему свой .claude/ - получаешь список мёртвого груза. devlog - память проекта между сессиями. Новая сессия открывается не холодной, а с последними записями и незакрытой работой. Даже презентацию сделал - ссылка .

❤8🔥3🤩2

Showing the 12 most recent of 20 posts we hold for @simple_agi. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked ≈ was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Forward network

Republishes

Channels on the register whose posts this channel has forwarded.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 19 September 2026 — this entry's latest reading, not the date you are reading this.

“SimpleAGI” (@simple_agi), 296 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/simple_agi.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.