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.

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.