What a day: @weegyman from @byte5ai gave me the first glimpse of a working demo of our new generative UI.
It's fricking awesome! An AI-native GUI!
Not another chat client, this is totally different.
And it will soon be part of omadia.ai
Ha, turns out the fix for agents that can't count is embarrassingly old: a calculator. But this is a full spreadsheet, in memory, never rendered. The model thinks, the sheet counts. Agents stopped inventing numbers the day we implemented this: omadia.ai
LLMs guess at math.
So our AI agent platform omadia gives agents a headless Excel in memory. Data goes in, the spreadsheet runs the formulas, the model sticks to reasoning, the agent reads the results back. File's there if you ask.
Take the guesswork out: omadia.ai
Still running workflows by hand? Repetitive tasks eating up your day? Many of them can run on an agent. With omadia.ai you don't need a dev for this. The agent builder does all the heavy-lifting. Oh, and it's free and open-source.
Your team answers the same questions 20 times a week. 🙄
Build the agent that answers and acts. Right where they work. 💡
✅ No code. No vendor. No black box.
✅ Self-hosted. Your LLM keys. Your data. GDPR-ready.
✅ Free. Open-source. Made in EU.
➡️ omadia.ai
The builder timeline is getting recursive.
We ask what people build to build tools that find more people asking what people build.
Anyway. What did you build? Or tried. Or gave up on. Drop a link.
Agent is mid-run. You realize it's heading the wrong way.
Until now: watch it finish, then correct.
With Omadia v0.7: type a message while it's running. Injected at the next iteration boundary. No stop, no restart.
omadia.ai
Running a social media account takes more tools than it should. Buffer or Hootsuite for scheduling, a separate analytics view, something for writing drafts. Multiple subscriptions, still context-switching.
Claude Cowork handles all of it. Just prompts. Here is the setup for X.
1/8
6⃣ ALGO LAYER
X's algo predicts 15 engagement signals per post. P(reply), P(repost), P(quote) and more.
This open-source skill scores your draft against those signals. Shows which ones you are hitting and what to change for better reach.
github.com/iret77/x-post-opt…
7/8
✅ That's a starting point. The X connector needs a one-time API setup. Everything after that is just prompts inside Claude Cowork.
✅ No subscription tools besides Claude and X, no fixed feature list. Build exactly the social media workflow you actually need, not the one someone else decided to ship.
💟 Like and repost if this was useful.
8/8
Can we agree that the most dangerous AI bugs are the quiet ones?
An agent shares something from the secret meeting. A tool returns one field too much. The model casually leaks it in the answer. Congrats, your agent is now a compliance incident.
Marcel wrote about the parts of omadia.ai that had to work securely before this could be used in real teams. Highly recommended read.
Imagine discussing something with your teammates while an agent is in the session too.
The agent takes notes. But those memories are only retrievable by the people who were there.
This is the point of omadia's multi-tier graph memory system: shared agents can work in teams without turning every memory into shared knowledge.
It keeps private context private.
omadia.ai is the open-source AI harness for grown-ups.
2️⃣ Agent memory breaks when every memory is treated as public.
omadia.ai uses access-aware graph memory so agents only retrieve memories the current user is allowed to see.
That makes shared agents work in real teams, not just private sessions.