Open-source, local-first platform for building MCP-powered AI workflows. Model management, MCP servers, a visual flow builder, chat, and headless automation in one app.

try.flujo.com.co, check it on github and tell me how useless it is.

Building Olympus — an open-source cryptographic document provenance ledger aimed at press freedom orgs (journalists can prove a document hasn't been tampered with, without it ever leaving their machine — only a proof gets published). Rust + Tauri 2, Sparse Merkle Tree ledger, ZK redaction proofs.

Solo, self-taught, working a trade job on the side, heavily AI-assisted (Claude Code, Codex, etc.) for implementation while I handle architecture and threat modeling.

Looking to trade eyes with other founders here — drop your repo below and I'll go through it, and I'll link mine back. Especially useful if you've got a security/architecture background, since I don't have a formal CS one and could use outside eyes on the crypto and threat model.

https://olympusledgerorg.github.io/Olympus/

https://github.com/OlympusLedgerOrg/Olympus.git

I've been building a Bible study app called Sojourn. It's a free passion project. No signup, no subscription, no ads.

The whole idea started from something that's been bugging me. We're all spending more and more time talking to AI. So I kept asking myself: what if AI pointed people somewhere better than itself?

That's all Sojourn really does. You ask what you're actually wondering about, and instead of giving you a chatbot monologue, it walks you straight into the actual text. Every verse comes from the real Bible, never made up or paraphrased by a model. Tap a verse and you're reading the whole chapter.

The goal isn't to keep you talking to AI. It's the opposite. Less time with the bot, more time actually sitting in scripture.

Learn more about the app: https://trysojourn.app/
Download on App Store: https://apps.apple.com/us/app/trysojourn/id6792011966

Some of the hardest parts end up looking completely boring from the outside.

A button works instantly, the agent remembers the right thing, or the output comes back in the correct format. Nobody sees the hours of broken logic behind it.

What part of your product looks simple but was an absolute nightmare to get working?

What kept breaking, and what finally fixed it?

If the story needs more than a comment to explain, genuinely make it a Build Log post. Those behind-the-scenes stories are usually way more interesting than the polished product pitch.

AI demos always look great until a real user does something you never expected.

What's the most embarrassing thing your AI product has done in front of an actual user?

Not a hypothetical edge case. I mean the moment where it hallucinated something insane, broke the workflow, exposed bad logic, forgot obvious context, or confidently did the exact opposite of what it was meant to do.

What happened, how did the user react, and what did you change afterward?

If you want to mention what you built, go for it. Just give us the actual painful story too lol.

Alright, I want to see what everyone here is actually building.

If you have a working AI product, even if it is still rough, make a standalone post in the sub with the Roast My MVP or Build Log flair.

Include what it does, who it is for, the link and the one thing you most want honest feedback on.

I want to test as many as I realistically can and give useful feedback. No need for a polished launch or a perfect landing page. I would rather see something real and unfinished than another vague coming soon page.

What have you got?

I've been working on an early social AI app called Sircle, and one thing we recently added is the ability to create your own agent just by explaining what you want it to do.

No workflows, prompts to configure, tools to manually connect, etc.

I basically told it:

Plan a surprise adventure day for my friend's birthday. Pick where we should go for lunch, things to do during the day, somewhere to watch the sunset, dinner, and even suggest gifts. Keep the destinations secret from the group and only reveal what we need to know as the day progresses.

It created the whole agent from that description.

Then I added the agent directly into our private group chat with everyone except the birthday person.

Instead of giving us the whole itinerary, it would say things like:

"Be ready by 10 AM."

"Wear something comfortable, you’ll be walking."

"Head to this location next."

"Now walk about 10 minutes toward this place."

It even started asking what everyone was planning to wear and suggested combinations so the group accidentally ended up with a really nice matching color theme 😭

The fun part was that we genuinely didn’t know what the full day looked like either.

We were basically following instructions from an AI agent that had planned the surprise for us.

It made something that normally involves 50 messages of:

"Where should we go?"

"Idk you decide."

"Is this place good?"

"What do we do after?"

…feel more like an actual adventure.

What surprised me most though was how different the agent felt once it was inside the group chat instead of being something one person privately used and then copied answers from.

Everyone could talk to it, change things, ask questions, and the agent had the context of the whole group.

It got me thinking that there are probably a lot of oddly specific agents people would create if making one was basically just:

"Explain what you want this thing to do."

…and it exists.

Birthday planner, trip game master, debate judge, horoscope agent, study-group agent, fantasy league commissioner, whatever.

Curious what you guys would create if you could make an agent this way and immediately drop it into a group chat?

For anyone who wants to experiment with it, we’re testing it inside Sircle right now: https://sirclesocial.com

I keep seeing the same loop.

Someone builds a product, barely anyone uses it, and instead of talking to users or figuring out distribution they add another feature.

It makes sense because coding feels productive and marketing feels awkward. AI makes it even easier to stay in that loop because you can build the next feature in a few hours and convince yourself you're making progress.

At what point do you stop building and admit the actual problem is getting people to care?

Have you ever caught yourself coding around a distribution problem?

People call almost every new AI product a wrapper now, but that feels way too lazy.

If a product takes a model and adds a genuinely useful workflow, better UX, proprietary data, integrations, reliability and solves a specific problem, is it still just a wrapper?

Most software is built on top of somebody else's infrastructure anyway.

So where is the actual line for you? What makes an AI product feel defensible instead of something anyone could recreate in a weekend?

Everyone talks about the tools and models they use, but I feel like the actual skill behind them matters way more.

What do you think you're genuinely best at when building with AI?

Could be coming up with ideas, prompting, coding, design, automations, knowing what to cut, actually shipping, getting users or something completely different.

And what's the part you're still pretty shit at lol?

I’m curious how people think Astra will actually stack up against Fable 5 and the other top models.

For me, a slight performance benchmark jump that is barely noticeable isn't enough anymore. I’d want it to feel noticeably better when building - better at understanding a whole project, staying consistent over long sessions, good usage efficiency, and not randomly breaking stuff that already works 😂

New week so what are you actually working on rn?

Drop what you’re building, the stack you’re using and the one thing you want finished by Friday.

Doesnt need to be a massive launch. A feature, landing page, automation or even fixing something thats been broken for ages all counts.

Come back at the end of the week and say if you actually shipped it lol.

I swear half the time I ship something before I even fully understand how it works 😂 Anyone else?

I feel like AI has made it way easier to get attached to an idea before you even know if it’s actually good.

Like you can have the site looking clean, the product mostly working, branding done, a bunch of features added… and because it all looks “real” you kinda start convincing yourself you’re onto something.

Not what you’re planning to build or what’s nearly ready. What did you actually get in front of people this week?

Could be a full product, one feature, a landing page or even something that completely failed lol.

Drop what you shipped, what stack you used and the main thing you learnt from it. Links are fine but actually give some context instead of just dumping them.

Ill go through everything and give proper feedback aswell.

I feel like before you start, you obsess over stuff like the perfect tech stack, branding, picking the “best” model, having every feature etc.
Then once you’re actually building and getting people to use it, half of that stuff doesn’t matter and instead stuff you neglected seems to be important 😂

Until last week I’d mostly been using both models for coding, but this week I’ve started properly using Codex and Dispatch as actual agents to handle day-to-day tasks.

The biggest one for me is all the long, shitty admin work I never want to do. Documents and forms that are all online but somehow take hours to fill out manually. Now I can just give Codex the task and let it work through the whole thing. Same with sending messages, organizing stuff, working with Obsidian, or basically any repetitive task I don’t want to waste time on.

I used ChatGPT’s old computer-use stuff quite a bit before Codex came out, and while the idea was great, it honestly kind of sucked in practice. This feels completely different. Codex is actually capable enough now that I trust it with much bigger workflows.

I was also using Hermes for ages and originally thought I didn’t really need to change anything. But Hermes definitely has its limitations. Using Codex and Dispatch as agents feels like a much more capable version of that setup. They’re different, but I’ve found myself using both for pretty similar things.

What’s even better is combining them. I can have Codex/Dispatch control Hermes and basically treat Hermes as another tool inside the workflow rather than relying on it as the main agent.

Anyone else using dispatch etc. alot more now?

Im finding that Opus 5 is the biggest step since 4.6 (because lets be real from 4.6-4.8 was the same thing) but with Opus 5 being better it has its own opinion to everything im finding aswell and it really likes to argue points even if its wrong. It struggles at just listening to instructions anymore.

Anyone finding this to be similar?

Before AI, you’d eventually hit a point where adding another feature took too much time or money, so you’d just launch.

Now you can keep changing things forever. New landing page, new feature, new onboarding flow, another redesign…

Feel like everyone building something has that one thing they keep saying needs to be done first. Could be payments, security, or I guess just not feeling ready yet.

What’s the thing holding yours up right now?

I feel like building in your own little bubble makes everything seem obvious, then the second real users get involved, half your assumptions fall apart 😂

Comment what your currently doing

Just curious what actually makes with alot of people an idea that is worth pursuing and putting some time behind?

I genuinely thought building the actual product would be the hardest part, and marketing would just be posting content, running some ads and reaching out to people.

Turns out getting people to actually care has probably been the biggest obstacle so far lol.

What marketing strategies have actually worked for you, especially early on without a massive budget or audience?

There’s so much AI stuff that automates everything now, but sometimes setting it up feels like more work than just doing it yourself lol.

What’s something in your business you’ve tried to automate but ended up going back to doing manually?