... Several Claude Code and Codex sessions at once? The hard part stops being the work and becomes remembering which one is waiting for you. Lancetta's Sessions wall puts every session you started on one wall, as post-its: Your turn: it asks you something, finished, stopped, or its terminal closed. With how long the longest has waited

... Ross, the owners of N8N Chat UI, and we launched on Product Hunt today. One thing we're curious about from people building with n8n: what makes a chat widget useful on a site, beyond sitting in the corner waiting to be clicked? The widget has a small JavaScript API, so you can start a chat from almost anything. The example we keep coming back to is e-commerce: if a shopper's been on the checkout page ...

... everyone! Like many of you, I used Splitwise for years to split trip and flatmate expenses. Lately, it has become almost unusable on the free tier between strict daily expense limits, annoying 10-second wait timers, and constant paywall popups just to do basic math. So I built Contri a clean, fast, and 100% free Android app for splitting group bills without the nonsense. What makes Contri different: Zero ads, no paywalls: No daily caps on adding expenses ... ... second wait

... agents Beyond Claude Code, Codex and Grok, AgentDock now reads Gemini CLI, GitHub Copilot CLI, OpenCode, Kilo Code, Antigravity CLI and Claude Cowork , and shows Cursor's agent under its own name. Their dots show when they're working, waiting for you and done, and their finished turns go into History, Activity and Tokens. Nothing to install. They're in preview until each one is checked in a live session: turn them on in Settings Agents. Answering from the Inbox ... ... Collision radar: a red ring when two agents change the same file. Second opinion: press V on a finished task and Codex reviews Claude's work, or Claude reviews Codex's, in a new tab beside it. Waiting

... where a new email no longer holds you in a queue behind itself. You tap the notification, Skim was already downloading that exact message, and it used to make you wait for that download, give up on it, then start again from scratch. Efficiency! Fixed Opening a message you just got is quick again. Clicking a message that had just arrived could hang on "Fetching from the server " for up to a minute. Your click used to wait

... decide that your product was actually ready to launch? I m particularly curious about the point where you stopped thinking , we need a few more things before launching, and decided to just go for it. Did you wait for: a certain number of users? consistent usage? testimonials? a polished onboarding experience? a few important integrations? or did you launch much earlier and use Product Hunt itself to get feedback? I m working on a developer-focused product myself and trying ... ... avoid making the mistake of either launching too early or waiting

... Open the terminal where your agent is running. Do it now, before you read the rest. Is something sitting there waiting for you? How long has it been there? I did this an hour ago. Mine had been waiting

... been putting off a price increase because I keep telling myself I need more data first. "I should wait until I know my churn rate." "I should wait

... more months of retention stats before changing my plans, but honestly i think i'm just nervous to charge more . Every time i look at the numbers i find another excuse to push it back. Did you guys wait for full cohort data before increasing rates or did you just change the pricing page and deal with whatever happened ...

... built Barcode & QR Scanner & Maker a free Android app built for speed. No lag, no waiting when you're mid-payment or trying to get through a gate/access scan. Point, scan, done. Why it's fast: Instant detection built on CameraX, tuned for near-zero scan delay Multi-barcode detection in one frame no rescanning 100% offline no server round-trip slowing things down No tracking, no data collection Other features: GS1 parser for retail/product codes ...

... links did nothing. What was rationed was crawl budget, and none of the levers on my side reached it. The part I still cannot explain is why 31 August specifically. Nothing shipped that week. Has anything reliably shortened that wait for you on a domain with no authority yet? Comment from Serdar D(@serdarships): Answering your question first: the only thing that ever moved that wait

... Hunt. And if you're wondering how the heck that happened, just give me a minute. I've only been here for a couple of days, even though I've known about Product Hunt for months. Why did I wait? Fear. Yeah. I'm not ashamed of saying that anymore... I spent 7+ years in the pharmaceutical industry until I couldn't stand the healthcare system anymore. So I headed toward what I loved most: marketing. Finding the right positioning ... ... thinking: Could I actually build something myself? And even if I could... who is going to buy it? I don't have a huge social following. I don't have an email list. I don't have a community waiting

... Product Hunt community I m Veking, an indie developer. I ve been between jobs for the past three months. At first, every day felt like a waiting room: applications sent, inbox open, hoping someone else would decide what came next. Eventually, I got tired of waiting

... After years of building with teams, I'm convinced most dependency problems aren't scheduling problems. They're perspective problems. Every cross-team handoff has two sides that never see it the same way. If you're waiting, the other team looks slow, or like they've deprioritized you. If you're the one being waited

... weekday at 8:55 check overnight GitHub activity and #product on Slack, cross-check today's calendar, and post a digest to my Notion." What lands in Notion example Tue Aug 12 Needs you today PR #481 approved overnight waiting on your merge Nina asked in #product whether the pricing page ships this week 2:00pm Northwind call proposal thread summarized below From then on, when you sit down at 9:00, the things that need you are already standing ... ... scripts, and edit documents right where they sit. "Tidy up this folder group by type, and don't delete anything without asking." Check the last folder: the suspected duplicates weren't deleted they went to a review folder to wait

... Genuinely collecting numbers on this, because everyone I ask gives a different one and I suspect the honest answer is much lower than people admit. I build real-time voice and face models, so waiting is the problem I stare at all day. The thing that surprised me is that the tolerance is not one number, it moves enormously depending on what the agent appears to be doing. If it is silent, people bail in about two seconds ... ... shows a spinner, maybe five. If it streams tokens so you can see it working, people will sit there for thirty and not complain. Same wait

... which of these are you? A. Nothing my agent does reaches past me. Genuinely low stakes, no gate needed. B. It could reach customers, I know it, and I have not built the gate yet. C. It stops and waits for someone to come back and look. Safe, and it quietly kills completion. D. It emails or Slacks someone, which mostly works until the person who cares is not in that channel. E. I built the real thing, timeouts, escalation ... ... them. The other half inverts the intuition. You would think affects more people means wait

... window with a titlebar and nothing. Restarts didn't help. Reinstalling didn't help. Then, hours later, it just came back which is somehow more unsettling than staying broken. Turns out nothing was broken. The whole UI was waiting on the first mailbox query, that query was politely queued behind the catch-up sync, and the app had no way to say "hang on, I'm reading" so it said nothing at all. For hours. In an empty window. Cool ... ... answered in 2 seconds, the shell appears anyway. If it fails outright, you get an error not a blank rectangle and a shrug. No more "welcome to Skim!" for people who've been using Skim for months. Onboarding waits

... shortest amount of time. Not to mention when you have a family and want to make time for your personal life too. For me, it s: using AI for summarisation, research, and repetitive tasks, delegating tasks, using waiting time for work, for example while waiting

... paying to the first result; payments are on from day one, because a launch without a way to pay only tells you people are curious; and we can answer every comment by hand that day. What I would not wait for is every feature. A few things in our product still wait

... built to produce an answer, recommendation, signal, or action every time a user asks for something. But in areas like trading, investing, healthcare, or cybersecurity, forcing an answer can be dangerous. Sometimes the most responsible output might be: Wait. There is not enough information. The risk is too high. No action is better than a bad action. Do you think users would trust an AI more if it openly admitted uncertainty and occasionally recommended doing nothing? Or would that make ...

... Daily reality: Claude Code in one pane, Codex in another, Cursor in a third, plus a few shells. An agent stops and waits for "yes". By the time I find the right pane, 20 min gone. Just me? What's your setup notifications, layout tricks, or you've accepted the tax? Comment from Ghost Kitty(@ghost-kitty-9562997): Comment Deleted Comment from Sahith.V(@nextmark): @hellokidder01 That "which one stopped" problem is the unglamorous one nobody talks about until they ... ... interns. Start with sandbox + repetitive tasks, then edge cases, then 1% traffic. Comment from Kidder(@hellokidder01): Honestly this is exactly why I built one for myself PokePoke . Menubar app, pings me when any agent (Claude Code / Codex / Cursor) is waiting

... Setup 2, let it rip: auto-approve, skip permissions, go do other work. Faster in theory. Except I come back to one of three things. It finished 30 minutes ago and I wasted the half hour. Or it sat waiting on a yes/no I never saw. Or the fun one, it happily ran something I would never have approved. The more agents I run in parallel, the worse this gets. Babysitting three terminals is impossible. Trusting three terminals blindly ... ... Ghani(@aadilghani): @virko_kask   Agent-state instead of task-type as the urgency signal is better than what I had, and I think you just moved my whole priority model. Category decides if it may reach me, idle-vs

... only problem the early founders have. They usually do not know when to start promoting, or simply do not have the courage to start. In the past: I used to struggle with sharing something before it was finished. I waited until everything was done before announcing that I had built something. Because I kept the problem to myself instead of talking about it, I couldn't validate whether it was worth building or improving the idea through feedback. I spent ... ... Maybe when I launch it, and others will test it, they will hate it :D hahaha Comment from Nika(@busmark_w_nika): @artem_fedorovich  I would ask them to sign up for the waitlist. Currently 18 people are waiting

... first group tore their workflow apart and rebuilt it around AI. The second group is waiting for the dust to settle before committing to anything. The waiters have a defensible case. Half the AI tools from 2024 are dead, the best model changes monthly, and rebuilding your stack every quarter has a real cost. In most platform shifts, the fast follower wins (think Apple). But this shift compounds in a way that previous ones didn't. When a competitor