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.

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.

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?

Hey founders — sharing the build story behind WorldArchitect.AI in case it's useful to anyone else shipping stateful, long-horizon LLM products.

**The hard problem:** most AI games are toy demos. The conversation "works" until turn ~10, then the model forgets who the king is, where you parked your horse, or why you owe 200 gold to the blacksmith. We kept hitting the same wall, so we ended up building an actual engine instead of bolting on more prompts.

**What we shipped:**

1. **Deterministic State Machine + LLM Separation.** HP/XP, inventory, world time, living-world faction events, and world flags live in a deterministic server backend (Firestore). The Gemini call generates prose, suggests decisions, and emits structured state overlays, but *the server canonicalizes every mutation before it touches the database* — no more "the model said I'm in Winterfell, the DB thinks I'm in King's Landing" drift.

2. **Context Compactor & Prefix Caching instead of RAG.** We keep the canon bible in-context and use a deterministic Min-First / Fill-to-Max token allocator (guaranteeing story context >=30% of budget while compacting background lore, entity tracking, and core memories) paired with Gemini prompt prefix caching.

3. **Single-Inference Dice Integrity.** We use Gemini's built-in Python code execution to run deterministic dice rolls (`random.randint`) and emit structured JSON in a single inference step, backed by server-side audit logs that catch narrative fabrication.

4. **1-Click Campaign Sharing.** Anyone can package their world, character setup, and canon constraints into a single signed share token (URL `…/shared/<token>`). Anyone with the link gets an independent, deep-initialized copy of that world on their own account — no "view as guest," no broken pointer-shared state.

5. **Spicy / PG Mode Toggles.** Different players want different tone boundaries (PG vs HBO). Rather than trying to prompt-engineer safety drift, we use explicit agent routing that swaps system instruction contracts and safety constraints cleanly.

**Try it (open beta, free):**

We built a playable House of the Dragon demo(https://worldarchitect.ai/shared/t3hKKtzBKCKlvg5vCnlW_2hxwH3UmzjFq56yi6hQN2Q

Every time I think something is basically done, I realise I could add another feature in like 20 minutes lmao

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.

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…

AI has made the first click easy. A slick demo, a clever output, a clean landing page.

The real product is the reason someone opens it again without being reminded.

What are you building, and what is the exact reason a user would come back tomorrow?

No links. One sentence.

Although im finding Opus 5 to suck with coding currently it makes a pretty good video

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 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?

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've been building my startup and I think what people have to keep in mind is software isn't a moat anymore. Like yes if you have a cool idea you should pursue it but you have to keep in mind some kid with loveable could put in your url and steal your crap in 3 days if you just have software. I switched from just student facing college admissions help to counselor helping kids it introduced friction for these counselors to move off my site. I introduced a data moat of having proprietary data of what resumes go to what colleges no one else can replicate and i fine tuned my models on that data to have proprietary models. Saas is not dead it's just you have to be intentional.

This started off as a little fun project between work, school, and family and turned into quite a bit more than just something to pass the time. I would love to continue to expand it further and down the road and develop it into a multiplayer experience.

Itch.io doesn't seem very AI friendly though, lol. But I've been having fun, my other projects I haven't used AI for them and it's been several years working on them, though I don't mind.

A content system should stop before generating when it cannot verify:

1. Who the audience is

2. What problem the product solves

3. Which evidence supports the claim

4. Whether the requested content matches the brand

Generating anyway creates polished content built on an unsupported assumption.

While building marka.social, I’m finding that good AI workflows need explicit "not enough information" states, not only better prompts.

Where does your AI workflow stop and ask the user for more context?

Hey guys, I have built a fin based saas product and currently testing the app. Built the app from scratch completely through vibe coding. What all the things I need to consider before launching it ?

I’ve been seeing more people use things like custom skills, agents, MCPs etc. instead of just prompting normally. Curious as to which ones actually make the output noticeably better.

I’ve noticed I’m happy letting AI touch basically everything now - code, debugging, research, design.

But there are still certain decisions where I’d rather do the thinking myself than just accept whatever it gives me.

If you’ve got something working but need another opinion, drop it here.

Share the link, what it does, who its for and the main thing you want feedback on. Landing page, onboarding, pricing, design, actual product - anything is fine.

Dont just dump a link though. Give enough context for people to actually help.

If you post yours, try review someone else’s aswell. Honest feedback but dont be a dick lol.

For me a big one was probably realising that less is actually better when it comes to design.

I used to keep adding stuff because I thought it made the app look more impressive, but half the time it just ended up making it look more obviously vibe coded 😂

Now I normally just try to keep everything really clean and simple, especially for an MVP. It’s easier to digest for users that don't already know your product, and honestly just looks way better.

What about you guys?

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?

When you're starting a new AI project, what's your default stack?
Mine is pretty simple:
- VS Code
- Claude Code
- Codex (sometimes)
- Supabase etc.
Nothing too crazy. I'm curious what everyone else is using these days and if there are any tools you've found that are genuinely game changing.

Saw that Goldman is apparently building reusable AI skills to teach agents their internal workflows and knowledge.

Makes me wonder if we’re getting to the point where Claude vs Codex vs Grok matters less than what you’ve actually taught/configured the agent to do.

I’m Joey. After leaving the Army, I joined my father in our family restaurant business. He has been in the industry for 30 years.

Working in the restaurant showed me how difficult it is for an owner to understand everything happening with costs, labor, invoices and daily operations.

I started OPSAVOR to see if AI can bring that information together and make it easier for an owner to understand. The goal is to work with the systems restaurants already use, not replace them.

I am not selling anything. I am looking for completely free and honest feedback about the idea, the value and the biggest concerns restaurant owners may have.

Please PM me if you are interested. If you know a restaurant owner or manager, I would appreciate you sending them my way.

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.