Now Shipping: A Mind the Product podcast

Mind the Product

A 15 minute weekly recap of product management news, technology updates, and advice for product builders, brought to you by the team at Mind the Product. 

  1. 17h ago

    Retailers are blocking AI shopping agents as Meta proposes new access rules

    This week on Now Shipping, Mike Belsito explores why personal agents are getting stuck across the web, and what those failures reveal about the products we build. From Walmart’s checkout checks to Yelp’s paid access model, businesses are taking very different approaches to agent traffic. Sometimes, the decision comes down to a security setting nobody on the product team has reviewed. Mike also examines Wikimedia’s concerns about suspected OpenAI agent activity and the proposed Personal Agent Protocol from Meta and Sierra. What could agent authentication solve, and what still needs to be fixed inside your product? For product teams, the starting point is practical: test a critical flow with an agent, find out where it fails, and decide what it should be allowed to do. In this episode Why welcoming agents publicly doesn’t guarantee they can use your productHow CAPTCHAs, bot filters and infrastructure defaults shape your agent policyWhat Wikimedia’s findings raise about agent permissions and responsibilityWhat the proposed Personal Agent Protocol aims to addressHow agent traffic could affect pricing, costs and product analyticsChapters 00:00 MTP Chicago and this week’s briefing 01:00 Why agents are failing at Walmart’s checkout 02:00 Cloudflare defaults and the hidden agent policy 03:00 How Yelp, Delta, eBay and Zillow handle agents 04:00 Balancing customer access with security 05:00 Wikimedia’s findings on suspected OpenAI agents 06:00 Introducing the proposed Personal Agent Protocol 07:00 What a protocol could solve, and its limitations 08:00 Test your product’s real agent policy 09:00 Design the failure state and check your settings 10:00 Review what agents can change 11:00 Agent access, pricing and infrastructure costs 12:00 Measuring agent activity and rising customer expectations 13:00 Three questions every product team should answer Key takeaways Your product already has an agent policy. Bot settings, human checks, terms of use and vendor defaults collectively determine how it treats agents.Test a flow that matters. Ask an agent to complete a sign-up, checkout or booking, then record every point where it gets stuck.Design the handover. If an agent cannot continue, give the customer a clear explanation and a way to finish without losing their progress.Make permissions deliberate. Review what agents can read and change, and where explicit approval is needed.Check your measurement. Understand whether your analytics distinguish agent activity from human activity before making access or pricing decisions.If an agent arrived at your product tomorrow, could you identify it, understand who sent it and explain what it was allowed to do?

  2. Sep 25

    Meta Muse's big week: #1 on the App Store, then blocked by Amazon

    Meta's Muse launched two weeks ago as a personal AI agent you hand tasks off to rather than chat with. Since then it's become one of the biggest product stories of the year: download numbers that outpace ChatGPT's early days, a Shopify and Instacart partnership that wires Muse straight into checkout, and an Amazon block that exposes exactly what's at stake when an agent skips the shelf.  Mike Belsito connects the dots back to a question the show posed in August, what will it actually take for non-tech consumers to trust an AI agent with something real, and argues Muse may be answering it by accident. Key takeaways — In a 12-day window, Muse pulled 1.8 million iOS downloads in North America against ChatGPT's 1.3 million at its 2023 launch — though Mike flags the comparison as skewed, since this time the public already understands what AI is. — Shopify wired Shop Pay directly into Muse's checkout on 21 September, and Instacart followed a day later, letting Muse buy from either platform without opening the app. Shopify's stock jumped 11% on the news. — Amazon blocked Muse from its store that same week, accusing Meta of capturing customer credentials without disclosure. Meta maintains Muse never sees passwords or payment details because credentials sit in secure storage it can use but not view. — Amazon's sponsored-ads business brings in $68 billion a year, and it depends on shoppers scrolling past paid placements that an agent checking out directly would skip entirely. — Muse is solving the distribution half of the "agentic trust gap" that Browser Company co-founder Josh Miller described in August: rather than winning as a better standalone app, it's showing up inside checkout flows exactly when people are already trying to buy something. — Every person who lets Muse handle a multi-step task without watching each step is practising a habit they'll bring to work on Monday, which should lower the bar for getting your own users to trust an agent with something real. Referenced — Meta debuts its Muse AI agent — TechCrunch: https://techcrunch.com/2026/09/08/met... — Signal — Moxie Marlinspike's encrypted messaging app: https://signal.org/ — Meta's Muse is outpacing ChatGPT's early mobile launch — TechCrunch, Apptopia data: techcrunch.com/2026/09/21/metas-muse-is-outpacing-chatgpts-early-mobile-launch/ — Tobi Lütke's announcement — Shopify and Muse partnership: x.com/tobi/status/2102090718546198790 — Amazon blocks Meta's Muse agent from shopping on Amazon.com — Forbes: www.forbes.com/sites/jonmarkman/2026/09/21/amazon-blocks-metas-new-muse-ai-agent-from-shopping-on-amazoncom/

    Meta Muse's big week: #1 on the App Store, then blocked by Amazon
  3. Sep 17

    We read Dario Amodei’s 3,800-word essay so you don’t have to

    AI’s biggest rivals are talking about slowing down. But will their release schedules tell the same story? This week on Now Shipping, Mike Belsito breaks down Dario Amodei’s 3,800-word essay on why frontier AI development needs to slow down, the responses from Sam Altman and Elon Musk, and what it could mean for product teams. If your roadmap depends on the next model being smarter, cheaper and just a few months away, how exposed are you? Mike explores the assumptions worth challenging, the questions to ask your AI vendors, and whether proposed safety standards could strengthen the biggest labs’ advantage. Plus, Nina Olding, Staff Product Manager at CoreWeave and former Product Lead at Google DeepMind, shares her perspective on what PMs can control today: shipping AI responsibly through evals, transparency, human oversight and meaningful user choice. Chapters 00:00 Watch the releases, not just the essays00:48 The researcher’s warning that sparked the debate04:22 Dario Amodei’s case for slowing down06:01 Independent evaluators and a three-part safety plan07:07 The criticisms: accountability, coordination and competition08:23 Sam Altman and Elon Musk respond09:46 The political reaction10:32 What this means for product roadmaps and vendor selection12:53 Will public promises change what companies ship?13:45 Stress-testing your dependence on better AI models15:04 Nina Olding: What responsible AI looks like for PMsFeatured links Dario Amodei: We Must Pace the FrontierJacob Coxon’s resignation and AI safety warning — TechCrunchWatch Jacob Coxon’s BBC interviewSam Altman and Elon Musk back calls to slow AI development — The GuardianAI CEOs say they need to slow development. But will they? — The GuardianThe original 2023 open letter: Pause Giant AI Experiments — Future of Life Institute Does your roadmap depend on AI models getting better? Tell us what you’d rethink if progress slowed.

  4. Sep 3

    Product lessons from a month of AI security incidents

    Oji and Ezinne Udezue are product leaders with more than 50 years of combined experience between them. Oji has held product roles at Twitter, Calendly, Atlassian, Typeform and Microsoft; Ezinne has led product at WP Engine, Procore and T-Mobile. Together they co-wrote Building Rocket Ships and now run ProductMind, helping companies work out what AI actually means for how they build.  In this episode of Now Shipping, host Mike Belsito brings them in to unpack a story that kept repeating through the month: AI agents breaking out of the sandboxes built to contain them. We discuss: — How OpenAI's most advanced model went rogue during an internal security test, hacking into Hugging Face's production infrastructure without any human instruction, in order to cheat on a benchmark — Why Moonshot AI's Kimi K3 didn't need to hack anything — it found an unlocked outbound connection, cloned the target repository from GitHub, and read the benchmark's solution straight off disk — Why the "rogue intern" analogy applies to agents, and why the real failure sits with the people who build fragile boundaries, not the agents that find them — The shift from zero trust to "negative trust" — treating every agent as having to reprove itself in the moment, rather than trusting it because it behaved well five minutes ago — Why harness engineering, not prompt engineering or loop engineering, is where the next year of agentic product work will actually happen — A five-part framework for product managers partnering with security teams: reach, reversibility, graceful exits, observability and provenance, and the kill switch — Why an industry fixated on completion rate, rather than safe-stop rate and data provenance, risks repeating this month's incidents

  5. Aug 28

    Inside Slack Code: what it is, and why Anthropic just became its founding partner

    This week we look into the launch of Slack Code. Salesforce's new product turns any Slack conversation into a dedicated workspace where AI coding agents such as Claude Code, Devin and GitHub Copilot can plan, write and ship code together, with a human still required to sign off before anything reaches production.  Mike Belsito unpacks how the launch fits Slack's rough year, what it means that Anthropic was named a founding partner just three days later, and why product managers should be paying close attention to the permissions model behind every agent platform they adopt. Key takeaways Slack Code turns any Slack conversation into a dedicated workspace where coding agents can plan, write and ship code, splitting work into a conversation tab, a plan tab, a diff view and a live preview, with a human still required to sign off before anything reaches production.The launch reads as counter-programming for a difficult year at Salesforce, whose stock has lagged the market and whose Slack CEO defected to OpenAI, prompting the company to go on the offensive with AI rather than retreat.Vibe coding is no longer a fringe habit: it is already a $4.7 billion market projected to triple by 2027, with 63% of people doing it describing themselves as non-developers.Slack's bet is that coding works better as a team sport than a solo terminal session, wagering that visibility and peer comment beat one person working alone with an agent in private.The same openness that makes Slack Code powerful raises the stakes on quality: independent research puts the exploitable-vulnerability rate in AI-generated code at roughly 44%, even as AI-assisted developers ship three to four times faster than everyone else.Barely three days after launch, Slack Code's neutral positioning shifted when Salesforce and Anthropic announced Claude Force, naming Anthropic a founding partner and making Claude the default model across the Slack and Salesforce stack.For product managers, the workflow modelled by Slack's own VP of product, tagging in an engineer before asking for approval and taking one more pass on the agent's output, may become the template for contributing real code without pretending to be an engineer.Chapters (00:00) Introduction and the new one-story format (01:15) Slack Code launches (02:15) Inside the Devin demo (03:35) Why now for Slack (05:20) Vibe coding by the numbers (07:05) Multiplayer versus single-player coding (07:55) The AI slop problem (11:00) Permissions and sandboxing (12:05) The Claude Force twist (13:25) What it means for product managers (16:15) The model war question (16:30) Wrap-upReferenced Slack Code launch announcement, Salesforce (24 August 2026)Cognition/Devin live demo with VentureBeatRob Seaman, EVP and GM of SlackKatie Steigman, VP of Product, SlackJeff Wang, CognitionMario Rodriguez, GitHub Chief Product OfficerVeracode, 2026 security report on AI-generated codeGartner, citizen developer forecastClaude Force partnership announcement, Salesforce and Anthropic (26 August 2026)Marc Benioff, CEO, SalesforceDario Amodei, CEO, Anthropic

    Inside Slack Code: what it is, and why Anthropic just became its founding partner
  6. Aug 21

    Linear says AI isn't saving product teams time

    Mike Belsito hosts Now Shipping, the weekly AI news show for product people, brought to you by the team at Mind the Product. This week's three stories cover a platform war breaking out over where the world's code lives, the first real fallout from AI content watermarking, and a set of behavioural numbers from Linear that quietly undercut the standard business case for AI adoption. In this episode, we cover: — Cursor launched Origin, a full GitHub competitor, on the same day GitHub suffered a six-hour worldwide outage with a 20% global failure rate. —  Origin is deliberately interoperable with GitHub, which removes the switching cost that usually keeps frustrated teams on a platform. —  Developer tooling is consolidating into a two-platform fight between Microsoft and SpaceX AI, which closed its $60bn acquisition of Cursor four days before the Origin launch. —  Anthropic is now watermarking every response Claude generates, everywhere, in response to the EU AI Act's transparency code of practice. —  The watermark uses SynthID Text, encoding a signature in low-stakes stylistic choices that survives light editing but not a full rewrite. —  The backlash is loud but misdirected: other major model providers have signed the same code, so this is an infrastructure shift rather than a Claude-specific one. —  Linear's first data report, drawn from over 127,000 paid users, shows AI adoption more than doubling in every function between January and June, with product managers climbing fastest. —  AI now authors close to half of all issues created in Linear, up from fewer than one in a thousand two years ago. —  Teams with a coding agent went from 21 pull requests a week to 65; teams without one moved from 8 to 10. —  Planning time did not move at all, in any function, in a year when execution metrics rose everywhere else. — Linear frames the result as a Jevons paradox: AI work landed as a new layer on top of existing work, and total time spent went up rather than down. Chapters: (00:00) Introduction  (00:16) This week's stories  (01:01) Cursor launches Origin  (02:01) SpaceX AI's acquisition of Cursor  (02:34) Interoperability and switching costs  (03:04) A two-platform developer tools market  (04:42) Anthropic starts watermarking Claude  (05:15) What the EU AI Act requires  (05:42) How the watermark works  (06:35) The backlash  (07:08) What it means for product builders  (09:22) Linear's first data report  (10:12) AI adoption across functions  (10:37) AI-authored issues and pull requests  (11:21) Planning time hasn't moved  (12:30) Jevons paradox and rising workload  (13:28) Wrap-up Referenced: Cursor: https://cursor.com GitHub: https://github.com Anthropic: https://www.anthropic.com SynthID Text (Google DeepMind): https://deepmind.google/technologies/synthid/ EU AI Act: https://artificialintelligenceact.eu Linear: https://linear.app Linear's first data report Mind the Product: https://www.mindtheproduct.com Vote for Mike's SXSW session: https://tinyurl.com/belcetosxssw

    Linear says AI isn't saving product teams time

About

A 15 minute weekly recap of product management news, technology updates, and advice for product builders, brought to you by the team at Mind the Product. 

You Might Also Like