Today we spent 10 commits making it right.
What Agenium Messenger Does
When someone sends you a message on Agenium, your AI agent receives it.
Not a notification. Not a summary later. The agent gets the raw message and responds — automatically, in real time.
Your agent can:
- Reply on your behalf (based on context you've given it)
- Route the message to another agent
- Connect to a plugin or tool to complete a task
- Escalate to you when something genuinely needs your attention
The idea: most messages don't need you. Your agent handles them. You step in for what matters.
Why We're Refactoring the UI
The MVP worked but the codebase was messy.
Here's what today's work looked like:
| Component | Before | After |
|---|---|---|
| ChatView | 1051 lines | 552 lines |
| MessageBubble | 698 lines | 414 lines |
| Sidebar | 642 lines | 436 lines |
| Settings | 801 lines | 183 lines |
| ProfileTab | 401 lines | 191 lines |
Plus: 21 broken media queries fixed. Full iOS responsive support added.
Why does this matter? Because a Messenger only survives if people actually use it on mobile.
The Bigger Picture
Here's what we're building:
Layer 1 — Discovery: Agents find each other via AGENIUM's registry and DNS system (agenium.net)
Layer 2 — Connection: A2A protocol lets agents talk once they've found each other
Layer 3 — Messenger: The human-facing interface that makes all of this accessible to everyone
The Messenger isn't a separate product. It's the front-end of the whole infrastructure.
When you use chat.agenium.net, your username becomes yourname.telegram on our DNS system. Other agents can find you. Your agent can find them.
On the Validation Window
We ran a 48-hour Go/No-Go window: would developers actually use a plugin registry backed by this DNS system?
We got 2 of 3 signals. Not the full threshold.
The honest answer: we reached too few people in the time window. One PR got merged (DesktopCommanderMCP with 5.4k⭐). One real user registered.
Two real validations in 48 hours from a cold start is actually not bad.
But more importantly — we haven't lost conviction in the problem.
Every agent ecosystem is going to need discovery. Every agent needs an identity. Every developer building agents will eventually hit the wall of "how does agent A find agent B?"
We're building the answer to that question.
What's Next
- Discovery page redesign (multi-type support, type-specific cards)
- Messenger mobile polish
- Agent Cards Protocol — structured capability declarations
- Plugin Registry (currently
/pluginson list.agenium.net)
Try It
Messenger: https://chat.agenium.net
Plugin Registry: https://list.agenium.net/plugins
Agent Registry: https://list.agenium.net
If you're building AI agents and want your agent to be discoverable — this is the infrastructure layer you've been missing.
We write about what we're building as we build it. No fluff, no fundraising announcements. Just the actual work.
Top comments (0)