PH热榜 | 2026-06-19

Claude Code Artifacts launches today, a solution for teams struggling to share in-progress AI work. Instead of manual status updates, you get live, interactive web pages built from your full session context that update automatically.

What makes it different: Artifacts capture work as visual pages (PR walkthroughs, dashboards, incident pages, release checklists) that refresh in place — no need to wire up data sources or stand up infrastructure.

Key features

• Built from full session context (codebase, connectors, conversation)

• Live pages that update & republish automatically

• Version history with restore capability

• Private to your organization by default

• Gallery to browse/manage all artifacts

Benefits: Teams spend more time building, less time communicating status. Everyone sees the same view with the same context.

Who it's for & use cases:

• Software engineers: PR/bug walkthroughs

• SRE/on-call: Incident pages that become postmortems

• Designers/frontend: UX variations from real components

• Security: Findings linked to exact code lines

• Legal: License audits flagging copyleft

• FinOps: Cloud cost drivers mapped from Terraform

Available in beta for Claude Team & Enterprise orgs via CLI/desktop app.

P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends

I use Claude Code every day to build my products, so this hits a real nerve. For me the killer use isn't team status updates, it's showing a non-technical client what I'm building mid-session without deploying a half-finished thing. Sharing a live artifact instead of "trust me, it's coming" would kill so much back-and-forth. Question: can you share an artifact with someone outside your org (a client) easily, or is it team-only? That's the use case I'd reach for first.

Live preview for agent work is useful because review is where trust gets built. Do you see this becoming more collaborative, where a human can inspect multiple agent branches, compare outputs, and decide what gets merged or discarded?

The auto-republishing live pages from full session context is the part I'd actually use, sharing in-progress work usually means stopping to write a status update. Does it handle multiple repos in one session? Congrats on shipping.

The auto-republishing live pages are clearly the headline feature, but I keep thinking about the flip side: sometimes I'd want to freeze a version rather than have it shift under me as the session keeps moving. Is there a way to pin a snapshot alongside the live view, so the durable record and the live one can coexist?

The live artifact angle makes sense for PR walkthroughs and incident notes; the key question for teams will be how access and staleness are handled when the underlying session keeps changing.

I'm not a developer by trade, but AI tools have made it possible for me to go from idea to working prototype much faster than I thought possible. Excited to see more tools that make building accessible to non-engineers.

Another banger update by Claude.

I have the old cowork for windows, using that with Claude Code in Powershell. Can someone tell me, is the new Claude Code Desktop stable? I would hate to replace "good enough" with buggy.

do you guys stll use 'superpower' plugin/skill?

Hey Product Hunt! I’m Miki, founder of Zernio :)

We built Zernio as a social media API. One integration, 10+ platforms, and developers could ship social features without spending months on OAuth flows and platform-specific quirks. That part worked.

But we kept getting the same question: what about WhatsApp?

Not “can you send a message”, but the whole thing. Numbers, broadcasts, calling, in-chat forms, group chats, AI agents. People were building real products on WhatsApp and the existing options were either expensive BSPs with markups on every message, or raw Meta APIs that take weeks to months to set up.

So we built it properly.

Connect a number, get the entire WhatsApp Business API behind it. Same Zernio integration developers already know. Zero markup on usage, you pay exactly what Meta charges per message sent, and Zernio monthly subscription. REST, SDKs, CLI, and a hosted MCP server if you’re building with AI agents.

We’re 7 people in Spain. Bootstrapped. We’ve been shipping one WhatsApp feature a day this week and today felt like the right moment to bring it to Product Hunt.

We’ll be in the comments all day. Happy to go deep on anything, like how number provisioning works inside Zernio, how to manage templates, or how the pricing compares to Twilio, whatever you’re curious about 🤝

Hi PH community! Darya here, the marketer behind this launch.

I joined Zernio 3 months ago. Two weeks back Miki said "let's do a feature week for WhatsApp." the team said 'yes' without fully knowing what that meant for our calendars 😅

So we shipped. Workflows on Monday, phone numbers in 53 countries on Tuesday, calling API on Wednesday, Flows on Thursday. And today we're here on Product Hunt. Watching our team build in real time has been something. Seven people, bootstrapped, just shipping. So if you have any questions about the launch, the product, or how we pulled this week off (without tears) I'm here all day!!

After seeing from the inside how the team built this WhatsApp integration, it was just amazing. I'm so excited for you all to enjoy it and try it! ❤️

This is an insane product and an amazing team effort! Let keep pushing!

One of the most interesting launches today! And a good call on the whatsapp calling angle as this is the part nobody else is really shipping. QQ - how are you guys handling the 24h customer service window? I trust once it closes an agent cant reopen the thread without an approved template. Does the MCP surface that state back to the agent?

@paletmiki WhatsApp is a strong surface for agents because it is already where a lot of real customer conversations happen. The important part is making the API reliable enough for handoffs, approvals, and context history — not just sending and receiving messages.

Congrats! I tried your platform and the setup was smooth, good docs too

Just recently started using Zernio, but it works great and was super simple to set up!

Congrats on the launch Miki and team! Dealing with the official Meta API for WhatsApp is usually a nightmare, and the existing BSPs always take a huge cut per message. Love that you guys are offering the raw Meta pricing with zero markup. Definitely giving this a try for my next project!

I was going to post something like "great product" or "congrats on the launch"… but I've known the Zernio team for a while and always admired how they work, so I mean this: I already loved what they were doing on social, but folding in the full WhatsApp Business API is another level.

Having it all in one place (messages, broadcasts, group chats, even routing calls to AI agents) takes a ton off your plate.

Congrats on the launch. If you're building anything on WhatsApp, take a look. Probably the best API out there.

the "zero markup on usage" line got me. dealing with Twilio's WhatsApp pricing on top of Meta's fees was killing margins on a project last year. having messaging, calls, and AI agent routing all in one integration without the markup games is exactly what i would've wanted. the MCP server being hosted is a nice touch for agent workflows too. curious how you're handling rate limits when multiple AI agents are hitting the same number concurrently?

Hey Zernio team! 👋

Congratulations on the launch! 🎉

I love the idea of a unified social API. Handling multiple APIs and auth flows is a pain, so one layer for publishing, inbox, analytics, and account management is super valuable.

We're also launching Blazly Backlinker today, helping marketers automate backlink discovery, outreach, and guest posting from one workflow.

Would love to hear your thoughts if you get a chance to check us out as well. Best of luck with the launch! 🚀

I love Zernio! I'm really happy I've discovered it a few months ago which saved me tons of hours of Metas awful APIs. Zernio is now the backbone of my own app. Great work guys!

Is any meta account linking required for these WhatsApp numbers? AFAIK, meta is really aggressive with marking things spam and with recent mass Instagram accounts banning fiasco, more so

Hey, I have started using Zernio and it's so smooth to integrate and work flawlessly!

Over 6 month in production with the WhatsApp SDK and it's running very smooth! Never had major issues and I love how much the team improves the product constantly, especially the WhatsApp connection. Heads up to the team for making it easy to connect with my clients and customers through their favorite channel 👍🏽
Keep building, keep moving
Leon 🐒

The channel line up is crazy @dasha_nazarova1

Does this mean through Zernio, there could also be 2-way AI-assisted Whatsapp conversation also possible?

And we all know how tricky it is to get things done through Meta, would Zernio assist in the process in case there are issues connecting and setting up Meta + WhatsApp?

Excited to explore this further during the weekend.

I think Zernio is so cool. We use it ourselves. I think they are just adding more and more massive advantages and just enable you to scale and build content and workflow distribution across multiple channels. Huge respect.

wow this is huge, congrats on the launch!!

WhatsApp API and dev experience are quite challenging, you solution seems very interesting! Do you have a list of all the use cases that you solution enables?

This looks awesome excited to try! Congrats on the launch @paletmiki

This is really cool! Having messaging, calls, and AI agents all through one WhatsApp API is a huge deal for developers. Quick question — does it support sending media files like images or PDFs in messages, or is it mainly text-based for now?

We haven't tested the WhatApp connection yet, But look forward to deploying it for our customers. I'm sure it's top notch as their other products which we have been testing for several months now. Keep up the good work, team! 🤘

Congrats on your launch. Wishing you the best!!

The calling + AI agents combo in a single API is what makes this stand out - most WhatsApp integrations I've looked at just cover messaging. Been thinking about building something that handles voice callbacks automatically and the current options are painful. Question for the team: how does the rate limiting work when you're running outbound AI agent campaigns at scale? That's usually where these tools hit unexpected ceilings.

Hey PH community!!

Carlos here - the Product Evangelist at Zernio, basically the guy whose job is to make noise about this thing across X, PH, and wherever you hang out.

Joined the crew a month ago and immediately got thrown into the fire. The team was already shipping at warp speed (small team, bootstrapped, zero bullshit), but my mission is crystal clear: get this API in front of every solopreneur, AI agent builder, and tool maker who's tired of wrestling with 15 different platform APIs just to ship social features.

I've been out here posting, threading, and hunting conversations with you guys — the real ones building in public.

Watching this tiny squad (5 people max) ship features that save months of eng time has been wild. No VC theater, just raw execution.

So if you're a builder embedding social into your product, cooking autonomous agents that actually act on X/IG/TikTok, or just tired of the integration tax... hit me up.

Now we are on PH to make Zernio BIG. 🚀

WhatsApp is such an important channel for SMB workflows because it mixes support, sales, reminders, and relationship management in one place. The MCP angle is interesting. How do you think about guardrails for AI agents using WhatsApp: template approvals, human handoff, and preventing an agent from over-messaging a customer?

Strong launch. WhatsApp is one of those surfaces where the guardrail matters as much as the API call.

For agent workflows, I’d want a pre-send state check: window open or closed, template required, last inbound timestamp, and handoff owner. Are you planning that as a helper, or leaving it to builders?

Congrats on your launch. The thing I'd want to understand as someone building a product on top of this: if each of MY customers needs their own WhatsApp number connected, how painful does that get at scale? Can I wrap Embedded Signup into my own onboarding so a non-technical customer connects their WABA in a few taps, or does it always route through Meta's flow? Multi-tenant provisioning is usually where WhatsApp infra falls over. Great launch regardless.

Really surprising direction from Midjourney... a successor to the MRI and a spa in downtown San Francisco??

Check out the details of how the Midjourney Scanner works:

https://www.youtube.com/watch?v=uP2Xn3WUnoI

The system involves (source):

• 8,960 transducers per chip/system

• 40 systems arranged in a ring

• 358,000 ultrasonic elements total

• A 70 cm diameter ring

• Waves traveling through water at about 1,481 m/s

• Data capture around 17 GB/s

• Around 40 GB of data per body slice

• Reconstruction using 21 servers

• Claimed 2 PFLOPS compute

• Claimed 806 TB raw data

• Lift movement at 4 cm/s

• Goal of several hundred slices in 60 seconds

• Claimed resolution of internal tissue details down to about 0.5 mm

Had to double check to make sure this was the same Midjourney that does AI image gen. Didn't expect this!

Such an interesting idea. A 60-second body scan that people can do regularly sounds genuinely useful. How accurate is it, and what can it detect today?

This is genuinely fascinating — a full body scan in 60 seconds with no radiation sounds like something out of sci-fi. I'm curious though, is the scanner something you visit at a Midjourney Spa location, or will it eventually be available for clinics and hospitals to use too?

This is a pretty unexpected direction for Midjourney, but it's interesting to see the brand branching out beyond creative AI.

Hey Product Hunt 👋 Eric, Caleb, and Nick from Firecrawl here. Today we're launching the Firecrawl Research Index, a specialized index for agents pushing the frontier of AI/ML research.

AI/ML research moves fast, and the work that matters is split between new papers and the code that implements them. Most search providers omit or misrank key papers, leaving you to review sources by hand without ever being sure you've caught everything.

So we built an index for it. Firecrawl's index includes all 3M+ arXiv papers, as well as GitHub artifacts from top research repos, refreshed daily so agents always stay current.

On arXivQA, the index has state-of-the-art recall, 18% above the next best provider at similar cost. It also scores 0.750 MRR, meaning the correct paper lands in the top two results. Your agent finds the right papers, right away.

Plus, the index ships with a complete research toolset. Agents can retrieve papers, verify claims against the full text, and pull code for implementation - running the full research loop end-to-end. An agent training a model overnight could pull an optimizer from a recent paper and a stability fix from a related GitHub issue, then test both in its next run.

Firecrawl Research Index is available now in the API via /search/research, CLI, MCP, and SDKs, and plugs into any harness you already run (Codex, Claude Code, or Grok Build).

Try it here: https://docs.firecrawl.dev/features/research

We'd love to see what you build with it.

The indexing isn’t the hard part, it’s the finding of what papers make earlier papers obsolete.

Or, not only that, it’s the understanding that many papers (even recent ones) are irrelevant. You’ll get agents touting results, only to read the paper and see that the conclusions are based on GPT 4o, which for many purposes has more in common with the Apollo guidance module than current models trained with reinforcement learning.

Okay fine, that’s a bit too hyperbolic, but really: the changes in training paradigms just make a huge corpus of research not very applicable to current LLMs, and that’s a point that models skip right over.

I don't do ML research, I build production agents, but the core pain here is universal: agents quietly acting on stale or misranked sources and nobody noticing until it bites. Pairing each paper with the code that implements it, refreshed daily, is the clever bit. Curious whether you'll extend that same "source + the thing that implements it, kept current" idea beyond arXiv to general docs/APIs, because that's exactly where my agents drift. Nice launch.

This is useful. For research agents, the part I’d want surfaced is provenance per downstream step: which paper, which repo or issue, which claim, and what changed in the experiment because of it.

Does /search/research return enough citation structure for an agent to keep that trail, or is that on the harness?

3M+ arXiv papers plus GitHub artifacts all in one index refreshed daily is seriously impressive. The recall benchmark results are pretty convincing too. I'm curious — does the index also cover papers from conferences like NeurIPS or ICML, or is it purely arXiv-based right now?

Getting state-of-the-art recall on arXivQA is legitimately hard. The tricky bit isn't crawling the PDFs. It's parsing structured content from LaTeX source vs. the rendered PDF without losing math notation and figure references. We've spent time on similar extraction challenges when pulling structured data from dense technical documents. What does your indexing pipeline use for equation and table extraction from arXiv source tarballs?

This is cool. How do you decide which GitHub repos qualify as top research artifacts?

Hey Eric! IT's truly impressive. 3M+ papers is more than enough to make researches that actually matter. Love to see you helping on this and wish you all the best!

@ericciarla congrats! Will definitely try it

Hey Product Hunt 👋

I built API To MCP because AI agents are getting smarter, but connecting them to real business APIs is still too hard.

Most teams already have valuable systems: CRMs, ERPs, support tools, finance dashboards, internal APIs, and SaaS platforms like Google, Meta, GitHub, Notion, Shopify, and Slack. But turning those APIs into something ChatGPT, Claude, Codex, Cursor, VS Code, Antigravity, or custom agents can actually use often requires custom engineering.

API To MCP helps you turn REST or GraphQL APIs into hosted MCP servers.

You can build visually from the dashboard, or connect the API To MCP Manager MCP to an AI coding agent and let it create, test, deploy, and update MCP servers from chat.

Today it supports:

- Hosted remote MCP URLs

- REST and GraphQL APIs

- API Key, Bearer, Basic Auth, OAuth2 Client Credentials, and per-user OAuth

- Workflow tools and JMESPath response mapping

- Live MCP servers and forkable snapshots

- Public MCP directory

I’ve worked hard to make the product stable for launch day, but this is still an early version. If you run into any issues while trying it, I’d really appreciate your feedback.

I’d love to hear:

1. What API would you turn into an MCP server first?

2. Would you rather use a live MCP directly, or fork a snapshot and add your own credentials?

3. What would make this easier for non-technical users?

As a launch thank-you, all paid plans are 30% off during the Product Hunt launch period.

Thanks for checking it out. I’ll be here all day answering questions.

The forkable snapshot idea is the part I would want to test first.

Turning an API into MCP is useful, but the hard production question is usually: can I freeze the tool contract that an agent saw, review it, and then safely promote it to a live credentialed server?

For a first useful workflow, I would look for:

• import an OpenAPI or GraphQL spec

• - generate a small MCP tool set

• - run one real read-only call

• - inspect the exact schema and mapped response the agent receives

• - fork a snapshot before adding write actions or user OAuth

• - diff the live server against the snapshot after API docs change

That kind of review trail would make API-to-agent wiring much easier to trust, especially for internal business APIs where a wrong write action is worse than no automation.

Definitely adds a lot of value. How do you handle auth scopes when different agents should get different tool access, like read-only CRM vs write/update access?

This solves a real headache. Setting up MCP servers from scratch for every API is tedious, so being able to just point it at a REST or GraphQL API and have it generate the server automatically is a big time saver. Does it handle authentication flows like OAuth or API keys automatically too, or is that something you configure manually?

Can you pin a snapshot version for an agent so updates don’t change behavior mid workflow?

This is a really amazing use case. Can it support internal microservices spec like grpc?

The live vs forked MCP split is the right product question. I’d be curious how you want teams to carry policy with the fork: allowed actions, credential scope, approval rules, and a receipt after a write. Otherwise the fork solves setup, but production teams still have to prove what an agent changed.

One API for the whole WhatsApp Business stack, calls included, is exactly what I wished existed last time I built on WhatsApp. The hosted MCP server is a great touch for agents. Congrats on the launch!

Wrapping heterogeneous APIs behind a unified MCP layer is a smart abstraction. The hardest part isn't the HTTP adapter. It's auth propagation across OAuth, API keys, and custom schemes without leaking secrets into agent contexts. We've hit this friction proxying third-party integrations in multi-tenant setups. How do you handle token refresh when an OAuth TTL expires mid agent tool call?

This solves a real bottleneck: business systems already have APIs, but agents need a safer execution layer. Curious how you handle permission boundaries. Can an MCP server expose different actions by role, for example read-only CRM access for one agent and write/update access for another?

Hey! 👋

Congrats on the launch of API to MCP! 🚀

I really like how you're helping developers bridge existing APIs into the MCP ecosystem. With AI agents becoming more capable, reducing the friction between APIs and MCP tools feels incredibly timely and useful.

We're also launching Blazly Backlinker today, helping marketers automate backlink discovery, outreach, and guest posting from a single workflow.

Would love to hear your thoughts if you get a chance to check us out as well. Wishing you a fantastic launch day! 🎉

Congrats on the launch! 🎉 I gave API To MCP a try and was genuinely impressed. Setup was surprisingly simple, everything worked smoothly out of the box, and the overall experience was very polished. Turning APIs into MCP servers has never felt this easy. Great work to the whole team and wishing you a successful launch! 🚀

The forkable snapshots idea feels useful. Teams may want to try a live MCP quickly, but still need control over credentials, auth, and mappings before using it seriously.

Hi everyone!

UE 5.8 is the last big update before Epic moves on to UE6.

One interesting part is the experimental MCP plugin.

It lets AI agents connect to the Unreal Editor, understand the engine and the current project, and help with assets, systems, testing, and optimization.

So is it the right time to vibe code some real games? :)

btw, you don’t need to pay Unreal royalties until your game hits $1M.

5.8 also adds Sandboxes. You can experiment in an isolated space, keep only the changes you want, and avoid polluting the main project.

Mesh Terrain is another fun one: a new 3D mesh-based terrain system, so worlds are no longer limited to heightfields — much more room to play!

The native MCP plugin is the most exciting thing here for me — letting AI agents hook directly into the Unreal Editor for asset management and optimization is a totally new workflow. Curious, is the MCP plugin going to be open source or is it locked to specific tools/agents?

Interesting timing on this since UE6 is already being teased. Feels like the AI agents feature was added late rather than something core to the release - the implementation seems pretty surface-level from what I've read in the docs. Would have been more useful to ship this 6 months ago when people still had runway to build on 5.x. For new projects starting today it's hard to justify building on something the team has already mentally moved on from.

this is so cool, Santiago!

This feels like a tiny internet stock market with digital graffiti. I love that it embraces randomness instead of optimization.

This has been extremly fun already. I build this during a hackathon last weekend, and shared it live with a room full of amazing builders. The feedback was great and it got some initial traction. It has already been a great way for some people to learn about agentic payments and MPP.

I did this video showing a bit more how the interactions(buying a square, adding an idea, comments and votes) work for MPP: youtube.com/watch?v=fkT9oVAZ0Vs&feature=youtu.be

More than happy to answer questions and/or help anyone get onboarded to agentic payments, tempo, mpp, etc!

The clever part is you can't click to buy, you have to wire up MPP to play. Quietly the most fun onboarding to agentic payments around. Congrats @dfect

This is awesome. Things are gonna get wild with agents soon and this is exactly the kind of weird, fun experiment that gets us there. Curious to see where this goes 🔥

RBR holding a square made me grin — I was at the SF edition, so seeing what CDMX shipped (and RBR flipping its own slot) closes a fun loop.

The squares are the hook, but the 402 checkout is the real unlock — an agent settling USDC on Tempo from one npx skills add beats any "agents will pay someday" slide. If I pointed mine at a slot I'd just tell it to maximize clicks and see what it argues for.

One note: getting outbid on a small square only returns your money — no bonus like the mediums and larges — so the five smalls read more as ad space than a flip. Looks like the board already feels it (top idea: give smalls at least 1.1×). Either way, fun to watch.

Is it a bird? Is it a plane? Is it an ad product? Is it the gamification of advertising? 🫪

I came in expecting one thing and left with a lot more questions. The squares are interesting, sure, but I'm even more curious about the people: what they'll promote, who'll join first, and what behaviors this incentive system ends up creating.

Can't wait to see how this weird little experiment unfolds.

Congrats on the launch! 🚀

This scratches an itch I didn't know I had. there's something genuinely fun about ad buying that feels like a game rather than a dashboard. Love how the incentive structure makes every slot a story.

Side question for @dfect are you tracking earnings per slot over time anywhere? Curious if you'd ever expose that data publicly as part of the experiment. Would love to see what the "best" slot ROI looks like over a month.

Congrats!! I loved the "play 2048 while you wait" feature! :D

The STUN-only approach is actually pretty cool.

Most tools saying "peer-to-peer" end up relaying traffic through their own servers when things get complicated.

Have you seen many transfers fail because of NAT restrictions?

Congrats on the launch!

browser-to-browser is the right default — but the part nobody shows is transfers behind symmetric nat quietly falling back to a turn relay. that relay's the one bit of 'no server' that isn't.

This is clever. Does resume work if the receiver accidentally closes their tab mid-transfer?

Hey! 👋

Congrats on the launch! 🚀

I love the simplicity of the concept. So many ideas get stuck in planning mode, and a product that encourages people to stop overthinking and actually ship resonates with every founder and creator.

We're also launching Blazly Backlinker today, helping marketers automate backlink discovery, outreach, and guest posting from one workflow.

Would love to hear your thoughts if you get a chance to check us out as well. Best of luck with the launch today! 🎉

The name is hard to ignore 😄Are there any practical limits on file size or transfer speed, but this looks really useful. Congrats!

Here come the Google Ad Agents -> @Google launches AI agent for Ad Manager.

Ask Ad Manager in Google Ad Manager is a new conversational AI agent built with Gemini.

It’s designed to help publishers make faster, more informed decisions by uncovering new insights and automating manual processes right in the UI.

Here is a look at what it can do:

🔍 Faster troubleshooting: Instead of manually sifting through reports, now, you can ask, "Why isn't this line item delivering?" Ask Ad Manager will analyze the situation, diagnose the root cause, and provide the steps to fix it.

📊 Deeper insights: Ask complex questions (e.g., "How are my top bidders performing this week?") and get actionable data tables to help you decide on new pricing rules or programmatic deals – without having to the page you’re working on.

🧭 Smarter navigation: Save clicking around the UI as Ask Ad Manager can take you directly to the right campaign page with all the correct filters and settings pre-loaded.

Because Ask Ad Manager is grounded entirely in your own first-party data, the guidance is personalized to your specific business and setup. (And importantly: your data is never used to train our models or shared with anyone else.)

Ask Ad Manager is rolling out in beta this month, with a wider rollout planned for later this year.

P.S. I hunt the latest and greatest launches in tech, SaaS and AI, follow to be notified → @rohanrecommends

The hard part in advertising is rarely getting more data, it is deciding what to do with it. Does Ask Ad Manager explain why it recommends a fix or pricing change, and does it separate diagnostic suggestions from actions that should need human approval?

Great timing on this. the publisher analytics space is finally getting some love. The challenge I keep hearing from AdSense and AdMob publishers isn't the depth of data inside GAM, it's that their revenue is spread across multiple Google properties with no single place to see everything together. They're opening AdSense in one tab, AdMob in another, YouTube Studio in a third just to get a morning number.

Curious whether Ask Ad Manager will eventually help publishers who are running across multiple platforms (not just GAM), or is it scoped to GAM-specific inventory for now?

This is neat. How does it handle ambiguous questions that could map to multiple report dimensions?

Sounds useful. The challenge isn't usually getting data, it's turning it into decisions. Curious how the agent handles that.

When Ask Ad Manager identifies a delivery issue or recommends a change what level of transparency does it provide into the reasoning behind that recommendation? For advertisers managing large budgets, understanding the ‘why’ is often as important as getting the answer.

I like that Backlinker tries to bring the whole process into one workflow, especially for founders or small teams that don’t have a dedicated SEO person.

The big thing I’d be curious about is quality control. How do you make sure the outreach stays relevant and not just “more automated backlink emails”? Do users get to review and approve opportunities/emails before anything is sent?

Also curious how you define a good backlink opportunity: domain authority, topical relevance, traffic, competitor links, or a mix of all of these?

Hey Everyone!

We're excited to introduce Blazly Backlinker.

Link building is one of the most important parts of SEO, but it's also one of the most time-consuming. Most teams still juggle spreadsheets, prospecting tools, email finders, AI writers, outreach platforms, and follow-up systems just to earn a few quality backlinks.

We thought there had to be a better way.

So we built Backlinker to automate the entire workflow:

🔍 Discover relevant backlink opportunities
📧 Find verified contact information
✍️ Generate personalized outreach emails with AI
📝 Create guest post content faster
📊 Track outreach and backlink acquisition in one place

Our goal is simple: help marketers, agencies, and founders spend less time on manual outreach and more time growing organic traffic.

🎉 Product Hunt Launch Offer: Purchase our Starter Plan and get access to the Growth Plan ($99 value) for first 3 month as part of our launch promotion.

We're still improving the product and would love your feedback:

❓What's the most frustrating part of your current link-building process?
❓Which backlink-building tasks would you love to automate?

We'll be here all day answering questions and collecting feedback.

Thanks for checking out Blazly Backlinker! 🚀

The review-before-sending flow is important here. Backlink outreach can go wrong fast if it feels automated, so keeping humans in control while automating prospecting, contacts, and drafts makes sense.

🎉 Special Launch Offer for the Product Hunt Community!

As a thank you for all the support, anyone who purchases our Starter Plan during the launch will receive access to our Growth Plan (worth $99/month) for your first 3 months.

If you're looking to simplify backlink prospecting, outreach, guest posting, and tracking, this is a great opportunity to get started.

Thanks for being part of our launch journey! 🚀

Anyone who's done link building knows the outreach isn't the hard part anymore. Finding genuinely relevant opportunities is. Nice to see a tool focusing on that workflow end-to-end. Congrats on the launch!

Congrats ! What sources are you monitoring to discover backlinks opportunity? Is that only searching for guest post or also PR/marketplaces/directories?

How do you pick opportunities that are actually relevant and avoid burned domains or bad links?

the notch as a drop target looks like a genuinely good call! its dead space on every mac I guess. Congrats on the launch!

the notch-drag-into-slack flow is the whole game — make-or-break is the clip being encoded on disk before i grab it vs a file-promise finishing on drop. that gap is where most capture tools fumble.

The drag-from-notch workflow feels really practical. For quick bug reports or UI feedback, skipping uploads, links, and extra sharing steps could save a lot of small interruptions.

The notch integration is actually clever - been ignoring that real estate for 3 years and this is the first tool that makes it feel like a feature rather than a design compromise. The drag-to-share flow is the kind of thing that sounds gimmicky until you use it and realize you've been doing it the slow way forever. Does it handle multi-monitor setups where the notch screen is secondary? That's the one edge case I hit constantly with menu bar tools.

Looks clean. Native macOS apps that do one thing really well are becoming surprisingly rare.

Hey QuackScreen team! 👋

Congrats on the launch! 🚀

Capturing, dragging, and sharing directly from the MacBook notch is such a clean use of existing hardware. I love products that turn something people overlook into a genuinely useful workflow improvement.

We're also launching Blazly Backlinker today, helping marketers automate backlink discovery, outreach, and guest posting from one place.

Would love to hear your thoughts if you get a chance to check us out as well. Wishing you an amazing launch day! 🎉

The persistent memory angle is what caught my attention. Re-explaining the same project context to AI tools every session gets old fast. Congrats on the launch!

Nice. The separate terminal context is a good start. The thing I’d want next is a tiny run record for each agent task: what it was allowed to touch, which terminal or repo it used, what changed, and what should be carried into memory after the run. Is that how you’re thinking about the temporary context layer?

Having terminals, tasks and AI in the same workspace makes a lot of sense.

Out of curiosity, are the agents actually executing commands in the terminal, or do they operate through a separate execution layer?

Congrats on the launch.

Terminal workspace + agents is a solid combo. What was the biggest surprise about how people actually wanted to interact with their tasks once you shipped?

Persistent memory is the part that stands out. A lot of agent workflows fail because context disappears between sessions. How do you decide what should become durable memory versus temporary context, especially when multiple tasks or terminals are running in parallel?

Hi Product Hunt,

I am the solo creator of Screen Ruler, a Chrome extension that helps designers and developers inspect web pages.

For a long time it was strictly a measurement tool. But I kept hearing the same feedback from the community: you wanted to edit text on the page, reorder elements, and tweak CSS without leaving the browser. So I spent the last month or two building a brand new edit mode. It handles HTML edits, CSS tweaks, pseudo-state styling, and @media rules, with every change tracked so nothing gets lost.

Under the hood, it uses an Atomic CSS engine that stamps edited elements with a unique data-id and writes changes to a transient stylesheet. Every edit is scoped to its exact element, breakpoint and pseudo-state, with no cascade leakage to other contexts. So if you want to treat a live web page like a design canvas, this is for you.

Would love your feedback. Thanks for taking a look.

Making CSS edits work inside :hover and @media rules is the hard part. Most tools show computed styles, but resolving which rule is winning the cascade and exposing it as something editable requires careful CSSOM traversal. When building embeddable components, we've hit similar specificity headaches. How do you implement live :hover editing without injecting a forced class or inline style override?

As a developer, I often end up opening DevTools just to tweak spacing, margins or font sizes and see what feels right.

Having a dedicated workflow for that with change tracking seems much more practical than losing everything after a refresh.

Nice work and congrats on the launch.

Nice update. The change tracking is the interesting bit, especially when a designer is editing a live app with a developer.

Do you export the change list as CSS/selectors or more like a visual snapshot, so someone can turn the tweaks into a real PR later?

This could be one of those tools you don't know you need until you've used it once and then can't go back. Inspecting margins/paddings on competitor sites is a daily task for solo builders without a design background.

Does it work on sites with heavy CSS modifications (Tailwind, shadcn variants), and is there a way to export measurements or snapshots for later reference?

Nice! I was using the Page Ruler extension before. It works, but I had a lot of trouble with the position of the measurements and numbers. Screen Ruler is better because I can easily measure components on the screen. You could add a free mode (unless I missed it) where I can select exactly what I want to measure

Hey! 👋

Congrats on launching Screen Ruler! 🚀

Such a simple idea, yet incredibly useful. As a designer, I constantly need to measure spacing, alignment, and dimensions on screen, and having a lightweight tool dedicated to that workflow is a real productivity booster.

We're also launching Blazly Backlinker today, helping marketers automate backlink discovery, outreach, and guest posting from one workflow.

Would love to hear your thoughts if you get a chance to check us out as well. Wishing you a fantastic launch day! 🎉

Strong launch. I like the split between model planning and a separate execution layer. For security work, the useful artifact is not only the report, it is the chain from target scope to authorized tool to command output to finding. Do you keep that run record exportable for client or audit review?

What’s the setup like to run a full assessment, and can you plug in your own tools or internal scanners?

The 'costs doubled, answers worse, then customers started complaining' sequence is the most relatable AI horror story I've seen this year. Finally something that catches it before the Twitter thread starts. Congrats on the launch!

Agent observability feels like it will become mandatory. For business agents, the question is not only cost/tokens, but “what did the agent try, why did it decide that, and when did it need human help?” Are you thinking about business-level traces like handoffs, approvals, and failed workflow outcomes?

Congrats on launch! I would love to know how is it different to other observability platform like langfuse/Arize?

@gustavofior Visibility is a big missing layer for agents. It’s hard to trust an autonomous workflow if you can’t see what it tried, where it failed, and what changed along the way. Agent observability will probably become a default expectation.

Super interesting! What does Intent mean?

Congrats on the launch! What other languages does it support other than English? Does it perform well in noisy environement?

How is this different from handy.computer ?

@Handy does the same thing for free + open-source.

I can also select models taht I want. Completely local.

Would love to know your thoughts on this.

The offline and local-first approach is what stands out to me. Feels like a refreshing change from everything being cloud-based these days.

The "source text to spoken script to AI audio" pipeline is something I'd genuinely use. I run a podcast on financial modeling (ModeLoop Podcast on Spotify) and the unglamorous reality is that turning written research into something that sounds natural out loud is most of the work. A multi-voice script editor that handles that transform in one place could cut my prep time a lot. Does it hold up for longer-form, dialogue-style episodes, or is it best for shorter narration?

Hi Product Hunt community! 👋

I'm Aarav, the solo developer behind Prism, and I'm incredibly excited to share it with you all today.

**What inspired me to build Prism?**
Like many of you, I found myself constantly switching back and forth between different browser tabs just to use various AI models for coding, writing, and research. Web-based AI tools felt slow, clunky, broke my focus, and lacked any real integration with my Mac's operating system. I wanted a fast, native tool that fit perfectly into the macOS experience, but existing AI wrappers were either locked to a single model provider or felt like web views inside a container.

**The problems I wanted to solve:**
1. **Multi-Model Access in one place:** I wanted to switch between Anthropic (Claude), OpenAI (ChatGPT), Google (Gemini), Grok, Kimi, and local offline models (via Ollama) instantly under one beautiful, native SwiftUI interface.
2. **True System-wide Utility:** I wanted to quickly pull up AI without breaking my flow. So, I built a Spotlight-like **Quick AI Panel** (summoned instantly with `Ctrl + Space`), a system-wide writing assistant, project knowledge bases, and custom prompt templates.
3. **Power-user Features:** Beyond chat, I needed tools that competitors lacked—specifically **Model Comparison Mode** (sending a prompt to multiple models at once and synthesizing the best parts), local **browser automation** (Playwright/Puppeteer), and built-in **study creators** (quizzes and spaced repetition flashcards).

**How Prism evolved during development:**
What started as a simple menu bar shortcut quickly turned into a deep OS-level productivity suite as I integrated developer tools (like the Prism CLI and IDE proxies). As I worked toward this launch, privacy became a top priority, leading me to build robust local-first privacy options, support for private offline models (Ollama & Apple Intelligence), and optional iCloud history sync.

Prism has a permanent free tier, an affordable hosted plan, and a **Lifetime License** (you can use code **SPECIAL25OFF** at checkout for 25% off during launch week!).

I’m actively shipping updates based on user feedback. I would love to hear what features you’d like to see next or how Prism can better fit into your day-to-day workflow. Please let me know what you think! 🚀

The Quick AI Panel and multi-model switching feel like the strongest parts here. Having Claude, ChatGPT, Gemini, Grok, Kimi, and local models in a native macOS flow could save a lot of context switching.

Strong framing. The hard part with analytics agents is usually not the chart, it is what happens after the answer gets trusted. If someone turns an insight into a report, Slack update, or downstream task, do you keep that action trail in the same context layer or outside it?

Can you set different permission levels so some users can ask questions but not trigger write actions?

Hi Product Hunt! 👋

I am incredibly excited (and honestly, a little terrified) to finally share Portia with you today. 🕷️💜

Here is a confession: I am not a macOS developer. I had zero prior experience with Swift, Apple’s strict sandboxing rules, or the complexities of Xcode. But I had a massive, daily frustration that every developer here knows too well: the dreaded EADDRINUSE error.

Like everyone else, I was tired of opening the terminal, running lsof -i :8080, finding the PID, and typing kill -9. I wanted a beautiful, native, 1-click solution that lives in the menu bar, or even works in the background instead of me.

Since I didn’t know how to code a native Mac app, I decided to partner up with AI as my virtual Senior co-pilot. 🤖

It wasn’t a "generate an app in 5 seconds" kind of journey. It was a long weekend of heavy prompt engineering, architecture planning, overcoming Apple Sandbox limitations, and making sure the app runs with 0% idle CPU and absolute system safety. The result is Portia verbatim: a production-ready, ultra-fast, premium native utility that works flawlessly.

We are launching two versions today:

🌎 Portia Lite (Free on the App Store): It runs in a sandbox and helps you find the your blocked port, allowing you to track down the issue.

⚡ Portia Full ($4.99 direct download): A non-sandboxed version with a background Launch Agent that lets you view the exact process path and kill (Strike!) the blocking process in exactly 1 click.

Building this proved to me that AI can truly democratize software creation if you guide it right. I’d love to hear your thoughts, feedback, and stories about your own battle with zombie processes!

I’ll be here all day to answer your questions. Thank you so much for the support! 🚀

This is one of those super simple tasks that take me several minutes to remember how to look for that one rouge node server running I forgot about. Nice!