Telegram RegisterThe public register of Telegram
Telegram profile photo for Fabelis

Channel

Fabelis

@fabelisAI

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

222subscribers

-2 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-1002253789327
TypeChannel
Username@fabelisAI
CreatedBetween 1 October 2024 and 10 January 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live30 August 2026
Measurements held4
Confirmed unchanged2 times, most recently 30 August 2026
On Telegramt.me/fabelisAI

Growth

2222242237 August 2026 — 224 subscribers8 August 2026 — 224 subscribers14 August 2026 — 223 subscribers22 August 2026 — 222 subscribers7 August 202622 August 2026
4 measurements spanning 15 days, net -2. 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 222–224 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
22 Aug 2026, 22:53222-1
14 Aug 2026, 21:55223-1
8 Aug 2026, 10:31224no change
7 Aug 2026, 14:39224first reading

Engagement

20 posts held, back to 10 January 2025the 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 1 May 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
3m 56s
Average length
3m 56s

Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Reaction mix

105 reactions across 14 posts, in 6 distinct kinds. The most used accounts for 44.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥4744.8%
👏2221.0%
1918.1%
👍1110.5%
43.81%
👎21.90%

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 14 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 105reactions 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 10 January 2025 to 1 May 2025, 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

1 May 2025, 06:07 UTC611 views17 reactionsread 8 August 2026

Refining our craft, pushed a sizeable update to our mcp-core repo https://github.com/stevohuncho/mcp-core/tree/main - support for 2025.03.26 spec plus option to switch to older protocol for servers and clients - mcp-core-macros tool_param! annotations testing and examples - more in depth cargo doc updates Note: mcp-core lives in our lead engineer's main repo for broader visibility

🔥13👏31

29 Apr 2025, 20:28 UTC618 views9 reactionsread 8 August 2026

We've heard your requests to open this tg up to the public and are in the process of getting a moderator to do just that!

5👏4

21 Apr 2025, 13:29 UTC≈1,040 views21 reactionsread 8 August 2026

We've got a few partner integration across the complex in the works as well!

👍10👏432🔥2

21 Apr 2025, 13:28 UTC≈1,010 views16 reactionsread 8 August 2026

Updating our roadmap shortly with a feature release!

👏11🔥5

6 Mar 2025, 09:33 UTC≈1,750 views24 reactionsread 8 August 2026

Working on some game changing PRs for RIG, should have an update on that shortly!

🔥193👎2

3 Mar 2025, 23:00 UTC≈1,660 viewsread 8 August 2026

Check out our new repo https://github.com/fabelis/mcp-core and our updated docs https://docs.fabelis.ai Tune in to our twitter post coming up shortly for a better overview and some cool technical demos. An in-depth README is also on its way. This is the start of an exciting chapter for Fabelis, expect updates to be in the form of days not weeks!

3 Mar 2025, 23:00 UTC≈1,420 viewsread 8 August 2026

Market down, project down? I don't think so! 🗣🚨 We've been hard at work revitalizing the vision for Fabelis with a new massive update. tl;dr The team at Fabelis has honed in on exploring the frontiers of the model context protocol (MCP for short). A new technology spearheaded by anthropic with the goal of arming AI agents to accomplish real-life tasks. You've probably seen Claude Desktop... Imagine Claude Desktop p

30 Jan 2025, 20:22 UTC≈1,390 views3 reactionsread 8 August 2026

Imagine if we used agents for real-life workloads? Coming soon....

🔥3

30 Jan 2025, 20:21 UTC≈1,250 viewsread 8 August 2026

https://github.com/fabelis/agent/releases/tag/v0.6.0 Tackled two whales at once! We added: - Deepseek completion to Fabelis - Docker support These are both live at https://fabelis.ai/playground We got this quick update out, but there are some serious game changing updates coming soon!

23 Jan 2025, 02:54 UTC≈1,120 viewsread 8 August 2026

Find our new section, the "playground" here: https://fabelis.ai/playground

23 Jan 2025, 02:53 UTC≈1,210 viewsread 8 August 2026

It's here! Our latest release now includes an expanded section of our website with a brand new dashboard! https://github.com/fabelis/agent/releases/tag/v0.5.0 We have deployed a massive new feature reminiscent of character.ai but built leveraging the flexibility of Fabelis and the power of rig.rs! We will be adding a ton of features to this new section and looking to collaborate with other members of the complex a

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

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

“Fabelis” (@fabelisAI), 222 subscribers as measured 22 August 2026. Telegram Register, tgregister.com/channel/fabelisAI.

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.