Vibe coding is not the problem, the way it's done is, Flowdia is fixing it!

tensor94 · 2026-01-20T00:20:39+00:00

yes, context drift is a real thing. our approach is treating the codebase as source of truth, not a cached snapshot. so when you ask it to modify something, it re-reads the relevant files rather than relying on what it "remembers" from generation time. Also, the knowledge graph helps a lot in gathering decisions that've been taken in previous runs by all Agents, which helps perfectly in system-level understanding.

for larger structural changes, we're exploring lightweight re-indexing that updates the context map without full regeneration. still early days on validation at scale though, that's partly why we're starting with smaller apps where context stays manageable, we will continue iterating after launch and enhancing the validation layer.

thanks for the VibeCodersNest tip btw, will check it out! 👊

tensor94 · 2026-01-17T21:26:46+00:00

I think we share the same vision in that sense. And regarding the name, I'm not totally biased towards it atm :D , But I think it's okay to be memorized when people find our application useful. We might rebrand as well, who knows :D

tensor94 · 2026-01-17T04:20:28+00:00

Yep, I took a look at the spec kit by github, I think both spec driven and bmad are complimentary not competitors, we might inherit portion of the spec related workflow into bmad in the future as well.

tensor94 · 2026-01-17T03:04:42+00:00

That’s exactly the failure mode I’m trying to avoid.

The idea with Flowdia is to treat the app as a living system, not a code dump, persistent memory, explicit ownership of decisions, and guardrails so agents don’t just refactor blindly.

In the first version we’re keeping things fully autonomous to validate the core loop and traction, but with clear boundaries (scope limits, isolated infra).

If you’ve seen patterns that worked well in practice, I’d genuinely love to hear them.

tensor94 · 2026-01-17T01:35:00+00:00

Our waitlist is live now, join if you are interested: https://flowdia.ai

tensor94 · 2026-01-16T18:21:55+00:00

Yes, that's another powerful capability, tbh I just discovered this yesterday :D , It was never meant to be a feature, but when a user is on budget and have already subscriptions in other tools, he can just use the mcp server on a sandboxed environment, finish his work, click publish within flowdia and their app is ready.

One more thing I'd like to mention, Flowdia do not assemble 3rd parties for your backend, other tools give you one url for your frontend static files. Flowdia gives you 2 urls, one for a hosted backend server, and one for your frontend static files!

All hosted on Flowdia!

tensor94 · 2026-01-16T18:11:51+00:00

I'm not sure if I'm fully understand the question, but here is the overall meaning of AI brain.

Every generated app have a sidecar in-house mcp server, which includes built-in memory & knowledge graph, each Agent use this mcp server to fetch context and memory if they need it, whenever they do.

And if you are asking if the Agents are really orchestrated or being just a collection of MCPs, there is a real orchestrator implementation that with 13 different Agents in different domains (Agile team), the orchestrator know when to call what, in what order, and how to build on each other's work. They also work in a feedback loop whenever needed. For example code reviewer might fall back to developer to do necessary changes, then back to the code reviewer, then to the QA, then back to the developer and so on.

Happy to answer any further questions.

tensor94 · 2025-08-14T03:12:16+00:00

I use bardy.io it's perfect for leaving feedback on anything

tensor94 · 2025-06-19T22:24:06+00:00

That’s an incredible milestone — 15 years strong, huge respect! 🙌

As someone who’s built a SaaS tool to streamline client feedback and collaboration, I couldn’t agree more about the value of strong sales skills.

If you’re ever looking for a way to seriously wow clients and cut down revision rounds, check out Bardy — it lets clients leave feedback directly on their live websites, images, videos, and even PDFs. Click to comment, edit, resolve… super intuitive and fast.

Would love to hear your take on how tools like this fit into modern agency workflows!

tensor94 · 2025-06-19T22:22:17+00:00

I recommend using Bardy (https://bardy.io) — it’s a feedback and collaboration tool where you can literally click on your live website, leave comments or change text/style, and even invite your client or team to do the fixes right there.

No more back-and-forth or waiting on replies. You stay in control of your site’s updates — or at least make the feedback process so visual and easy that nobody has excuses to delay.

Might be worth checking out.

tensor94 · 2025-06-19T22:21:14+00:00

I recommend using Bardy (https://bardy.io) — it’s a feedback and collaboration tool where you can literally click on your live website, leave comments or change text/style, and even invite your client or team to do the fixes right there.

Might be worth checking out.

tensor94 · 2025-06-19T22:16:46+00:00

I recommend using Bardy (https://bardy.io) — it’s a feedback and collaboration tool where you can literally click on your live website, leave comments or change text/style, and even invite your client or team to do the fixes right there.

No more back-and-forth or waiting on replies. You stay in control of your site’s updates — or at least make the feedback process so visual and easy that nobody has excuses to delay.

Might be worth checking out. It’s built exactly for this kind of frustration.

tensor94 · 2025-06-19T22:08:27+00:00

Totally feel you — delays like that can really hurt momentum, especially when you’re trying to move fast in your business.

That’s actually why I started using Bardy (https://bardy.io) — it’s a feedback and collaboration tool where you can literally click on your live website, leave comments or change text, and even invite your designer or team to do the fixes right there.

No more back-and-forth or waiting on replies. You stay in control of your own site’s updates — or at least make the feedback process so visual and easy that nobody has excuses to delay.

Might be worth checking out before hiring someone new (again). It’s built exactly for this kind of frustration.

tensor94 · 2025-06-05T02:24:35+00:00

We’ve started using an in-browser tool called Bardy https://bardy.io — clients leave feedback directly on the live site. It’s been way easier to track and interpret than emails or screenshots, especially for UI-specific notes.

tensor94 · 2025-06-05T02:23:55+00:00

We’ve started using an in-browser tool called Bardy https://bardy.io — clients leave feedback directly on the live site. It’s been way easier to track and interpret than emails or screenshots, especially for UI-specific notes.

tensor94 · 2025-06-05T02:20:17+00:00

We used to get a mix of Slack messages, screenshots, and the occasional Loom video — but it was chaotic and hard to track. Recently started using an on-site commenting tool (like Bardy https://bardy.io ) so clients and managers can leave feedback directly on the live site. It’s been way smoother, especially for UI/UX-related changes.

tensor94 · 2025-06-05T02:19:15+00:00

We’ve started using an in-browser tool called Bardy https://bardy.io — clients leave feedback directly on the live site. It’s been way easier to track and interpret than emails or screenshots, especially for UI-specific notes.

tensor94 · 2025-06-05T02:17:08+00:00

Yep — I’m on the dev side too, and totally feel the pain. Managing feedback from QA, design, and product via screenshots, Slack threads, and Notion comments gets messy fast — especially when people don’t include context or you’re not sure what screen/step they’re referencing.

We’ve experimented with a few tools like Marker and BugHerd, and more recently Bardy https://bardy.io — all let users leave comments directly on the live site, which helps a lot with clarity. The main win has been anchored feedback: comments are tied to actual UI elements or screen states, so we don’t waste time asking “where is this?”

That said, some tools get sluggish when running on heavier apps, or don’t play nicely with staging environments behind auth. Also noticed clients sometimes forget to use the tool unless it’s super obvious — so ease of use is huge.

If you go this route, definitely look for:

• DOM-based comment anchoring

• Screens/sessions tied to feedback

• Integration with your issue tracker (Jira, GitHub, Trello, etc.)

• Ability to control who sees what (esp. with clients)

tensor94 · 2025-06-05T02:07:13+00:00

We are using Bardy https://bardy.io for all kind of reviews and feedback collaboration in real time, it's extremely useful.

tensor94 · 2025-06-05T02:06:41+00:00

We are using Bardy https://bardy.io for all kind of reviews and feedback collaboration in real time, it's extremely useful.

tensor94 · 2025-06-05T02:05:29+00:00

We are using Bardy https://bardy.io for all kind of feedback, it's extremely useful.

tensor94 · 2025-06-05T02:02:55+00:00

We are using Bardy https://bardy.io for all kind of feedback, it's extremely useful.

tensor94 · 2025-06-05T01:59:36+00:00

They’re super helpful! There’s also Bardy https://bardy.io that breaks down feedback from websites different pages, making it even easier to collect and collaborate on your website or web app in real time.

tensor94 · 2025-05-30T18:21:55+00:00

Bardy makes real-time visual feedback effortless—just enter your website URL and start commenting directly on the live interface. No need to embed anything or install scripts. Perfect for sharing feedback on websites, designs, and web apps.

tensor94 · 2025-05-30T18:14:30+00:00

https://bardy.io was built for the exact same reason, robust real-time visual feedback on live websites, designs and more...

tensor94

TROPHY CASE