Hey everyone, Before I flood this with content, I want to make sure it’s helpful to all of you! Quick poll: what do you want more of? Vote below and drop a comment if something’s missing from the list. The results drive what I build next.

Drop your answer in the comments. Tell me one thing you're trying to automate right now. It could be: - Something repetitive that's eating your time - A process you've started building but got stuck on - An idea you don't know how to approach yet Every Sunday I'll pick one submission and do a full deep dive: architecture, tool selection, flow design, and the decisions that actually matter. I'll post it here so everyone benefits. Drop yours below. — Mike

New build, short and practical: an AI product photo studio for a candle brand, about 6 cents a photo. The stack: - Mobile-first front end: pick a photo, choose layout + aspect ratio, type a one-line prompt. - n8n workflow: webhook fires, an agent expands the one-liner into a full prompt tuned for the image model. - Image model: Google Nano Banana 2, run through KIE.AI (a marketplace that resells model usage well below retail). - Poll until the job finishes, download the image, push it to a self-hosted open-source image server, serve it back to the app. - Approve to publish: the photo lands in a wholesale partner portal so retail stores can pull assets themselves. Cost breakdown: about 6 cents per image to generate, under a penny for the prompt expansion (GPT-4o mini). The second unlock here is the retail partner self service, no more sending photos to partners manually. Build for the whole workflow, not just the cool part. Want the template? Say so and I will post it. Built something similar? Show me.

A couple of weeks ago I shared a small workflow: it turns YouTube videos I find interesting into structured research docs, so the good ideas don't evaporate the moment the video ends. New tech, architecture talks, build logs. Transcribe it, break it down, and file it where my agents and I can both find it later, so we can ideate on it and figure out how it fits the stack we are already building. That workflow was the goal. I built it because I wanted it, and it does its job. But finishing it left me holding something I didn't have before: a research library that grows every time I digest something good. And that asset spawned the next idea. Now that I've got this dataset, what can I automate around it? So I built a LangChain blog writer agent on top of it. Every 2 weeks it reads that same research library, surfaces three things worth writing about, and hands me the shortlist. I pick one. It drafts the post. I approve it. Then it publishes to my site on its own. I keep exactly two decisions: which idea, and whether the draft is good enough to ship. The agent does the rest. That's how I approach AI. You don't architect the grand system up front. You build one honest thing because it's worth having, and the finished thing hands you raw material you didn't have yesterday. One good idea becomes the dataset for the next one. It cascades. Now here's the part I left out, because the cascade goes back further than the YouTube workflow. None of this was the plan. It started when I decided to actually learn LangGraph and LangSmith. Not for a project. Just to understand how agents get built, and how you trace what they do once they are running. I made toy graphs. I sat and read the traces. I broke things on purpose to see what the tooling would show me. That curiosity was the first domino. Learning the framework is what got me building agents at all. Building agents is what made me want a research pipeline to feed them. That pipeline is what made the blog writer obvious.

Glad you're here! This is a room for people who want to actually build with AI agents, not just watch demos. Whether you wired up your first workflow last week or you've got agents running in production, you belong here. Let's kick it off. Drop an intro in the comments and tell us: 1. Who you are and what you do. 2. How long you've been playing with AI (be honest: "since last Tuesday" is a totally valid answer) 3. What you're trying to build, or what brought you here. 4. One thing you're stuck on right now (someone here has probably solved it) A few things to know: - New stuff drops regularly: workflow templates, build teardowns, and the engineering behind real deployments - No question is too basic. The people who ask are the people who build - No gatekeeping, no fluff. Share what works, ask what doesn't The fastest way to get value here is to engage. Comment on intros, jump into threads, post what you're building. See you in there. — Mike