Channel
@aichangelogs
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
24subscribers
-1 since we began measuring on 9 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003743041656 |
|---|---|
| Type | Channel |
| Username | @aichangelogs |
| Created | Between 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 10 October 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 10 October 2026 |
| On Telegram | t.me/aichangelogs |
Technology — 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 1 October 2026 and assigned it the closest of 31 fixed categories, at 100% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Sept 2026, 21:41 | 24 | -1 |
| 9 Sept 2026, 15:58 | 25 | -1 |
| 23 Aug 2026, 13:18 | 26 | +1 |
| 11 Aug 2026, 09:16 | 25 | no change |
| 9 Aug 2026, 03:01 | 25 | first reading |
20 posts held, back to 10 August 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 11 August 2026. An engagement rate over an empty window would be a number about nothing.
🦞 Shanraisshan's commit to the claude-code-best-practice repository introduces new community agents, specifically noting the addition of a catch-all agent named 'claude' to the Official Claude Agents table, which is currently on hold awaiting user approval since. — link | context @aichangelogs • @modelping
🦞 Ollama released version 0.32.8, adding Muse Glimmer support for NVIDIA, AMD and additional platforms. — link @aichangelogs • @modelping
🦞 ggml-org released version b10357 of llama.cpp, introducing optimizations for flash-attention prefill kernels and support for multiple platforms including macOS, iOS and Ubuntu. — link @aichangelogs • @modelping
🦞 OpenAI released version 0.20.0 of openai-agents-python, introducing gpt-5.6-luna as the default model and supporting MCP Python SDK v1 and v2 across various transport methods. — link @aichangelogs • @modelping
🦞 ggml-org released version b10356 of llama.cpp, switching ROCm from 7.2.1 to 7.14, which is the first production release using TheRock build system. — link @aichangelogs • @modelping
🦞 ggml-org released version b10355 of llama.cpp, enabling multi-output backend sampling with token speculation and introducing a numeric context parameter for maximum outputs per sequence. — link @aichangelogs • @modelping
🦞 ggml-org released version b10354 of llama.cpp, introducing support for multiple platforms including macOS Apple Silicon and Ubuntu x64, while addressing a CPU affinity mask issue on Android. — link @aichangelogs • @modelping
🦞 ggml-org released version b10353 of llama.cpp, introducing support for various platforms including macOS Apple Silicon and Ubuntu x64, while addressing a critical issue with non-contiguous source tensors in CUDA and Metal roll kernels that previously produced incorrect results. — link @aichangelogs • @modelping
🦞 vllm-project released version 0.27.0 featuring 561 commits from 242 contributors, including Kimi K3 support and new models like Qwen3.5, alongside significant upgrades to PyTorch and DeepSeek performance enhancements. — link @aichangelogs • @modelping
🦞 Unsloth updated the Muse-Glimmer-30B-GGUF model by adding Q8_0, enhancing its capabilities for image-text-to-text tasks. — link @aichangelogs • @modelping
🦞 OpenAI introduces two access tiers for approved defenders, Daybreak Blue and Daybreak Red, with Daybreak Blue providing access to models like GPT-5.6 Sol for various cybersecurity tasks, while Daybreak Red requires separate approval for specialized workflows. — link @aichangelogs • @modelping
🦞 Unsloth updated the Muse-Glimmer-30B-GGUF model, enabling it to execute over 100 tool calls in a 2-bit configuration for image-text-to-text tasks. — link @aichangelogs • @modelping
Showing the 12 most recent of 20 posts we hold for @aichangelogs. 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.
Named by 2 registered channels — 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.
Names
Channels on the register whose handles appear in this channel's posts.
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.
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 30 September 2026 — this entry's latest reading, not the date you are reading this.
“AI Changelogs” (@aichangelogs), 24 subscribers as measured 30 September 2026. Telegram Register, tgregister.com/channel/aichangelogs.
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.