Hey builders

It's Christmas. You're probably supposed to be doing something else right now.

And yet here we are. Both of us. You reading Product Hunt, me posting on it.

I built a thing. It's called It Works (itworks.now).

I ve spent the last few months obsessed with a specific failure in multi-agent systems: The Black Box Dilemma.

Most MAS setups I see (including my own v1) treat orchestration as "glue code." You have a central manager, a few agents, and a lot of hidden logic. When it fails, you re left guessing. As someone on IndieHackers put it: "You re just parallelizing chaos."

The Shift: From "Dictator" to "Blackboard"

In our latest iteration, we deleted the 430-line monolithic controller. Instead, we implemented a Blackboard Pattern.

Hey everyone

Taskade started as a real-time collaboration tool for planning and productivity. Then we added memory, agents, and automations. Soon it stopped feeling like a static tool and started acting like a real living workspace that could handle parts of the work on its own.

When I first set up OpenClaw, I ran into a big problem immediately.

I spent $250 on my first day doing what felt like harmless testing.

Nothing production. No customers. Just me trying things like:

• Summarize this Slack thread

• Give me a morning digest

• Explain this error log

• Pull action items from the last N messages

• A couple Telegram alerts

I didn t build our internal compliance tracking tool the traditional way.

I vibecoded it.

Instead of long PRDs, heavy sprint planning, and weeks of back-and-forth, I stayed close to the problem and built in tight feedback loops shipping small, observing behavior, and iterating fast.

The flow was simple:

There's a popular narrative on social media right now that AI can build software so quickly and cheaply that SaaS is dead (or will be soon).

Why pay for Linear when AI can build a project tracker in an afternoon? Why pay Stripe $30k/year when you can vibe code your own billing system in a weekend? The cost of building software has collapsed to near zero, therefore the value of selling software has collapsed to near zero. QED, SaaS is dead.

Hey everyone

I m exploring different Backend-as-a-Service (BaaS) options for vibe coding projects small but creative builds that start locally and later go live (think quick prototypes, coding agents, or AI-powered hobby apps).

I d love to hear your thoughts on:

• how easy is it to debug or simulate the backend locally?

• how smooth is it to go from local to hosted?

• any gotchas or scale-to-zero tricks to keep costs minimal?

• functions, auth, storage, DB branching, edge runtimes, etc.

This morning I opened my inbox to find an alert from GitGuardian about a leaked key. My first thought: Great, another phishing email. Nearly deleted it on the spot. Then I realized yesterday when I was using Cursor to bulk-update my scripts, I d left the API key in plain text

Here's an idea we are thinking about:

Netflix for AI generated fims, pretty self explanatory

Problem

This week, Google unveiled Veo 3, its latest AI video model capable of generating hyper-realistic videos from text prompts. The line between AI-generated and human-made content is blurring rapidly.

This was a deliberate experiment inspired by my CTO. I wanted to test a simple question:
Can a Product Manager ship a real website end-to-end today without handoffs?

Here s the stack:

• @Figma structure, hierarchy, & visual components

• @Adobe Illustrator brand consistency & visual components

• @ChatGPT by OpenAI positioning, copy angles, objections

• @Lovable iterate layouts before committing

• @Cursor turn ideas into real UI fast