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).

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.

You finish a session, close Cursor, come back the next day. Ten minutes gone just reconstructing where you were. Stack decisions, rejected approaches, half-finished threads.

Nobody talks about this part. Everyone optimizes the coding flow but the between-session memory problem just sits there.

How much do you spend on monthly subscriptions?

If you re already on a premium plan like Claude Max or ChatGPT Pro, stick with it, unless you really want to optimize your "vibe coding" workflow.

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.

Hey there,

Bit of context first: I am a member of a 30 people+ team and most API clients we used felt like they were built for a different job than what we actually did.

I just launched AllPub.co and built pretty much the entire thing using Vibecoding with Claude Sonnet 3.5. I'm a software architect with just some basic Python knowledge, so this was my first full web app build. Wanted to share my experience!

What I Built

I spent 25 years on construction sites. Today, I don't write code I orchestrate it.

While my latest launch ('What Do I Say?') was trending on PH, I spent the afternoon using agentic loops to build a Full-Stack AI Navigation App.

The Stack:

• Backend: Real-time Google Maps/Waze data orchestration.

• UI: High-end 'Co-Pilot' dark mode dashboard with 2D/3D perspective switching.

• AI Layer: A multi-intent voice brain that handles routing, traffic interrupts, and 'Pit Stop' predictions.

• The Result: A production-grade, voice-first navigator built without writing a single line of manual code.

Came across the recent Claude Code leak from Anthropic, and what stood out wasn t the leak itself, but what it revealed about how these systems actually work.

• A source map file accidentally exposed ~500k lines of TypeScript

• Turns out Claude Code is basically a multi-step prompt orchestration system, not some mysterious black box

• Includes things like:

  • layered prompt pipelines ( prompt sandwich )

  • fake tools to prevent model distillation

  • simple frustration detection (regex for rage prompts )

• Even hints at future features like background agents and persistent memory systems

What s interesting is this:

It kind of confirms that the real product layer in AI isn t just the model it s everything wrapped around it.

Which raises a few questions: