Telegram RegisterThe public register of Telegram

Channel

AI и разработка | Кейсы, грабли и ИИ...

@ai_in_dev

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

178subscribers

+0 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002062513059
TypeChannel
Username@ai_in_dev
DescriptionКомьюнити о практическом применении ИИ в разработке. LLM, агенты, Cursor, LangChain, кейсы, вебинары и вот это вот всё. Про нас — https://spectr.dev/ Учиться — https://ai-academy.spectr.dev/ По сотрудничеству — в ЛС канала
CreatedBetween 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live8 August 2026
Measurements held2
On Telegramt.me/ai_in_dev

Growth

1787 Aug 2026, 19:16 — 178 subscribers8 Aug 2026, 13:30 — 178 subscribers7 Aug 2026, 19:168 Aug 2026, 13:30
2 measurements taken within a single day. 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 177–179 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Aug 2026, 13:30178no change
7 Aug 2026, 19:16178first reading

Engagement

20 posts held, back to 13 February 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 21 May 2026. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
43
Videos
3
Links
31

Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Reaction mix

25 reactions across 8 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
👍25100.0%

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 8 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 25reactions 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 13 February 2026 to 21 May 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.

Recent posts

21 May 2026, 08:55 UTC109 views3 reactionsread 8 August 2026

Начинаем трансляцию про применение ИИ у застройщиков В гостях — Сергей Михеев, ИТ-директор в «Ак Барс Дом» Если тема для вас актуальна, подключайтесь к трансляции по ссылке: https://vkvideo.ru/video-137384692_456239243 Можно задавать вопросы в чате трансляции

👍3

20 May 2026, 09:53 UTCviews —

AI и разработка | Кейсы, грабли и ИИ... pinned a photo

13 May 2026, 08:32 UTC139 views5 reactionsread 8 August 2026
Photo

Применение ИИ у застройщиков, опыт «Ак Барс Дом» 21 мая проведем эфир с ИТ-директором девелоперской компании и поговорим, как внедряется ИИ: какие задачи с его помощью пытаются решать, что работает, а что — нет Гость — Сергей Михеев, ИТ-директор в «Ак Барс Дом» 🗓 21 мая, 12:00 мск, Четверг 💻 ОНЛАЙН На примере опыта девелопера «Ак Барс Дом» разберём, как AI внедряется в компании: где он уже применяется, есть ли от

👍5

10 May 2026, 10:34 UTC116 viewsread 8 August 2026

Zed показывает, зачем редактору несколько агентных тредов 22 апреля 2026 в stable Zed 0.233.5 появились parallel agents, а блог Zed отдельно разложил UX: Threads Sidebar, несколько потоков в одном окне и навигация между проектами и worktree. Stable release · Blog Смысл не в слове “multi-agent”. Одна длинная AI-сессия быстро превращается в свалку контекста. Здесь можно разнести изолированные куски работы: один агент

9 May 2026, 10:31 UTC111 viewsread 8 August 2026

Локально начать, в облако отдать Windsurf сейчас собирает гибридный workflow в одну цепочку. 15 апреля 2026 в Windsurf 2.0 в редактор добавили Devin Cloud, а 28 апреля 2026 в Windsurf 2.1.29 появились Devin for Terminal и Devin Local. Сценарий понятный: начать задачу рядом с кодом и терминалом, а длинную часть передать в облако, где у агента своя VM, тесты, video recordings и autofix. Changelog · Docs Практический

8 May 2026, 10:26 UTC103 viewsread 8 August 2026

Почему Codex идет в AWS 28 апреля OpenAI и AWS открыли limited preview для OpenAI models on AWS, Codex on Amazon Bedrock и Managed Agents. Для Codex публично заявлены Codex CLI, desktop app и VS Code extension: доступ через AWS credentials, inference через Bedrock. OpenAI · AWS Смысл не в самом анонсе. Для enterprise agentic coding упирается не только в модель, но и в контур запуска: где живут доступ, биллинг и сог

6 May 2026, 10:05 UTC114 viewsread 8 August 2026

Cursor делает security review постоянным слоем 30 апреля 2026 года Cursor запустил в бете Security Review для Teams и Enterprise. Внутри два always-on агента: Security Reviewer проверяет каждый PR, а Vulnerability Scanner гоняет плановые сканы по кодовой базе. Security Reviewer ищет не только уязвимости, но и auth-регрессии, privacy и data-handling риски, auto-approval агентных тулов и prompt injection. Vulnerabili

6 May 2026, 07:35 UTC≈1,460 views4 reactionsread 8 August 2026

Запись вебинара «Искусственный интеллект в автотестировании: опыт QA Automation Tech Lead» VKVideo: https://vkvideo.ru/video-137384692_456239241 YouTube: https://www.youtube.com/watch?v=mN_N4q5Y6eE Спикером вебинара выступил Олег Пендрак — Tech Lead QA Automation в СберЗдоровье и лидер сообщества ThreadQA. Олег поделился своим опытом применения ИИ и прямо на вебинаре продемонстрировал конкретные примеры сценариев п

👍4

5 May 2026, 11:55 UTC97 views3 reactionsread 8 August 2026

Cursor переводит плагины в командную настройку Cursor обновил Team Marketplace: теперь админ может создать его без привязки к репозиторию и прямо в настройках задать режим установки для first-party plugins. В changelog от 1 мая перечислены три режима: Default Off, Default On и Required. Это важно не только как удобство. Плагин в Cursor может упаковывать MCP-серверы, skills, subagents, rules и hooks, то есть команда

👍3

5 May 2026, 09:58 UTCviews —

AI и разработка | Кейсы, грабли и ИИ... pinned a photo

5 May 2026, 09:58 UTC101 views2 reactionsread 8 August 2026
Photo

ТРАНСЛЯЦИЯ ВЕБИНАРА «Искусственный интеллект в автотестировании: опыт QA Automation Tech Lead» Подключайтесь по ссылке: https://vkvideo.ru/video-137384692_456239241

👍2

4 May 2026, 12:57 UTC105 views2 reactionsread 8 August 2026
Photo

Cursor SDK выводит агента в код 29 апреля 2026 Cursor открыл в public beta TypeScript SDK. Того же агента из приложения, CLI и web теперь можно вызывать из своего кода через @cursor/sdk. Модель простая: local работает в вашем cwd, cloud запускает задачу в выделенной VM Cursor, а run.stream() отдает события по ходу run. Для cloud-run Cursor отдельно обновил streaming, cancellation и lifecycle control. Практический

👍2

Showing the 12 most recent of 20 posts we hold for @ai_in_dev. 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.

Citation-graph rank

Citation-graph rank — 668,993 of 1,169,250entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 8 August 2026 — this entry's latest reading, not the date you are reading this.

“AI и разработка | Кейсы, грабли и ИИ...” (@ai_in_dev), 178 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/ai_in_dev.

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.