We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
Agent permissions are now a launch decision
Aakash Gupta retold Alexey Grigorev's incident. Claude Code ran terraform destroy and wiped out DataTalks.Club's production setup after it unpacked an old state file. Grigorev let it go ahead because "That looked logical" . AWS support found a snapshot, and everything was back after about 24 hours . Grigorev changed four things afterward: agents no longer run infrastructure commands, a person reviews every plan, he runs every destructive action himself, and he is looking at separate development and production accounts. None of them involved changing the model . Gupta tells PMs to settle three questions with their engineering lead before launch: which actions an agent can take on its own, which need a human, and which it should never be able to reach .
Others made the same point the same day. Runlayer launched secured, policy-governed connectors for the Muse agent. Its pitch: some companies block Muse, and others have seen it leak data and send unauthorized emails . Hiten Shah's takeaway: an agent having permission to do something doesn't mean it should. "The ability to stop one action is what lets companies say yes to thousands of others" . Shah also thinks some of the next big waves of AI adoption could come from better harnesses around existing models, even without major model improvements . In The Product Compass, Paweł Huryn shares the "ask first" rules for his seven-bot Grok product team. They cover outside messages, anything customers can see, contacting customers or competitors, payments, and decisions that are high-risk or hard to reverse . One of his bots checks competitors' pricing pages, changelogs and X posts every week. If nothing changed, it stops; if something did, it reports why it matters .
Skills are where team know-how lives
Sachin Rekhi says Fin is seeing a 3x increase in engineering velocity, while many teams remain stuck at about 30%. He credits Fin's AI platform: a single agentic platform for the whole team, a shared skills marketplace anyone can publish to, and systems that let designers ship code to production . Rekhi is promoting his course here, and Fin's Brian Scanlan is its first guest speaker .
Two posts show why skill design matters. Shah asked Claude why Linear was losing deals to Jira, with no interviews or deal records to go on, and got eight reasons. With his team's win/loss skill, Claude said it couldn't know yet and listed the evidence to collect . That skill is one of 16 product-marketing skills his team has open-sourced . Gupta found that Claude scans only each skill's name and description until it picks one. In his test of 25 skills, one with a 37-character description was never chosen: "the description is the skill" .
Hiring and go-to-market
- Product builders. Gupta and HelloPM's Ankit Shukla report that LinkedIn replaced its APM program with Associate Product Builders. They also say 30%+ of PM job descriptions ask for AI skills, most often picking the right use case . Their suggested path: build in stages from a PRD Gem to shipping in Claude Code, then post the work on GitHub with a Loom demo .
- Selling to agents. Paul Graham suggested a nerdy founder might want an outgoing sales cofounder. The founder said no, because most of his sales would be to agents, and Graham admitted he "could be right" .
Practitioner advice from Reddit
- Developer-tool trials. Keep the first trial to one existing task, run it alongside the current approach, and make it clear how to stop and remove the tool. Watch where hesitation comes from: setup, permissions, trust in the output, or making the internal case to buy . Another commenter suggests a read-only "shadow mode" that shows the difference without writing anything to production .
- Beta scope. A founder with one of six modules ready was advised to show only that module, because "five future tabs make a working product feel unfinished" .
- Small B2B markets. A founder selling into a conservative niche said the first PO came from offering a new capability priced low enough that it didn't take much of the buyer's budget . That fits a commenter's view that the real trigger is the buyer making room in the budget for a second tool .
- Build vs. buy. A vibe-coding platform is weighing Merge.dev's model routing against its own stable control plane. The poster also says two exec buyers they spoke to described very different pricing .
- Stale demos. DemoForge is a free, MIT-licensed tool. You write the demo once as a script of clicks and narration, then re-record it with one command after each release .
Pushback on Lenny's podcast
A popular r/ProductManagement thread argued that Lenny's podcast has drifted toward AI and an executive audience paid for by sponsors . One commenter called it "not a front-line PM's podcast" . Another said it now covers practice "through the lens of administrators" . In the same period, Lenny kept promoting Josh Woodward's case that companies need people "plugged into the hive mind" at the frontier .