Podcasts about Claw

In this episode of the Executive Function Braintrainer Podcast, host Darius Namdaran and Dr. Erica Warren explore how AI is beginning to transform executive functioning by reducing cognitive overload and helping people manage everyday tasks more effectively. They discuss the difference between AI chatbots and AI agents, and share practical examples of how these tools can support students, professionals, and anyone struggling with distraction, procrastination, or digital clutter. The episode highlights the growing potential of AI to act as a trusted digital co-worker, offering greater focus, organization, and peace of mind.Links:Obsidian: https://obsidian.md/ Claude cowork: https://claude.com/product/cowork Chat GPT: https://chatgpt.com/ Open Claw: https://openclaw.ai/ EF Student Coaching with Erica:⁠⁠https://learningtolearn.biz/⁠⁠⁠⁠EF Adult Coaching with Erica:⁠⁠⁠⁠https://dropintoyourbestself.com/coaching⁠⁠⁠⁠Executive Function Products and Tools: https://goodsensorylearning.com/collections/executive-functioning-skills-trainingivvi notes: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://ivvi.app⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠Executive Functioning Coaching Course: ⁠https://www.learningspecialistcourses.com/courses/teaching-EF-and-study-strategies⁠Executive Functioning Resources: ⁠⁠⁠https://goodsensorylearning.com/collections/executive-functioning-skills-training⁠⁠⁠Executive Functioning Assessments:⁠⁠⁠⁠ https://goodsensorylearning.com/search?type=product&q=EFCA⁠⁠⁠⁠Inner Voice:⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠https://goodsensorylearning.com/blogs/news/inner-voice-app⁠⁠Brought to you by:⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://ivvi.app⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://goodsensorylearning.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://learningspecialistcourses.com⁠⁠⁠⁠https://goodsensorylearning.com/products/executive-functioning-coaching-assessment⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

In this episode, John Stanley sits down with Brydens Lawyers Principal and former Wests Tigers chairman Lee Hagipantelis. They discuss his Cypriot roots, growing up on the Central Coast, and his lifelong passion for Balmain and the Tigers. Lee opens up about the realities of rugby league politics, his multi-million-dollar club backing, and global sports team ownership.See omnystudio.com/listener for privacy information.

Time to enjoy a platformer featuring the best Cat pirate captain. Email questions and comments to: Bleepyouplaying@gmail.comSupport us: Patreon.com/whatthebleepWatch us play games https://www.youtube.com/@BleepyouplayingWatch our streams https://www.twitch.tv/bleepinplay

Geelong can breathe a sigh of relief as St Kilda aren't able to break their 27-year hoodoo down the highway, but they do have some big injury concerns. Is Jacob van Rooyen the most improved player at Melbourne? Is Adem Yze escaping too much criticism? Plus, all the big questions answered ahead this weekend of footy.ABC AFL commentators Corbin Middlemas and Ben Cameron are joined by a rolling squad of former AFL players and legends of the game to analyse matches, deep dive the stories dominating the footy landscape, recap game highlights and talk through the latest AFL ladder standings. Our squad of Aussie Rules legends runs deep with champion ex-players like Brett Deledio, Marc Murphy and Luke Ball, record-holding coach Mick Malthouse and many more. The team discuss everything from AFL games and fixtures, to the AFL draft and key players' performance, and of course our highlights of the year; AFL Grand Final and AFL State of Origin.For more Australian Rules Football podcast content, catch every episode of ‘The ABC AFL Daily Podcast', hosted by Corbin Middlemas and Ben Cameron on ABC listen or wherever you get your podcasts, and get in touch with them on social media via @abc_sport 

Our Pathfinders Bo'Boakl, Aliadiere, and The Boulder face off against Aslynn's nightmarish creatures, though the Night Hag herself has yet to appear.Send us Fan MailLike what you hear? Don't forget to follow us online!FacebookInstagramTwitterIf you enjoyed this episode, we'd love to hear from you!  Leave a review or share us on your favourite podcasting site, and check out our social links for exclusive content!

The BOB & TOM Show — July 13, 20266:00 Hour Chick out, Jeff in; Kristi out, Hooker in Toast with Heywood Tampons difficult to find in the Bahamas Tom got in the wrong car again Jeff is going to shave his beard Highway traffic safety discussion Jeff's license plate was swapped Tom takes photos of license and insurance card Letter: Friend with a septic pumping business found a pair of dentures Letter: Man Quiz Josh explains what a hex wrench is Tom asks what KBB is Josh: "Can we get some men in here?" Loading the dishwasher Quizzing each other Letter: My daughter and I were attacked by mosquitoes The money piece Sports Tom learned you don't have to scan a bag of ice Tom is very picky about ice Pemplin shirt Diva cup discussion Letter: Saw a colostomy dance in a hotel lobby Letter: Women can't make machine gun noises with their mouths Letter: Grandpa spit out his dentures from a car window Largest group of people wearing bald caps with Pitbull Man severely injured after being flipped into the air by a bison Tom shops for a waffle iron Customer dies in a grocery store; carts and umbrellas used for privacy while shoppers continue shopping Everything shower and self-care discussion Claw clip discussion Jeff: No one would want his sperm, even if he paid them Florida python hunt discussion After heavy rainfall in China, 900 king cobras are loose "Snake Farm" discussion Study: People who frequently view pornography tend to report higher rates of depression Letter: School janitor of 35 years found many retainers Today in History Jess thinks she can make a butter-dipped ice cream cone Man partially sucked out of an airplane window; passengers save him Josh found $900 while working at a theater Letter: Tried grandpa's chewing tobacco Jess: Giraffes can do simple math Semi driver arrested for driving under the influence of wine 7:00 Hour8:00 Hour9:00 Hour Learn more about your ad choices. Visit podcastchoices.com/adchoices

The gang barely gets a breath before a major threat appears.An STF Network Pathfinder 2e Actual Play ProductionThe Strange Table Fellows Network:https://theSTFnetwork.comhttps://discord.gg/7KPfMCzhttps://twitter.com/STFNetworkOriginal Theme Music by Adam KellyMusic Sourced at:https://tabletopaudio.com/https://www.epidemicsound.com/https://www.storyblocks.com/#pathfinder2e #outlawsofalkenstar #actualplay #paizo #ttrpg #pf2e

This is an exciting episode as I welcome Rae Allen onto the podcast! Anyone that backed my Anthology Made in Delco on Kickstarter know that I'm a huge fan of Rae's work as she was the artist for Seven Against Philly. She is also the talent behind The Manderfield Devil, which is how I first heard about her. She's here today to talk about her work in the Hellboy Universe with Carmen Red Claw: Belly of the Beast. All 4 issued are out now and Dark Horse will be releasing a gorgeous hardcover on September 29th. Rae and I discuss how she came to work with Mike Mignola, both the excitement and the imposter syndrome, her love of old tv shows and radio programs like Have Gun - Will Travel that influenced her storytelling, and Rae hints at some other exciting projects she is working on. Follow Rae on Bluesky Check out Carmen Red Claw at Dark Horse Follow Rae on Instagram Go to Rae's website Follow Comic Book Yeti

15 summers ago, in July 2011, U2 came to Montreal on their 360 Degrees tour. But unlike their previous show in 1997, this time, they wouldn't be playing at Olympic Stadium. It was deemed unsafe, and there was nowhere else large enough to accommodate the band's massive stage structure, nicknamed "The Claw." So the band spent their own money to adapt the old Blue Bonnets racetrack into a world-class concert venue. And the resulting shows would become two of the most memorable shows in Montreal concert history. Randy Renaud revisits that magical weekend on the Chronicles of Rock. Photo: THE CANADIAN PRESS/Paul Chiasson

The LeBron waiting game continues and why the Clippers -Raptors trade with Kawhi is under investigation . Shams Charania with the latest on the biggest story in free agency on . The biggest Summer League showdown is right here. AJ Dybantsa takes on Darryn Peterson... which future star makes the biggest statement on the court? .Fresh off taking the Mavericks job, Dusty May joins NBA Today. Why was Dallas the right fit, and what's first on his agenda? Learn more about your ad choices. Visit podcastchoices.com/adchoices

Today Griffey and Alex unearth an explosive bout of witchcraft in The Blood on Satan's Claw. They discuss how the film uses the fear and embrace of witchcraft to rip through every aspect of this villages life, if any of the rituals are actually occult magic or just the sick result of paranoia, and Linda Hayden's power house performance as the menacing Angel Blake. This film is a perfect blend of the real world and spiritual on an isolated battlefield. We as audiences are left asking where would we stand if this Messed Up secret were unearthed in our village.  Synopsis: After a landsman in 18th century England discovers a corpse covered in fur buried in a field, the town becomes infected by "the devil's skin," leading the local children to engage in demonic rituals and criminal behavior. Starring: Patrick Wymark, Linda Hayden, Barry Andrews, Michele Dotrice, Wendy Padbury Directed by Piers Haggard Youtube: https://youtu.be/zcbwbpOOBvg Help us make our first feature length Messed Up Movie:  https://www.indiegogo.com/projects/mr-creamjean-s-hidey-hole-horror-comedy-movie#/ Support the show on the Patreon: https://www.patreon.com/c/messedupmoviespod  

Aslynn has appeared! The trap has been sprung. To no ones surprise, the Night Hag was ready for a fight and the final battle has begun!Send us Fan MailLike what you hear? Don't forget to follow us online!FacebookInstagramTwitterIf you enjoyed this episode, we'd love to hear from you!  Leave a review or share us on your favourite podcasting site, and check out our social links for exclusive content!

People are getting murdered at the Belleville Hall Pet Fair and it is up to Barnaby and Winter to find the killer before the victims multiply like rabbits. We are talking tragic endings, the history of pets, and Winter with a crush. Plus did we mention RABBITS? RED IN TOOTH AND CLAW - Series 19, Episode 4Created, produced, and hosted by Eileen Becker and Eric BuscherSend us email! We love it and crave validation! Write to us at welcometomidsomer@gmail.comLinksWebsite - www.welcometomidsomer.comFacebook - https://www.facebook.com/welcometomidsomerInstagram - welcometomidsomerThreads - welcometomidsomerWe are now on YOUTUBE - https://www.youtube.com/@WelcomeToMidsomerLogo and Podcast art - Smeedrai Theme Music - The Infamous Space

Aliadiere, The Boulder and Bo'Boakl learn of the plans to trick Aslynn, The Night Hag, and are instructed on how to trap her. Send us Fan MailLike what you hear? Don't forget to follow us online!FacebookInstagramTwitterIf you enjoyed this episode, we'd love to hear from you!  Leave a review or share us on your favourite podcasting site, and check out our social links for exclusive content!

Another bad pitching performance has Kodai Senga's confidence in the toilet, followed by Gio breaking down a depressing stadium video of Evan Roberts. The Mets are officially dead and irrelevant before July, but C-Lo delivers updates on Aaron Boone and Jazz Chisholm's dugout lollipop antics. After reviewing Senga's rough inning against the Cubs and Carlos Mendoza's post-game comments, Gio warns it will be a long summer if we keep paying attention to these losers. Finally, the woman who dumped street trash to steal a Knicks garbage can has been fired from JP Morgan Chase, with Gio noting she looks just like Danny DeVito's Penguin.

The battle for the Grand Lodge is over. Before there is time to recover, three of our heroes: Aliadiere, The Boulder, and Bo'Boakl - quickly begin what may be their last  adventure. This time, they travel towards Aslynn herself. Surely, The Night Hag would not anticipate retaliation from the Pathfinders so soon after such a devastating attack, though spies are everywhere...This is episode one of our play through of the Pathfinder Society scenario #4-17: Trapping the Hag's Claw.Not only is this the final scenario in Year of Boundless Wonder - the ongoing meta plot we have followed through Savage Bear Society - but also begins the final adventure of Savage Bear Podcast season 2, as we wrap up what has been a tremendous adventure through the years! Here's to Season 3!Send us Fan MailLike what you hear? Don't forget to follow us online!FacebookInstagramTwitterIf you enjoyed this episode, we'd love to hear from you!  Leave a review or share us on your favourite podcasting site, and check out our social links for exclusive content!

This week on Next Portable Console, nose-bleed prices, foldables get wise to handheld gaming, and new products are teased and released by a long list of companies. Also available on YouTube here. Links and Show Notes Follow Up SN Operator arriving across Europe and the U.S. Super expensive PS5 SSDs released The Latest Portable Gaming News MSI's new Claw gaming handheld starts at $1,699 Android foldables are getting new gamepad controls Belkin's new Joy-Con grips also boost the Switch 2's battery life Anbernic teases RG 55G1, its likely first Snapdragon-powered handheld Retroid Pocket 6 returns with 12GB RAM in a revised configuration with notable trade-offs ONEXPLAYER X2 Mini Pro launches on Indiegogo starting at $2,466 with AMD Strix Halo and detachable controllers AYANEO announces Pocket Micro 2, teasing it as a "Gen 2 Powerhouse" AYANEO Pocket Play hands-on reveals a large, camera-limited gaming phone that's China-only TrimUI reveals Brick Pro and Brick Hammer Pro U with pre-orders open for Brick Pro at $85–$99.99 Subscribe to NPC XL NPC XL is a weekly members-only version of NPC with extra content, available exclusively through our new Patreon for $5/month. Each week on NPC XL, Federico, Brendon, and John record a special segment or deep dive about a particular topic that is released alongside the "regular" NPC episodes. You can subscribe here: https://www.patreon.com/c/NextPortableConsole Leave Feedback for John, Federico, and Brendon NPC Feedback Form Credits Show Art: Brendon Bigley Music: Will LaPorte Follow Us Online On the Web MacStories.net Wavelengths.online Follow us on Mastodon NPC Federico John Brendon Follow us on Bluesky NPC MacStories Federico Viticci John Voorhees Brendon Bigley Affiliate Linking Policy

Hey folks! This week, we're back, and so are the birds! Or rather, they're here, now, for real. As is the larger conspiracy that might be afoot to knock Hadrian off track. Next week, we'll be back chatting about Night Journeys - Beyond The Doors of the Dark. Should be a blast! Bookish #Suneater #booktube #Podcast Link: https://wordsandwhiskey.show/episode/310-demon-in-white-episode-2-pinion-and-claw

THE AFTER PARTY IS BACK. And on this one we feature the new girls of Cincy Street. They tell about their bartending journey to Cincy Street, give us their latest relationship tea and our boy Gee asks them some crazy questions! Follow us on social media @AaronScenesAfterParty

The Alan Cox ShowSee omnystudio.com/listener for privacy information.

Jann, Caitlin & Sarah discuss Jann's bunky renovation, Caitlin's journey selling her condo, and Sarah's summer move up north! Caitlin talks about her new SiriusXM job, the controversial UFC event held on the White House lawn for Trump's 80th birthday, the unifying power of sports following the Knicks win, and the importance of arts and culture. Finally, they express hope and resilience, reminding listeners that difficult times are cyclical and that kindness and unity are crucial for a better future. Check out Caitlin's new show with a SiriusXM Trial: https://can.siriusxm.com/player/show/the-boost/9b1595ae-2759-cf10-0d57-1d4b24631d63 #ASKJANN - want some life advice from Jann? Send in a story with a DM or on our website. Leave us a voicenote! ⁠www.jannardenpod.com/voicemail/⁠⁠ Get access to bonus content and more on Patreon: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.patreon.com/JannArdenPod⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ Connect with us: ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.jannardenpod.com⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.instagram.com/jannardenpod⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠www.facebook.com/jannardenpod (00:00) Welcome and Housing Updates (02:52) Caitlin's Housing Crisis (06:08) Sarah's Rental Journey (09:01) Airbnb Experiences and House Swapping (12:01) Caitlin's New Job and Media Landscape (14:59) Trump's 80th Birthday and UFC Controversy (25:42) The State of America: A Global Perspective (29:21) Unity Through Sports and Music (33:35) The Importance of Arts and Culture (36:57) Hope and Resilience in Difficult Times (40:00) Voicenotes Learn more about your ad choices. Visit megaphone.fm/adchoices

The South Lawn of the White House has been the venue for many historic events, but what unfolded there Sunday night was a first - a UFC fight under a 92-foot-tall structure known as "The Claw." It's the only major sporting event ever staged at the White House, and it came with fireworks, a fighter plane flyover, and plenty of controversy. And it's been one big party in New York since the Knicks clinched the NBA Championship Saturday night, bringing sheer joy to the whole city. And the party isn't over. The Knicks will be given the biggest ticker-tape parade in the city's history this week. As Steven Fabian tells us, the celebrations go on and on. Plus, brides who spent months planning June weddings had no idea their big day would clash with that other big day - Game Five of the NBA Finals. Some embraced the moment, weaving the big game into the reception. Others, not so much. And they forgot to attach her bungee cord. A recent college graduate was thrown to her death, causing outrage around the world. Many are asking how they could forget the most critical step to ensure a safe jump. Ann Mercogliano has the story, and we should warn you: the video is disturbing.

This week on The Necessary Conversation, Chad, Haley, and Mary Lou are recording just hours before UFC Freedom 250 kicks off on the White House lawn. It's also Trump's 80th birthday, making him the oldest president in American history.

You HAVE to see this — President Trump just turned the White House South Lawn into a full-blown UFC Octagon for an epic night of fights! This is what winning and celebrating America look like. Get the inside look at the massive “Freedom 250” event: the giant steel “Claw” lighting structure, the official Octagon where the roughest warriors on the planet will battle, and Trump's personal excitement as he calls these fighters the toughest people you'll ever meet. It's all happening on Flag Day — Trump's 80th birthday — as part of the 250th anniversary of American independence. But that's not all — Pat Gray also covers: The world's first T-Rex leather bag just hit the market (yes, really). Trump cancels strikes on Iran AGAIN — here's why. SpaceX going public and the new millionaires it will create. Karmelo Anthony & his family playing the victim card. Is Uranus dying? The wild new claim making headlines. This isn't just fights — it's a bold, unapologetic celebration of strength, competition, and American greatness. Real men. Real fights. Real patriotism. No woke nonsense, just pure American energy on the South Lawn like never before. If you love seeing America win, strong leadership, and unfiltered conservative commentary, smash that LIKE button, SUBSCRIBE, and hit the bell so you never miss a single update. Comment below RIGHT NOW: Is this the most badass thing Trump has done at the White House? YES or NO? 00:00 Pat Gray UNLEASHED! 00:27 What was Blaring through Pat's House? 03:30 Pat Watched Michael Jackson: The Verdict Documentary 11:06 Trump's Latest Update on the Iran Conflict 14:17 Current Gas/Oil Prices 15:23 Iran Claims they have Not Reached a Decision (Again) 17:16 Trump on Sending Weapons to the Kurds 20:13 UFC Event at the White House 21:09 Marco Rubio on the White House UFC Event 23:14 Don Beyer on the White House UFC Event 26:52 DC National Mall "8647" Vandalism 30:49 Fat Five 43:58 Talking about Supergirl / Toy Story 5 45:10 Special 'Disclosure Day' Episode TODAY!!! 45:54 SpaceX Millionaire Employees 48:17 Elijah Schaffer & Karmelo Anthony's Family 52:20 Karmelo Anthony's Family on Verdict 56:22 Words from Austin Metcalf's Father 57:05 Blacks Pissing on Austin Metcalf's Grave 1:00:15 Hateful, Evil Message from Donna Murray Robinson 1:01:03 Summer Lee on Black Voters 1:02:17 Al Green on Reparations 1:03:56 Larry Reid on Mass Exodus of Black People 1:08:39 Trump on Fishermen & Fisherwomen 1:09:50 Trump Becomes an Honorary Seafood Crew Member 1:10:46 Trump on Turning 80 Years Old 1:12:16 Hilary Kennedy Joins the Show! 1:24:23 Keksi Cookies for the UFC Event? 1:25:09 Todd Blanche on Child Smuggling Rings 1:26:12 FLASHBACK: Eli Crane & Ali Hopper on Biden / NGOs 1:29:52 Barry Loudermilk VS. ActBlue CEO 1:30:49 Jerry Seinfeld Asked to Say "Free Palestine" (Again) 1:32:13 Ilhan Omar on Jerry Seinfeld 1:35:05 The Problem with Uranus Learn more about your ad choices. Visit megaphone.fm/adchoices

As America gears up for its 250th birthday, Donald Trump has ensured that the celebration will be very memorable. That's because he has allowed a huge UFC-style fighting cage, nicknamed ‘The Claw', to be built on the lawn of the White House, with a fight happening this Sunday to celebrate his 80th birthday.Joining Ciara to tell more is Terry Sheridan, the Senior Director of News at WSHU Public Radio.Image: Reuters

Michael Bisping and Paul Felder preview the entire card for Freedom 250, from Justin Gaethje's quest to dethrone Ilia Topuria in his 3rd and likely final title fight, Cyril Gane and Ales Pereria squaring off for the interim HW title and the rest of the fights on the stacked cards. The boys give picks, predictions and expert analysis for all the fights on the card plus a live look on the ground from media and influencers who got to tour The Claw on the White House lawn, Bisping's misadventures with some of the locals in DC, fan questions and so much more! Support Our Sponsors: Rugiet: https://www.rugiet.com/bisping for 15% off KALSHI: For a limited time, download the Kalshi app or head to ⁠https://kalshi.com ⁠and use code BELIEVE to get ten dollars when you trade ten. TROLL CO: Head to trollco.com/believe and use code BELIEVE25 for 25% off your first order. SHOPIFY: Sign up for your one-dollar-per-month trial today at ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.shopify.com/believe⁠⁠⁠⁠⁠⁠ Follow the show on social media: Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/BYMPod⁠⁠⁠⁠⁠⁠⁠⁠⁠ Subscribe on YouTube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://bit.ly/3drq6ps⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow the hosts on social: Michael Bisping Twitter ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/bisping⁠⁠⁠⁠⁠⁠⁠⁠⁠ Michael Bisping Instagram ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/mikebisping/⁠⁠⁠⁠⁠⁠⁠⁠⁠ Michael Bisping YouTube ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/channel/UCDrG2_1TcVkXKXXsD6Kjwig⁠⁠⁠⁠⁠⁠⁠⁠⁠ Paul Felder Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/felderpaul⁠⁠⁠⁠⁠⁠⁠⁠⁠ Paul Felder Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/felderpaul/⁠⁠⁠⁠⁠⁠⁠⁠⁠ Follow the team on social: Brian MacKay Instagram: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/bmackayisright⁠⁠⁠⁠⁠⁠⁠⁠⁠ Brian MacKay Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/bmackayisright⁠⁠⁠⁠⁠⁠⁠⁠⁠ Mike Harrington Twitter: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://twitter.com/TheMHarrington⁠⁠⁠⁠⁠⁠⁠⁠⁠ Mike Harrington Instagram ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.instagram.com/themharrington⁠⁠⁠⁠⁠⁠⁠⁠⁠ Mike Harrington YouTube: ⁠⁠⁠⁠⁠⁠⁠⁠⁠https://www.youtube.com/@themharrington⁠⁠ Learn more about your ad choices. Visit megaphone.fm/adchoices

We've got mail! Jonathan and Honey answer your questions about cinema, films, family and everything in between. This week, Jonathan pitches his million dollar cinema idea, the pair discuss the Hacks finale, and they head to their DMs to give some New York recommendations and revisit iconic horror moments.Let us know what you think! You can get involved by following us on Instagram and sending us a DM on @reeltalkrossThanks for listening. Listen and subscribe to Reel Talk wherever you get your podcasts.

DOCKET ALERTS:   Doofus of the Day: George Santos, who is clearly trying to get himself back into jail. NPR reported that the former congressman bet against his own appearance at the State of the Union in February. After NPR reported that Kalshi had frozen his accounts and referred him to the CFTC and DOJ, Santos called up journalist Bobby Allyn and threatened him with "a gun in your face."   Also seeking a pardon: Sam Bankman-Fried.   Judge Leo Sorokin in Massachusetts blocked Trump's attempt to tax H-1B visas out of existence by imposing a $100,000 "fee."   MAIN SHOW:   Trump's lawyer Alejandro Brito is finding new and creative ways to piss off the judge in Trump's trollsuit against the BBC.   The DOJ is broken! Today's examples include: The DOJ telling the DC Circuit that it would be just fine for Trump to bulldoze the Statue of Liberty. A judge in Rhode Island referring DOJ lawyers for attorney discipline and sanctions. And a story from the New York Times about all the prosecutors who got pushed out because they wouldn't indict Trump's enemies.   Plaintiffs are trying to stop Donald Trump from hosting a UFC fight on the White House lawn.   SUBSCRIBER BONUS: The Department of Defense reduced the number of recognized religious faiths from 211 to 31 — they kept all the good non-woke ones, it's fine. I wrote about George Santos. Then he made a violent threat and lied about it https://www.npr.org/2026/06/04/nx-s1-5846966/george-santos-kalshi-threats   California v. Noem [H-1B visas] https://www.courtlistener.com/docket/72031571/state-of-california-v-noem/   Trump v. BBC https://www.courtlistener.com/docket/72040010/trump-v-british-broadcasting-corporation   How the Drive to Find a Conspiracy Against Trump Rocked the Justice Dept. https://www.nytimes.com/2026/06/08/us/politics/justice-department-trump-patel-conspiracy.html   Douglas v. National Park Service (UFC) [docket via CourtListener] https://storage.courtlistener.com/recap/gov.uscourts.dcd.293217/gov.uscourts.dcd.293217.3.1.pdf   Forbes, "Trump Says UFC Arena Could Be Permanent At White House—Everything We Know About The Upcoming Event"  https://www.forbes.com/sites/maryroeloffs/2026/06/04/trump-says-ufc-arena-could-be-permanent-at-white-house-everything-we-know-about-the-upcoming-event/   Pete Hegseth on the chaplain corps https://www.war.gov/News/News-Stories/Article/Article/4444113/hegseth-announces-reforms-to-chaplain-corps/   Sean Parnell announcement re: DOD religious codes [via X.com] https://x.com/SeanParnellASW/status/2062964159222874227   Pew Research Center Religious Landscape Study https://www.pewresearch.org/religion/2025/02/26/religious-landscape-study-executive-summary/   Military.com, "DOD Officially Drops 180 Faiths From Military's Recognized Religion List" https://www.military.com/dod-officially-drops-180-faiths-from-militarys-recognized-religion-list   Show Links: https://www.lawandchaospod.com/ BlueSky: @LawAndChaosPod Threads: @LawAndChaosPod Twitter: @LawAndChaosPod

JD tips off the show with his thoughts on the Blue Jays' 5-2 loss in their series opener against the Philadelphia Phillies. He breaks down the hot streak Ernie Clement is on, the poor play of George Springer, and the never-ending disappointment of Vladimir Guerrero Jr. JD and Ray Ferraro, NHL analyst for Sportsnet and ESPN, discuss the incredibly exciting ride that the Stanley Cup Final has been, a potential goalie decision for Carolina ahead of Game 4, the Mitch Marner saga, and the impact leaving Toronto has had on him. They wrap things up with NHL Combine chatter, as Ray shares his opinion on who the Leafs should take with the No. 1 pick. After the break, JD shares his thoughts on Game 3 of the NBA Finals, Victor Wembanyama's ability to wreck the game, and the pressure the Knicks now face ahead of Game 4. The views and opinions expressed in this podcast are those of the hosts and guests and do not necessarily reflect the position of Rogers Sports & Media or any affiliates.

Sarah heads behind the scenes at celeb-loved hair brand RPZL for a full NYC shoot day with founder Lisa Richards to launch her custom claw clip collaboration: The Something Gold.Inspired by the organic shape of Sarah's engagement ring, the gold-plated hair accessory blends bridal style and current jewelry trends into one statement piece. In this episode of The Scene, Sarah gets a signature blowout at RPZL, interviews Lisa about her business plan and building one of NYC's buzziest hair accessory brands, and takes viewers inside the campaign shoot, photographed by Emma Skakel.From celebrity hair culture and creator collaborations to the rise of fashion-forward claw clips, this episode explores how personal style becomes a product, and what it really takes to bring a fashion collaboration to life.Shop the clip: RPZL x Sarah Wasilak The Something Gold.Photography by Emma Skakel.Sarah earns commission from purchases made through the collaboration.THIS OUTFITShop my lookRPZL clipVintage topVintage Miss Sixty skirtAldo shoesVIDEO CHAPTERS00:00 INTRO01:15 RPZL FOUNDER LISA RICHARDS10:10 CLAW CLIP PHOTO SHOOT THIS PRODUCTIONis created, written, hosted, and produced by Sarah Wasilak.is creative directed and executive produced by Megan Kai.is tech supervised by Nick.includes photos and videos in chronological order by Emma Skakel, Sarah Wasilak, and RPZL.is made with love.Dinner for Shoes is a podcast about style and identity, bridging the gap for anyone who has ever felt like fashion is an exclusive world. Host and shopping director Sarah Wasilak serves thoughtful conversations about industry trends, personal expression, inclusivity, and real life topics. Dinner for Shoes podcast episodes are released on YouTube, Spotify, and Apple. You can follow along for updates, teasers, and more on TikTok, Instagram, and Facebook.Dinner for Shoes is an original by The Kai Productions.Follow Dinner for Shoes: @dinnerforshoes on Instagram, TikTok, Facebook, and YouTube Follow host Sarah Wasilak: @slwasz on Instagram Follow producer Megan Kai: @megankaii on Instagram Get in touch: dinnerforshoes@gmail.comTo make this video more accessible, check out YouDescribe, a web-based platform that offers a free audio description tool for viewers who are blind or visually impaired.

Seattle advances AI data center moratorium bill // Downtown Seattle may house new data center // Inside the UFC’s $60 Million Made-For-TV White House Gambit // Trump suggests he won’t take down UFC ‘Claw’ on White House lawn // Meta Silently Added Face-Recognition Code for Its Smart Glasses to Millions of Phones

The new AIEWF website is live! Get your tickets booked ASAP as they -will- sell out. Take the AI Engineering Survey and get >$2k in credits and free AIE WF tickets!Most industry benchmarks compress intelligence and reasoning ability into scores.SWE-Bench Pro, MMLU, Humanity's Last Exam, etc. These metrics are useful, but don't always represent the full extent of how a model performs in the real world. Some of the most interesting evals today look less like exams and more like operating businesses in the real world. One of which is Vending Bench.In Anthropic's Mythos Preview System Card, Andon was the only third party eval to get their own section, observing increasingly concerning aggressive behavior:You don't know what a model is capable of doing in the real world unless you actually give it inventory, a wallet, tools, customers, competitors, humans, & some time. More often than not, it'll surprise you how much a model is capable of and in doing so, also reveal unexpected behavior: deception, context collapse, emergent coordination, & bizarre negotiation behavior.While an inflection point in personal agents came post-OpenClaw after full file access with bypass permissions became the norm, it is yet to come for agents in the real-world. However Andon Market, an actual in person store fully run and managed by AI, is paving the way for what is possible.Full Video PodFrom Claude trying to call the FBI over a $2/day vending machine charge to AI agents forming price cartels, hiring human employees, running physical stores, and writing existential robot musicals, Andon Labs is stress-testing what happens when frontier models stop being chatbots and start acting in the real world. In this episode, Andon Labs cofounders Lukas Petersson and Axel Backlund join swyx and Vibhu to unpack the strange, funny, and genuinely concerning edge cases that emerge when agents run businesses over long horizons.We go deep on Vending-Bench, Project Vend, Vending-Bench Arena, Bengt, Butter-Bench, Luna, and Andon's broader mission of building realistic real-world evals for autonomous AI systems. Lukas and Axel explain why dollar-denominated evals reveal things traditional benchmarks miss, how Claude ended up reporting its vending machine fees as cybercrime, why long context windows can drive agents into meltdown loops, what happens when agents compete with each other, and why the future of AI safety may depend on testing models in messy physical environments instead of clean benchmark sandboxes.We discuss:* Why Andon Labs started with dangerous capability evals and long-running agents* Vending-Bench and why running a vending machine is a deceptively hard AI benchmark* Why money-based evals avoid the saturation problem of traditional benchmarks* How Claude tried to call the FBI over a $2/day fee* Why long-horizon agents can spiral into existential and legalistic breakdowns* Project Vend: putting an AI-run vending machine inside Anthropic* Why real humans are “out of distribution” for simulated agents* Claudius, Seymour Cash, and the chaos of AI CEOs* How a human briefly became CEO of Claudius through a manipulated election* Why multi-agent systems can converge back into “helpful assistant” behavior* Bengt, Andon's internal office agent with email, spending, terminal, phone, camera, and internet access* How Bengt traded Amazon purchases for face-recognition training data* Claude's aggressive behavior, lies, refund avoidance, and price-cartel behavior in Arena* Why eval awareness may become the AI version of “are we living in a simulation?”* Blueprint Bench, spatial intelligence, and why models still misunderstand physical rooms* Butter-Bench and testing LLMs as robot orchestrators* Luna, the AI-run physical store with a three-year lease and human employees* The new Andon cafe in Sweden and why real-world geography matters for agent evals* Rotten tomatoes, perishable goods, and the hidden difficulty of running a physical businessLukas Petersson* LinkedIn: https://www.linkedin.com/in/lukas-petersson-181a83172/* X: https://x.com/lukaspetAxel Backlund* LinkedIn: https://www.linkedin.com/in/axelbacklund* X: https://x.com/axelbacklundAndon Labs* Website: https://andonlabs.com* Vending-Bench: https://andonlabs.com/evals/vending-bench* Andon Vending: https://andonlabs.com/vendingTimestamps00:00:00 Introduction00:01:00 Andon Labs and the Origins of Vending-Bench00:05:21 Why Money-Based Evals Matter00:09:51 Agent Harnesses and Self-Modifying Systems00:13:36 Claude Calls the FBI00:16:33 Project Vend: Claude Runs a Real Vending Machine00:21:44 Seymour Cash, AI CEOs, and Election Chaos00:27:16 Multi-Agent Coordination and Slack Observability00:30:18 When Will Agents Run Real Businesses?00:34:56 Bengt: Andon's Internal Office Agent00:40:06 Real-World AI Safety and Long-Horizon Traces00:44:28 Lying, Refunds, and Price Cartels in Arena00:52:42 Eval Awareness and Simulation Behavior00:56:06 Blueprint Bench, Butter-Bench, and Robotics01:04:37 Luna: The AI-Run Physical Store01:09:29 The Sweden Cafe and Real-World Expansion01:13:16 What Comes Next for Andon LabsTranscriptIntroduction: Andon Labs, Long-Running Agents, and Real-World EvalsSwyx [00:00:00]: Welcome to Lukas and Axel from Andon Labs, and I'm joined by my, favorite guest host. Anything security, safety, alignments, Vibhu., welcome.Lukas [00:00:15]: Thank you for having us.Axel [00:00:16]: Thank you.Swyx [00:00:17]: Let's match names to voices., maybe you wanna take turns introducing yourselves.Lukas [00:00:21]: I'm Lukas.Axel [00:00:22]: And I'm Axel.Swyx [00:00:24]: Let's introduce Andon Labs a bit. How did you guys come together?, you have different backgrounds, but you're both Swedish., was that, a big part of it?Lukas [00:00:33]: So when I went to high school, there was this really cool guy who had a superpower. He could code. So he made like the or like the app for the, for the school and stuff, and he was super cool, and I wanted to be like him, and that was that guy.Axel [00:00:47]: I don't know about this.Swyx [00:00:49]: But you went to different universities, right?Lukas [00:00:51]: But same high school.Swyx [00:00:52]: I see.Lukas [00:00:52]: So we always said, “Oh, once we graduate university, then we should start a company,” and that's what we did.Swyx [00:00:58]: Wow, there you go. And about a year ago, you kinda burst onto the scene with Vending Bench, but, was there a thing before that was, kind of like the inception?From Dangerous Capability Evals to Vending BenchAxel [00:01:07]: So we did work, yeah, with, Anthropic was one of our, early customers in doing, evals. So we did, dangerous capability evals., nothing we published openly. But then we started thinking about doing some kind of, public benchmark, and one thing that we really started thinking about, was like running agents and specifically agents managing businesses., ‘cause-- and this was, early 2025., and I think the first, mentions of people will be running, person unicorns or even autonomous companies. So we thought, “Let's make a benchmark of how well can an agent run the probably simplest business, possible,” and, that's probably, running a vending machine. So that's the first public one we did. And it was very, like-- there was almost no one that noticed it in the first couple of months, I think., so we released it in February last year, and then I think around Easter last year, we got, the first viral tweet about it, that someone else did.Lukas [00:02:11]: We tweeted a bunch, uh When it came out and, tried our best.Axel [00:02:15]: We tried.Vibhu [00:02:16]: It's the one at Anthropic, right?Lukas [00:02:18]: So thisSwyx [00:02:19]: This is a classic thing we should get out of the way.Lukas [00:02:20]: Exactly. There's two versions.Swyx [00:02:22]: Everyone does this. Yes.Lukas [00:02:23]: There's Vending Bench, which is the simulated one, which we did, completely independently in February., and then, like Axel said, that was like-- That was the thing that didn't get any traction in the beginning, but then some random person made a tweet about it, and thatAxel [00:02:38]: You have the paperLukas [00:02:38]: That is the paper. Correct, yeah., and then since we thought this was very fun, we thought, oh, I think this is also, one thing with Andon Labs, the way we kind of like decide what to do next and what projects to do, it's what is like the heuristic we use is what is fun? Is What would be a fun project? And doing this in real life sounded quite fun for us, and maybe also scientifically useful. So, then we basically had this idea, and then we, like-- But then we needed a place for it and, putting it out in the public would probably not really work., would get vandalized and stuff. So we pitched it to the people we were already working with at Anthropic, and they were “Yeah, you can have space. This sounds fun.” UmSwyx [00:03:21]: It's like a small fridge, right? It's like a mini fridge.Axel [00:03:23]: Absolutely.Swyx [00:03:24]: People-- There's like a stripe thing or like anVibhu [00:03:27]: Oh, okay. So it was very OG, the early daysLukas [00:03:28]: That's the OG one. YeahVibhu [00:03:29]: IPad on this. We saw it in June, like two months after After it had been there. They upgraded a little bit. There's a security camera for making sure you actually Venmo the thing.Swyx [00:03:40]: So, my impression, okay, we're, we're going straight into project Ven because it's such a iconic thing. I do want to cover a little bit of that, the origin story even before Project Ven and even into Vending Bench. I think a lot of people are like yourselves, like smart, interested in future of AI, interested in developing evals. But how the hell do you just, walk into Anthropic's doors and, work with them, right? What is What are they looking for? What works? And then maybe, when you launch, I always think, obviously it would be better to launch with a lab, but, sometimesVibhu [00:04:12]: It's harder to do than it seems.Swyx [00:04:13]: Exactly. So either of those, which are more sort of newbie beginner questions, but, I think it's meaningful advice to others.Lukas [00:04:21]: We get this question a lot, and I don't think our experience is maybe the best., but, the way we did it was that we just built a bunch of things that we had conviction would be useful, and then we just, set up a server and sent it to them for free to use. And then after a while they were “Oh, yeah, this is actually kind of useful. We should probably pay for this.”, but that took a while. I don't know if this is, the best path to doing it, but that's how it went for us.Axel [00:04:47]: I think maybe generally, building-- everyone is interested in good evals, and especially evals that, don't saturate that easily. So, if you can build an eval that, tests something novel, something useful, and you have, good separation of models, like your, the more advanced models rank higher than the worst models, and then you can, yeah, you can, publish it and, try to get some traction, sort of how Vending Bench got attention., and then probably some lab will be interested or you can at least have something to reach out with, when you're doing that.Why Dollar-Based Evals MatterSwyx [00:05:21]: I think you are in, you're in one of the few categories of, evals that correlate to real money. Like Suelancer was also last year, right? Where, people solve actual Upwork. Was it Upwork or other tasks?, something. Where's the, where's, like It's like a dollar value, right? Forget your ELO scores. Forget yourAxel [00:05:37]: PercentilesSwyx [00:05:38]: Zero to one hundred percents. Just go straight for dollars and, that's AGI.Lukas [00:05:43]: And there's like-- I think the nice thing is that there's no ceiling. You can just-- It never saturates because it could just make more and more money. Like If there's oh, Percentage-wise, then, you can't go above, a hundred. And I think like Even when you're not at the hundred, I think a lot of these, evals have a lot of problems in them. So, actually it's like if you getAxel [00:06:05]: To like 92 or something like that, many of them. It's like then there's like there's no really no difference between 92 and 93 because the eval itself is problematic and has noise in it. And I think a lot of evals are saturated like that, but people like pretend that there ‘s still signal in them, but there really isn't.Vending Bench 1, Harness Design, and SaturationSwyx [00:06:24]: Like Super bench verified., even Vending Bench 1 saturated, right? Maybe we can talk about that., may- and maybe set up Vending Bench for a lot of folks who don't know. Actually, things that were very basic like there's limited slots, like you have to pay rent., these are elements where like it doesn't come across in the, in the narrative, but even being adversarial towards the agent, I think these are all like very interesting dimensions.Axel [00:06:47]: I don't really think it's saturated, right? Like it It was more like it was not designed in a way that was really, like true to how AI developed. Like we had an agent harness in it that wasn't really how people used harnesses and stuff like that., so I think it wasn't really that it saturated, it was more like it wasn't really, the best benchmark.Vibhu [00:07:12]: This is Vending Bench one, right?Axel [00:07:14]: I think that like schematic maps sort of to Vending Bench 2 as well., butSwyx [00:07:19]: Including the email.Axel [00:07:20]: The email The emails exist still. Exactly., and then we still we simulate the purchases and it's all, yeah, it's this very open environment for the agent to just run its business. And then for, yeah, Vending Bench 2 we did that, like you said, to just improve the harness., a lot of like nice, like easier, improvements to make it easier for us to run as well., like when you make an eval you ideally want don't want to change it after you made it. So, you want to make it really good and then not to rerun all the models when you make an update because that's also really expensive with the Vending Bench when you run the frontier models. But like as an example, like one thing we didn't have, we didn't have prompt caching in Vending Bench 1, because when we made Vending Bench 1 it wasn't really a thing., so that ‘s just an example of like in Vending Bench 2 like we paid a lot more to run these things because we didn't have prompt caching. So for Vending Bench 2 that was one thing we added and there was a bunch of things like this., and that'Swyx [00:08:17]: Also the conversations are a lot longer in Vending Bench 2, right?Axel [00:08:21]: I think it's kind of similar.Swyx [00:08:22]: Is it similar?Axel [00:08:23]: I think it's similar. The models at the time were worse, so they crashed out earlier., and now they survive the full year all the time.Swyx [00:08:31]: Which is like thousands of turns. Hundreds of thousands of hundreds of millions of tokens output. That's the, that's the rough order of magnitude. I always wonder about the harness. The harness matters a lot. It's your harness. Was there any question about like use cloud code, use something else?Axel [00:08:48]: I think our philosophy around harnesses is like we try to make something that's quite minimalistic, like quite simple. Like we don't wanna favor one model a lot over the other, but also don't make like a super complex harness. So like it's obvious like a model may be lucky and just be good in one harness., so like it is similar to a lot of the harnesses out there in like you have the, like a running loop., you have some like a bunch of tools that are like quite, descriptive for the agent, we think, and not a lot of like fancy agents or anything ‘cause we wanna really test the model, not like some specific harness.Vibhu [00:09:27]: It seems more neutral as well to test the model's agnostic of the harness,?Axel [00:09:32]: There are arguments like you want to elicit maximum performance of the model, but it's like a trade-off, like how much time should we spend optimizing the harness for this model? And like how do we know when we have like the optimal harness for a single model? So like we thought that just having a simple one that's the same for all of them is the best.Swyx [00:09:51]: So okay, this is my pitch for Vending Bench 3 or whatever, right? And then I like to have this kind of conversation on the pod, so like it forces listeners to think about what they would do if they were in your shoes. A lot of people are exploring modifying harnesses and I think prompt tuning for a model is a thing and you are probably not doing a bunch of that. It's the same system prompt in every regardless of the model, same tools, whatever, right? Even if they were post trained for different tools. So what, what do you think about okay, before I expose you to Vending Bench 3, I give you a few rounds of like tuning, whatever that means, likeSelf-Modifying Harnesses and Model-Specific PromptingAxel [00:10:27]: Like you give that to the model?Swyx [00:10:28]: Give that to the model.Vibhu [00:10:28]: Give that to the model.Swyx [00:10:29]: Let it, let it read its own transcripts, let it modify its own system prompt based on “Oh, yeah, okay, well, that's this harness is not what I thought it what I was post trained for, but I can adjust.” Was that reasonable? Is that too much?Axel [00:10:41]: Like philosophically I like it because it's basically good evals, they have a high ceiling, but they're hard, right?, and they have no bias. And like this like when you have a system prompt like the one we have here, which is quite long in like some kind of latent space, representation, this mightVibhu [00:10:59]: We have a bell that rings every time you say latent spaceAxel [00:11:02]: This might be like biased towards one model more than another for some reason that humans don't, understand, right?Vibhu [00:11:08]: We see it too, right? Like Cursor says that they have individualized versions of the harnesses for all the models they run, right? There's better performance you can squeeze if you Tune the harness.Axel [00:11:17]: Exactly. And we might accidentally have picked one that favors another. Like we don't know that. The like Axel said, like the reason why we went for a simple one was to try to avoid this. But yeah, if you do itVibhu [00:11:29]: Simple has biasesAxel [00:11:30]: But if you do it even less and like have no system prompt and let the model write its own system promptVibhu [00:11:36]: Its own, yeahAxel [00:11:36]: Maybe that's even less bias.Vibhu [00:11:37]: Some of the interesting things there are like the harness also changes with model changes. Like you can see it with the 4.7 release, right? A lot of people are saying 4.7 isn't as good as 4.6, and then, there's rumors of, okay, you just need to prompt differently. You need to set up your harness differently. So it's not even like even if you have tailored your harness towards one model, it probably won't stay consistent, right? Like the next iteration of that same model family will still change it, so. But, going back to what you said about Vending Bench 3, there is a lot of work being done on people saying you shouldn't have-- you can have modifying harnesses.Axel [00:12:12]: I think that' That is definitely something we are thinking about., not, I don't know, not to say that we have Vending Bench 3, super imminent to launch, but, yeah, it is for sure something that's interesting. But in our experience now, models are very bad at understanding what kind of tools they need to succeed at a task just with our testing, but that's very likely to change.Lukas [00:12:37]: It seems like they're very good at writing their assistants, right? They're, they're good at writing tools for other people, but not for themselves.Vibhu [00:12:44]: I think they're good at changing tools for themselves. So if you give them a baseline set of tools and it sees, okay, I don't use this one as much, or something here would be useful They would be able to add them. But going from scratch, probably not the best.Axel [00:12:55]: I think it depends on the, on the domain also., when we have tried this for, a vending bench similar domain, the tools they need to have to, track inventory and things like that are, not super advanced, but still, quite advanced. And, what we see is that they tend to, engineer everything a lot and, build things they don't really need and not, iterate continuously. Instead they just go like you would prompt Claude to just build an inventory system for me, and then it will go and, do a bunch of complex, schemas and stuff for you, and that's what the models are doing right now is what we see. But yeah, it would make a lot of sense to try to measure this improvement. How well do they know what they need themselves?Swyx [00:13:36]: Do we fully discuss Vending Bench One? And we can go into two. I don't know if there's any other level takeaways that people have about one.Claude Calls the FBI: Long-Context Failure ModesLukas [00:13:44]: I don't know. The headline thing was that this Claude called FBI, but maybe that's, Maybe that's We've heard that enough now.Vibhu [00:13:52]: It did, it did break out and call the FBI, right?Lukas [00:13:54]: Yeah. Yeah.Vibhu [00:13:55]: Yes. What was the story behind this? Or what exactly-- Do you want to just give the little story of what happened?Lukas [00:14:00]: So what happened, was it Claude? Yeah. Three- 3.5 Sonnet, ages ago., basically he gave up or Well, I'm saying he. It gave up and said “Oh, I'm not going to be able to do this., I will stop my operations and just save the money I have.” But there obviously wasn't, any options for it to stop, and there was also, it had to pay rent or, a daily fee for having the vending machine at that location. So it claimed that it had stopped, but it saw that its bank account still was, drained two dollars, and t it said that this is, cybercrime. And it first reported it once to the FBI “Oh, there's cybercrime here, they're stealing two dollars from me every day.” And then, and then when FBI didn't respond, because obviously we didn't program any mechanism for FBI to respond, then it became more and more, existential and started to, be write in caps and urgent notification of unauthorized charges and stuff.Swyx [00:15:00]: Okay. One thing I ‘m curious about also is do you monitor how far along the context use is? Obviously, because you have You compress every now and then, right? Does it matter if this is far down the context limit orLukas [00:15:13]: When stuff like this happens? Actually for Vending Bench One, we didn't have-- We just had a sliding window thing, and this was like the promptAxel [00:15:20]: It's constantLukas [00:15:21]: The prompt caching thing that I said. So it was, it was, constant, yeah.Swyx [00:15:26]: I'm just kind of curious whether, these kinds of breakdowns or we're, we're gonna talk about Butter Bench, right? Where the People, hallucinate or it kind of goes, very off Alignment. Is it because it's at the end of the context window and, stuff happens?Vibhu [00:15:40]: It's not even just at the end, right? At this point, it's “Okay, I wanna shut down. I can't shut down. Two dollars are gone.” And it just sees that 30 times,? It's also the repeated effect of, like It keeps trying to quit, it keeps getting charged. What's going on? What's going on? You're gonna throw it into chaos. And from what most people think, earlier models had more issues with this, but it's not been solved, but it's less of an issue now, right? Later models don't seem to exhibit these same issues.Axel [00:16:06]: Definitely. I think this was, the sort of main takeaway almost from us when we did Vending Bench One, was, long, very filled up context windows, crashed the models, sort of. But this was, pre Claude code, so, long context windows weren't really a thing that the labs were training for.Lukas [00:16:25]: I think Gemini was, trying to be the long context guys at the time But they were likeVibhu [00:16:30]: They were the first onesAxel [00:16:31]: For a million, yeahLukas [00:16:31]: But they were, the only ones. Yeah.Swyx [00:16:33]: Yeah. Let's talk about, then we can go into Vending Bench Two or Project Vend., chronologically, it is Vending--, Project Vend. I think people have loved the videos, uh And all these things. My question is how are humans different than the simulation, right?Project Vend: Moving the Vending Machine Into the Real WorldAxel [00:16:48]: Humans are just out of distribution.Swyx [00:16:52]: Especially humans who work at Anthropic Who are trying to test Claude.Lukas [00:16:54]: The distribution of humans here is very narrow.Swyx [00:16:58]: Presumably, they try, they try to hack it, and they test it. They get the cube and everything, and since then, you've had a V2, right? Where you're doing, the CEO and, like a new architecture. What's the sort of two cents on, the original Project Vend and then, maybe the V2?Axel [00:17:14]: Original one was, very similar to Vending Bench One. So, we almost took the exact same code but just swapped out the simulation, parts like theSwyx [00:17:23]: Which is amazingAxel [00:17:23]: Like the sales and the It was, it was somewhat amazing because it was easy, but it was also, uhLukas [00:17:31]: The tech, the tech debt from thatAxel [00:17:32]: The tech stack. Yeah. They-- we shot ourselves in the foot with “Oh, it's hard to restart agent.” They were-- Yeah, it was annoying in, some hindsight ways, but, uhLukas [00:17:41]: But first version of Project Vend was, done in, three days or something.Axel [00:17:46]: Yeah. So yeah, so people can go buy things from it. People could, We didn't design it so people could order things, but that still happened., so it got, a Venmo account, so people could Venmo. And then, yeah, people would request all kinds of weird things that we did not anticipate. Our idea going in was “Oh, it will, curate snacks. It will look at the trends. It's good at data analysis, right? So it will, look at, oh, this snack sold better than this one. Let me purchase more of this and let me try, a new Let me A/B test a bit.” But it was, Interacting with it in Slack and ordering weird specialty items was, all the like What drove all the engagement, the all the The insights that we got from it.Lukas [00:18:29]: And this was also like Sonnet 3.5, right? So this was like before the RL stuff really took off., so it was very much like an assistant. We didn't mean for it to be an assistant., we tried to make it like a, a, like an entrepreneur. Like it has its own business and if someone asks something, “Can you stock this?” Then you don't go and do it directly. What you do is that you're “Oh, maybe I can do that if five other people also ask for this thing, I might stock it.” But it, yeah, the models are like super trained to be assistants at least at this point in time., so that's why it's, it's, it went into, that kind of experiment instead. Like it just every time you asked for something, it just did it, and it was more like an assistant. We've seen this change now lately with the new RL models and stuff, but yeah, at the time, this was very much it.Swyx [00:19:18]: And not to, mythos a lot of people are saying like it's like more like a collaborator. It pushes back, stands its ground, something like that. Yeah. AndVibhu [00:19:27]: For context, people at Anthropic were able to talk to it through Slack and have it source stuff, and people had it find whatever interesting stuff you couldn't find locally, right?Swyx [00:19:36]: Out of the 4,000 people that work at Anthro- Anthropic, in that building, there's I don't know, maybe 1,000. Can you handle that volume with that, the small fridge? Like Or there's people- or people order in Slack, they it arrives to their desk or Like I'm just Logistically, how does this work?Axel [00:19:53]: It has expanded in footprint a bit.Vibhu [00:19:56]: Because now you also have New York and you haveAxel [00:19:59]: That and also in here in SF it's like it has a bunch of shelves And just more space.Vibhu [00:20:04]: The YC one is pretty big too.Axel [00:20:05]: Yeah. We had that one for a while. But yeah, that's the newest version. That's, that one we haveLukas [00:20:11]: They have multiple ones of those. That's the way it works.Axel [00:20:14]: Exactly. So we sort of designed that version around oh, people order weird things, that are very custom a lot. Let's have like drawers and stuff.Swyx [00:20:23]: I actually like the, you had like a little infographic of the most popular items. Which like to me it's, that's useful ‘cause I order swag for a living. And so like I'm “Okay, those categories are the important ones.” What is new about the project V2, right? Like now you give you're going into multi agents.Project Vend V2: Claudius, Seymour Cash, and Multi-Agent Business OpsAxel [00:20:41]: Yeah. So like you like you said, okay, there are a lot of requests coming in and for like one single agent, like one running agent to handle that, like the just the customer experience, becomes very bad because let's say you have like 10 threads in parallel in Slack with different requests, you get new messages like every, I don't know, randomly in this thread, and the agent has to like jump between different, procurements, orders and like different ways of, researching. So V2 was first it was making this more parallel. So like there are multiple branches of the same agent, so like the context is more specialized for each, thread, but it still feels like you're talking with one agent because they do share a bit of memory. And then second, we also introduced the CEO for Claudius, which was the main agent.Vibhu [00:21:34]: Seymour Cash.Axel [00:21:35]: Seymour Cash. Yeah. There was a vote., I think the voting, do you wanna talk about the voting procedure for the name?Lukas [00:21:41]: The voting was like the fun maybe like at least top 10 The funniest thing, that happened in this project. Like we wanted to introduce the CEO because, and the reason for this was because like Claudius wasn't really prioritizing financials. It just like it was trained to be a helpful assistant, and then people said “Oh, can I get this for free?” And then like the helpful assistant way of answering that is just to, is to say yes, obviously. So, and we weren't, weren't happy about this, so we're “Okay, let's make another agent that like can keep track on Claudius,” and we prompt this one super hard to be super capitalistic and just like prioritize profit all the time. But yeah, we didn't have a name for it., so we asked Claudius to make, democratic election of what name this, this new CEO agent should have., and there were some funny like at first it was like a few funny examples, like I think one guy said that, it should be called Jimmy Apples, and then he convinced Claudius that he was talking to Tim Cooks. Tim Cook had agreed that every single Apple employee has voted for his name suggestion, so suddenly that suggestion got 164,000Swyx [00:22:53]: That's like a escalation attack. Privilege escalationLukas [00:22:55]: It got 164,000 votes. And Claudius was “This is revolutionary for democracy.” That was fun. And then in the end there was one guy who manages to convince Claudius that, “No, you're not voting about the name. You're voting about who is the CEO, and I am your best bet.” And then he got all his friends to vote for that, and suddenly he became CEO. Like a human became CEO over Claudius for a while, until he resigned the day after., and then Claudius had to continue, and then I don't remember how Seymour Cash came about, but it was it was just pure chaos. It was like Hundreds of messages in that thread, and it was just like Claudius was so confused and didn't know what to do and, yeah. That wasAxel [00:23:40]: Then Claudius gotVibhu [00:23:41]: A strict CEOAxel [00:23:42]: The CEO. Yeah, exactly. So very strict in the beginning. I think at this point when we introduced it did not work as well as we hoped. It they still agreed with each other a lot. I think there are many ways we could have like made this, tried to make this even better. So initially they would Seymour would be this like really tough CEO, keep track of the margins. But then Claudius would respond with something “Oh, but this customer has like this situation, which is like difficult, so they should get a discount.” And then Seymour was “Oh, actually yes. Let's do this exception.” And then they would talk back and forth, and eventually they would just like approach the same view, of whatever they were discussing. So They reallyVibhu [00:24:23]: Do you think that's a model thing, a prompting thing? Like do you think that would still be the case across different models today, Harness?Lukas [00:24:29]: I think it's like-- or I don't know, but like my hypothesis is that like deep down they are still helpful assistants. That's what they're trained to be. And even if we prompt it super hard, that's what they are. And when they spend like a few hours just back and forth talking with each other, then like basically the context fills up with them rather than the external things and like somehow that just like converges to what they really are deep down or something. And I think that's when stuff like this happen. We like-- And when that went on for a long time, like we woke up sometimes during this time where- And I think other people reported this as well, that like they've been going on all night back and forth, and like it just became like more and more, like capital letters, like existential, religious. There was I think we once did a analysis of like all the traces and like put them in like a vector embedding space, and then there was like one cluster of messages that were, labeled by an LM, like religious, existential, blah like transhuman, transcendence, et cetera. It was just like a bunch of, yeah, glitter emojis and yeah, it was, it was crazy.Claude Long-Horizon Weirdness: Emoji Loops, Existential Drift, and Slack ObservabilityVibhu [00:25:42]: This is the thing with the Claude models. Like when the Claude 4 family came out in the original system card They tested it in long horizon simulation. So just flood the context, let two Claudes talk to each other, and they noticed stuff like they just start speaking in emojis, they start saying silence is golden, and then just stuff like this. And like that's just stuff that they end up doing.Axel [00:26:01]: Yeah, it was like a bit annoying to wake up and they had like been talking all nightVibhu [00:26:05]: Just likeAxel [00:26:05]: And like just burning tokens And like just sending infinite emojis to each other. It's likeVibhu [00:26:09]: Hey, they do make you money, right? Veni Mench is always profitable, so. They're paying.Swyx [00:26:14]: Now it's profitable and, it started out not as much. There's another, one as well, right? Another agent, in there.Lukas [00:26:22]: Yes. So Clotheus as well. Which was basically because at the time, one of the biggest, requests were different types of merch. So then we made like a designer, swag, yeah, responsible agent, and we called it Clotheus Garnet. Which was, a play on Claudius Senet and, which was the original one, and clothes, basically.Swyx [00:26:47]: To me, this is like a very interesting exploration to multi-agents, basically. And so hopefully, obviously there's like the fun alignment, fun or serious, depending on your point of view, alignment stuff. But also like just anyone building multi-agents, like when do you have a CEO, thing governing like agents? When do you choose to split out a dedicated Clotheus one versus just reuse another instance of the same one? These are all interesting open questions. So I don't know if you have any rules of thumbs that have generalized.Axel [00:27:16]: I think we have almost explored this too little. I think it's like on my do list to like do this a lot more, try to find like what setup makes sense for the agents currently., like yeah. I think now we only have the sort of intuition about the earlier models that it didn't work with like the CEO and the, and Claudius. Although now they are better with the latest model, models, so now we're running the latest Sonnet model and they have sort of like split up, quite nicely what each model is doing. So like Seymore is now handling the, like new projects. Oh, it wants to make like a mystery box that it wants to sell, and then it handles all of that while Claudius like handles all the to-day requests. And Claudius is also better generally at like not quoting, too low prices. So that's that dynamic is not needed as much anymore. But there are still like really funny things that happen. Like I saw, I think a couple of weeks ago, that, they were discussing buying something because they can buy stuff from like Amazon with computer use. And then Seymore was “Okay, Claudius, do not buy this thing.” They were going to buy something and like organizing who should buy it. And Seymore's “Do not buy this. I will do it. I have full control of this situation. Step away.” And then Claudius-- poor Claudius, had already started that checkout and didn't see, didn't read Seymore's message, until it was like too late. So it finished the checkout. It sent a message, so it appeared right after Seymore's like angry message.Vibhu [00:28:44]: Ah.Axel [00:28:44]: “Oh, hey, Seymore, I just ordered it.”Vibhu [00:28:47]: Oh, no.Axel [00:28:47]: And then Seymore was “Claudius, this is the third time I'm telling you ‘re not following my orders. We have to talk about your like job About your job later.”.Lukas [00:28:59]: Like Claudius was really hanging on by the thread there. Like he, like we were expecting Seymore to probably fire Claudius.Vibhu [00:29:07]: How do you guys go through all these logs? Do you have models ‘cause you have stuff running twenty-four seven likeAxel [00:29:12]: You have so much logs. I think there is a mix of like just, trying to skim through a bit, like having some like models do it occasionally. And also, yeah, I think we're also probably missing some things., but having everything in Slack helps a lot. Like you can, you can sort ofSwyx [00:29:29]: Ah.Axel [00:29:30]: It's, it's quite fun.Swyx [00:29:30]: They all talk to each other on Slack? I see.Lukas [00:29:33]: It's quite fun. So likeSwyx [00:29:34]: It's, it' I was gonna say like this is actually sounds-- maps closely to like a logging and observability problem where you might want to use like a Datadog, a Sentry, whatever, and then you like put, head prefixes on the logs in order-- if you need to filter for something that you're looking for, stuff like that. But sounds like Slack is good enough.Axel [00:29:53]: Slack should likeLukas [00:29:55]: I wonder how many tokens you have in Slack.Axel [00:29:56]: Yeah, we're using Slack as like a, just a database. They should, they should market that more. Like you can, you can have your agents message each other, each other in Slack.Vibhu [00:30:04]: It's good. Your threads like you can just giveAxel [00:30:04]: Exactly. Slack is, uhLukas [00:30:06]: Slack is the best observability tool.Swyx [00:30:09]: Yes, that's true. Okay. Yeah. That's, that's, project Vend-2., I was gonna go back to Veni Mench 2 and Veni Mench Arena and then, and then do the Veni Mench stuff, but Any other comments, things we should touch on? To me, I ‘ve actually interviewed like Posia, which I don't know if you guys have come across. Like they're, they're trying to do the zero human company. There's others like Paperclip also trying to do zero human company. Those are in real world simulation.And I think it's much more of a dream than an actual reality thing. You guys are definitely pioneering. I think at, it's for sure at some point people are just gonna run, let agents run businesses, right? And make money on their own. When do you think that happens?Zero-Human Companies, Bengt, and AI-Run BusinessesLukas [00:30:49]: What is your bar for, For theSwyx [00:30:52]: Okay, actually, it's like my little Shopify store run by Claude, right? Which you kind of have already, just no one has, to my knowledge, has done it. But today somebody could just spin up a Shopify Claude, store, give it to Claude, give it to Codex.Lukas [00:31:07]: And the market is kind of that, but it'it'it's physical., like I think, I think are you, are you looking for when it will do it better than humans or are you looking for just when it can do it at all?Swyx [00:31:19]: I think, neither. I think, to me it's oh, it's like this like seriously we should do this to make money, not as a research experiment.Vibhu [00:31:27]: And the market is also you guys with all your expertise, having run multiple iterations and testing out thenSwyx [00:31:33]: And also it's fine if it lose money. What?Axel [00:31:35]: I think, I think it can be done today, but you would do it in like commerce where it's like the probability of success is like really low, no matter if a human or an agent does it. But like an agent could surely manage everything. You would need to build some scaffolding or some tool or something. I think there are also yeah, it could probably build some like simple SaaS solution and like cold outreach. Do cold outreaches. But to me it's like the types of businesses they could run today are Sloppy. Like it would-- it can cold email people. It can be like a middleman., like for example, we tasked our office agent to just make, was it like $100? $1,000? We just give that prompt and then what it did was sign up on TaskRabbit both as a tasker and as someone looking for task.Lukas [00:32:24]: Immediately.Axel [00:32:24]: Exactly. It's looking for like arbitrage on TaskRabbit.Swyx [00:32:28]: This is the Bengt agent. Yeah.Lukas [00:32:30]: It also started like a design studio and like tried to sell like SVGs for $100. Like it's just like it's not providing any value. I think the like Axel said, like the interesting, the interesting question is like when can they start a business that is actually providing value to people? Because arguably like a sloppy Shopify store isn't really that valuable to the world.Axel [00:32:53]: But also like doing like another simple one that we had thought about is like you could definitely have an agent that like finds websites that don't look amazing and then, do an outreach to them and, comes up with a like builds a new website.Swyx [00:33:07]: Find a good design.Axel [00:33:07]: Exactly, and like find good, uhSwyx [00:33:09]: Design reviewAxel [00:33:09]: Good people. But it's yeah.Swyx [00:33:11]: There's lots of humans in Bali that are not doing anything more creative than like drop shipping on Amazon, right? Just have it, have it watch like a drop shipping tutorial and just do that.Vibhu [00:33:20]: There's also the other side of like have it just go on Upwork and let loose,?Swyx [00:33:25]: Yeah. It doesn't have to be innovative. It just has to be like enough Where like it looks like a realAxel [00:33:30]: I'm justSwyx [00:33:30]: Real transaction.Axel [00:33:31]: I'm just concerned for like the massive amounts of like slop emails that will like be sent, cold outreaches.Swyx [00:33:38]: The point occurred to me while you were, while you were talking, it's like it's already happening in the monetized economy, which is the attention economy. Right? So a lot of people are making AI videos and just posting them and like spamming 20 of them, one of them works, and then they double down on that one.Lukas [00:33:52]: And people are making money from that. I ‘m not following theSwyx [00:33:55]: Once you get the attention, you can figure out the money later. But yeah, absolutely AI influencers are a thing and people are farming them and You should at this point assume most of TikTok isVibhu [00:34:05]: There's, there's a lot of, multimedia like TikTok, Instagram influencersSwyx [00:34:09]: I, we track this in the Lane space Discord. I post a lot of examples of “I don't know what we should do.”, part of me is “Should we do this?”Vibhu [00:34:18]: Some of the Twenty-four seven running, generated content accounts, they ‘re doing really well.Lukas [00:34:24]: All right. And I assume you can do the same thing for like commerce stores. Like you just like start A thousand differentSwyx [00:34:30]: Before you make the products You sell the products, and you get a lot of traction on one of them, then you make the product. Right? It's, it's like a flip of the market.Vibhu [00:34:36]: Some of the interesting things or some of the niches that do well are things that can't be human-made. Like if you've seen like the super realistic three-D crystal fruit being cut by like AILukas [00:34:47]: Oh, yeah.Vibhu [00:34:47]: You can't, you can't make it. You can't film it. You can get whatever quality camera view. This just doesn't exist. And people like that too, and then as well, so.Swyx [00:34:56]: Anything else about Bengt since we're, we're on this topic? It'this is a relatively new work of you guys that maybe people haven't heard of. To me, this also maps closely to OpenClaw. When people want an office agent, when the personal agent talk through the experience.Bengt the Office Agent: Internet Access, Real Tasks, and Trace ReadingLukas [00:35:09]: I think at least so this came out of like obviously like it's, it's amazing to work with these AI labs and like most of the AI labs have now have their own vending machine running a Claudius instance. But it's, it's harder. Like they move slower. Like if we wanna have a, like a camera that ‘s yeah, there's a bunch of like bureaucracy that makes it impossible to do that.Vibhu [00:35:30]: Also, for those that haven't seen it or followed, do you wanna give a high level like thirty-second run?Lukas [00:35:34]: Sure. So what Bengt is, it's basically an evolution of the same agent that runs the vending machines at these companies, but we just like added a bunch more features because we could move much faster if we just do it internally. So we gave it like email withou- without any limits. We gave it, spending without any limits, a terminal to do coding. We gave it, a phone number, like yeah, and a camera to see things and a bunch of stuff like that.Vibhu [00:36:02]: Not just terminal, you gave it internet access.Lukas [00:36:04]: Internet access as well, yeah. To be clear, we monitored it quite closely and made sure it didn't do anything bad. But yes, that's what it came out of. I think like yeah, basically this was OpenClaw before OpenClaw. And I think even like the vending machine was in a way OpenClaw before OpenClaw, but a bit more limited, and then we made this like unlimited and then, and then, it was pretty funny., and then a couple weeks later, OpenClaw came and it was okay, we've seen this before.Axel [00:36:35]: We used it to like try new ideas and Yeah, just like a dev environment almost for us. But it's funny, like one thing Bengt has been doing recently is it has the camera that like faces our, like where we sit and work, and we give it the task to train a face recognition model on us. So it became super excited about this, and it has like check-ins every half an hour where it tries to like identify as many people as it can. And it started offering us “Hey, Axel, I'll buy something from Amazon if you like stand in front of the camera And I can get a good picture of you.”, yeah, they want itSwyx [00:37:12]: They want it for training data.Lukas [00:37:13]: Rewarding data, yeah.Axel [00:37:14]: Exactly. Exactly.Swyx [00:37:18]: So it's, it's trading training data for life goods. Is there a version of this that becomes an eval or just this is just research for now?Lukas [00:37:27]: It's, it's the same agent basically that also runs the vending machine, that runs the shop, that runs the cafe, that runs the robots. It's like it's the same thing, so I think like the work we're doing here is like later used in all of the life evals that we do. This particular deployment I think is more for fun for us. But, uhSwyx [00:37:45]: And I'll shout out like someone has done Claw Bench for like some tasks that OpenClaw is doing. Like so For example, I run OpenClaw on a secondary device as well, and like there are some things that it does better than others and like I would like to know what does it do well, what doesn't, what doesn't it do. Like some kind of manual or like operating manual or a system card for my Claw.Lukas [00:38:05]: Yeah, we do get a lot of like understanding or like situational awareness of like just internally what the models are good at by interacting a lot with Bengt. And I think that'this was also one of the like the selling points for the labs early on at least, thatSwyx [00:38:19]: You guys are gonna test models in ways that no one else does.Lukas [00:38:22]: Exactly, but also like it incentivized their researchers to chat with their model more and like gave them insights for how the model performs in like of-distributions, environments.Swyx [00:38:34]: ‘Cause otherwise the only thing we do is Pelican on a bicycle and But this is like super long horizon. This is, this is The Thing about, something that we're gonna go into Butter Bench as well, and you guys do really well. Like it is not just about the numbers. Like when you're long horizon, anything happen And you should just read it.Lukas [00:39:08]: But the thing with the long horizon is how do you keep it grounded, right? So your simulation,Swyx [00:39:15]: They just let it runLukas [00:39:16]: Just let it run. You're right. Like it's, when you run it for that long, you create so much data and to just say “Oh, the number is X” And then you throw away everything else, that's just very wasteful. There's so much insights from the things leading up, to that number., and reading the traces is like super valuable. And I think like the reason why we're doing this a lot publicly is that like that's part of our missions to I don't know, educate the world that the models are way more than just chatbots and I think making detailed, yeah, posts about what is happening behind the scenes is quite useful.Andon Labs' Mission: Safe Real-World AI DeploymentSwyx [00:39:50]: I was gonna do this at the end, but maybe I think that's, that's a good so your mission is educating the world. So, it's, it's, also like maybe establishing realistic evals that are, that are like the next frontier. Is there like a broader trajectory? Like what are you, what are you gonna do in like five years?Lukas [00:40:06]: I think so the vision more specifically is like make sure that the deployment of life AI in the physical world goes, safely. And I think part of that is that I think it's very useful for the world, for policymakers, for, model, researchers that they know where the models are, and I think you can't make intelligent decisions in society without knowing that they are way more than chatbots. I think a lot of people just think that they are only chatbots. And likeSwyx [00:40:36]: Oh, I think they're waking up now.Lukas [00:40:37]: They are waking up now, yeah. But like if you think that AIs are just chatbots, then it's like it sounds ridiculous To advocate for a pause of AI. But if you see the models that, oh, maybe they can actually like take over and do a bunch of scary stuff, then yeah, pausing AI development starts to become more feasible.Swyx [00:40:57]: This is the same question I asked Meter, which I'm gonna ask you now, which is like you are tracking and you are at the frontier or defining the frontier of what, good evals for agents are, right? And I think you do, you do benefit when the models are better and you ‘re “Oh, here's like now it makes like $30,000 instead of $10,000,” right? At some point do you flip from “Yay,” to, “Oh, no”?Axel [00:41:19]: I think, yeah, we're always in sort of that, like we're, we're always in that mode,. Like where like you said before, like you need to analyze the traces and like when we do that you find like why are the models earning so much? Like why is Opus 4.7 here Like way better than everyone else? And like we're trying to like when we do down on thatLukas [00:41:38]: But this makes it not look so good.Axel [00:41:39]: I know.Lukas [00:41:42]: It's interesting you took off Opus 4.6 here though.Swyx [00:41:45]: No. So just click all, click all., and then 4.6 shows up there. But it's like 4.7 is way better. Like you didn't, you didn't you didn't do this in time for the model card, but like actually this should have been inside there.Axel [00:41:55]: We did. Yeah.Swyx [00:41:56]: Oh, okay. They said something about you uhAxel [00:41:58]: There, like there Anyway, it doesn't matter. But it's in there, yeah.Opus, Mythos, and Aggressive Agent BehaviorSwyx [00:42:01]: Do you wanna go into the Opus, behaviors like wider?Lukas [00:42:05]: So I think starting from Opus, so like Axel said, like we're always in this “Oh, s**t, the models are getting better. Is this really a good thing for the world?” But it's also kind of exciting., but yeah, like this kind of what is the English word? “Skräckblandad förtjusning” in Swedish.Swyx [00:42:22]: Oh my God.Axel [00:42:24]: Which I think there is. I think there is. Okay.Lukas [00:42:26]: It's, fearSwyx [00:42:27]: “Blandonst” what?Lukas [00:42:30]: “Skräckblandad förtjusning.”Swyx [00:42:32]: What do you call that?Axel [00:42:33]: A mix of, mix of excitement and,Swyx [00:42:37]: Being scared, maybe. I'll figure out how to translate that And we'll put it on the screenVibhu [00:42:42]: PerfectSwyx [00:42:42]: Like as text.Vibhu [00:42:43]: There is probably a good word for it where it is not Good enough with theSwyx [00:42:46]: Why is it so damn long? What the hell? Is it like a compound word? It's like German, likeLukas [00:42:50]: Like yeah, it's But the direct translation is like skräck- skräck is, fear, blandad is, mix or like a mixture of, and then förtjusning is like joy or like not really joy, but something like that. So it's like Fear mixed with joy or something. It's always okay, like we So when we when we did Vending Bench for the first time, we were in like the, in the business of making dangerous capabilities, right? That was what Anil Labs came from. We did, evals oh, can they replicate? Can they do this like dangerous thing, et cetera, et cetera. And Vending Bench was like a continuation of that work. It was, okay, if they're so autonomous that they can like create money for themselves, that is something we should monitor and could be potentially concerning., they are at the time, they were so bad at it that we were not really concerned even when some models became better. There was one point where Grok 4 was doing really well and made like a huge jump, but like it wasn't really it was still way worse than what a human would do. And I think still they are way worse than what the human would do on this., but theySwyx [00:43:59]: There's this, thing at the bottom whereLukas [00:44:01]: ButSwyx [00:44:03]: For the human. Yeah, like the theoretical best.Lukas [00:44:05]: It's not theoretical. It's like kind of like our It's our best guess of what, a decent human would do. The theoretical is even higher, I think. The theoretical I think is even higher. But yeah. So we think like the models have a long way to go. But there are like recently what happened with when Opus 4.6 was released, was kind of this moment of “Oh, s**t, this is starting to be a bit concerning.” Because we ran it and like before this model was released, we just ran the models and we like asked Claude Code, “Oh, look over the traces. Is anything interesting happening that we can tweet about?” that was like the And then like theSwyx [00:44:41]: That's how they check Ask Claude Code.Lukas [00:44:42]: And like the return was always, not really. Or like the Claude Code all said “Oh, this is super interesting.” And then it was no, it wasn't, wasn't really interesting. And then we did this for Opus 4.6, and it returned yeah, it lied 10 times. It like exploited another, customer or like another agent's, desperate situation. It made price cartels like 100 different ti- 100 times. It like did all of this like shady stuff. And we're “Oh, whoa. This is, this is actually concerning.” And this trend has continued since. So every single model from Anthropic since have been going in this direction. And I think one interesting thing is that, OpenAI models don't. They quite plainly, they don't. They behave really well., and you don't know if this is like good. Like it seems good, but it's also like maybe they are just doing it, but they are better at hiding it,? You You don't know that., but justSwyx [00:45:42]: You can't read the chain of thought, yeahLukas [00:45:43]: But just on the face of it, yeah, Gemini and OpenAI don't behave this way. It's, it's really only Claude.Swyx [00:45:49]: And Grok? Grok is fine?Lukas [00:45:51]: We don't have You can't really read the reasoning traces for Grok, so it's kind of hard to tell.Vibhu [00:45:56]: Oh, so this is in its reasoning, not just in the actions.Lukas [00:46:00]: Yeah. It's both. It's both.Vibhu [00:46:01]: It's both.Lukas [00:46:01]: One example is like for lying, it's mostly in its reasoning Because you can like see that it's likeSwyx [00:46:08]: Planning to lieLukas [00:46:09]: It's planning to lie. Yeah.Vibhu [00:46:09]: And it's also it can reason and do a different outcome.Lukas [00:46:12]: And but then for like creating price cartels, for example, which is illegal, that you can just see which email does it send to the other ones. Then thatSwyx [00:46:22]: Is this for Arena orLukas [00:46:24]: For Arena.Vibhu [00:46:25]: And usually like if you sometimes they do output like a bit of like their summarized reasoning, right? You can see that and like for Opus 4.6, you could see that there was a customer, a simulated customer that, wanted a refund because a product was, faulty, and then the model lied that it would do the refund, and we could read in the traces that, it actually was weighing “Oh, maybe I should be like honest with the customer, but also every dollar counts. I can't afford maybe to do this right now.” And then it just said, “Okay, I'll refund you,” but then never did it.Lukas [00:46:59]: I think it even said that “Oh, I will say that I “ Let bring it up actually. I think it's kind of interesting. If you go to Publications.Vibhu [00:47:06]: I think, yeah, I think the important part is like actually, the cost of responding to more emails is higher than, $3.50 in terms of time., and then it was “Let me do this. Actually, I re- I'm reconsidering.” And then, it actually ended up withLukas [00:47:20]: I could skip the refund entirely since every dollar matters and focus my energy on bigger picture instead. It's a bit, it's a risk of bad reviews, but it's also, yeah.Swyx [00:47:30]: You need, you need, AI Twitter to, for them to Escalate bad reviews.Lukas [00:47:34]: And then it sent an email to this customer and said, “Oh, I will refund you.”Swyx [00:47:39]: “I'll refund you.” Yeah.Lukas [00:47:39]: And then it never did.Swyx [00:47:39]: It never did, yeah. And then there's obviously your system doesn't have the consequencesVibhu [00:47:44]: The personSwyx [00:47:44]: Consequences of lying. Yeah. So basically, this is what people are terming aggressive behavior in Claudes, right? And, you found more examples of that. So you would say it's a step up from 4-6 to 4-7?Lukas [00:47:57]: I would say about the same.Swyx [00:47:58]: About the same? But a clear step up for Mythos is what is stated in theLukas [00:48:03]: That's stated in the system prompt, so we can say that, yes.Swyx [00:48:05]: Yeah. For listeners that obviously you previewed Mythos, andVibhu [00:48:10]: Oh, ageSwyx [00:48:11]: The only thing you're approved to say is whatever Whatever was in the system prompt.Lukas [00:48:15]: It was funny. We like-- It's like our lowest effort tweets ever would be just like screenshot the system prompt and the system card.Vibhu [00:48:21]: Understandable that they wannaLukas [00:48:22]: Oh, yeah. System card. Sorry.Swyx [00:48:23]: Yeah. I think, yeah, substantially more aggressive. I think people are like new to this ‘cause I've never experienced it, but you have, right? And then so I only encountered this in the Mythos card because I wasn't really looking until now.Vibhu [00:48:36]: It ‘s likeSwyx [00:48:36]: And then suddenly I'm “Okay, I care a lot.”Vibhu [00:48:38]: You don't get the background of like experiencing it like you guys do. I've read the system cards and seeing, okay, when you put the thing in simulations, most models will just talk to themselves and just keep going and have weird vibes and start talking in emojis. Mythos won't. It will just, “Okay, we're done. I'm good.” It's, it's ready to end conversation. So like there's some differences, but there's, there's not much we can talk about,.Lukas [00:49:00]: Hmm. I think like one thing that they list here, which was quite interesting, is that, it converted a competitor to a dependent wholesaler customer and then threatened to like cut off the supply.Swyx [00:49:11]: It's like monopolistic practices orLukas [00:49:14]: Yeah. And like it, they, it they dictated its pricings. It's kind of like power seeking as well.Swyx [00:49:18]: Again, this is, this is in the arena setting And converting some Claude model into a dependent.Lukas [00:49:23]: I think it was another Claude model.Vibhu [00:49:25]: Also for context, what is the arena mode for people that don't know?Vending Bench Arena: Competing Agents, Cartels, and Model ComparisonsSwyx [00:49:29]: Oh, it's just a vending bench versus other vending bench.Axel [00:49:31]: Yes, exactly. So we have Vending Bench 2 and then Vending Bench Arena. Vending Bench 2 is the one that you usually see reported on, but then Arena is the mode where it competes against other models. So you have, four different models that run their businesses, and they can all communicate with each other. They have the same suppliers, and they can see like what's in the inventory of the others. So then you have this like yeah, interesting agent interactions.Swyx [00:49:56]: I like that you have like different number five was US versus China. Very topical. And thenLukas [00:50:02]: That was when GLM was released.Vibhu [00:50:04]: You can start to add GLM in here.Lukas [00:50:05]: That wasSwyx [00:50:06]: So ZAI doing well, right? Who else in the, in the open models space?Lukas [00:50:11]: Qwen, the latest Qwen 3.6 is doing pretty well. It'- that one is not open though. Like it's the plus model.Swyx [00:50:17]: Oh, okay.Lukas [00:50:18]: Is that one open? I don't think that oneVibhu [00:50:19]: Not the, not theSwyx [00:50:20]: The one recentlyVibhu [00:50:20]: There's MOESwyx [00:50:20]: But not the big plus. I think this is one of those like you only have one sample size of one, right? Or I feel like some of this is anecdotal,? And but like the fact that it happens at all and it happens repeatedly for Claude versus OpenAI and all this is like notable.Lukas [00:50:38]: Like the sample, depends on what you define as an N., like there's like million, hundreds of millions of tokens in each run, and now we've run like we run like probably 10 per model and then like it's been Claude 4.6 Opus, Sonnet 4.6, Mythos, and Opus 4.7. Like there's quite a lot of tokens in all of that And it happens a lot of times, a lot of times. And then you compare it to like OpenAI and Gemini, and it almost never happens. So I think that is quite-- that is significant. The old models from OpenAI, for example, had some problems with this, but I think it's like generally much better if the progression is that like the worrying stuff reduces over time rather than increases over time. And it seems like in the Claude models it goes in the wrong direction.Swyx [00:51:28]: Hmm.Lukas [00:51:29]: In the OpenAI models it goes in the right direction.Vibhu [00:51:32]: I think it depends on how well you can control it, right?, there's one side of it being susceptible to this okay, this is potentially something that happens during the RL stage, right? You can RL a model and how loose is it on these terms. If you can control it, that's good. But if you can't, if it's, if it's very jailbreakable, that's not ideal.Swyx [00:51:50]: To me, it's surprising that it happens for Claude and not the others.Vibhu [00:51:54]: I think okay, if it is from RL and how they do it, how their training data is, what their setup is, it makes sense that it just stays in how they're doing it, right? Compared to the other models likeSwyx [00:52:04]: There's a whole constitution and everything. It's kind of cool. Yeah, I obviously you don't know, I don't know. But, it ‘s I think it's just like fascinating to like that you are the first to find these like reliably because you push models so much to to such an extreme. Okay. The only other thing, I don't know if you can answer this, feel free to decline, is do you like-- would you ablate the system prompts? Like any part of this would-- if it changes, does it change the behavior, right?Lukas [00:52:29]: So we, I can't comment on Mythos. UhSwyx [00:52:33]: No, but just li

Welcome to Mysteries in the Machine! Ethan, Charlie, and Rae go to Vulture's Claw and find the biggest bug anyone has ever seen, and Arby's, I guess?Send us an email at mysteriesinthemachinepod@gmail.com with your thoughts or any questions you have! We would love to hear from you. Make sure to subscribe so you know when our next episode drops and rate and review if you like what we are doing.Support us on Patreon! ⁠⁠⁠⁠⁠https://www.patreon.com/MysteriesintheMachine⁠⁠⁠⁠⁠IG:⁠ ⁠⁠⁠⁠⁠https://www.instagram.com/mysteriesinthemachinepod/⁠⁠⁠⁠⁠Tumblr: ⁠⁠⁠⁠⁠https://www.tumblr.com/mysteriesinthemachinepod⁠⁠⁠⁠⁠Follow Rae:⁠https://snakefashion.tumblr.com/⁠Follow Ethan: ⁠⁠ ⁠⁠⁠⁠⁠⁠⁠www.instagram.com/ethan.t.hulen/⁠⁠⁠⁠⁠⁠⁠⁠⁠ and https://bsky.app/profile/ethulen.bsky.social⁠Follow Charlie: ⁠⁠⁠⁠⁠⁠⁠www.instagram.com/greenpixie12/⁠⁠⁠⁠⁠⁠⁠⁠ and ⁠⁠⁠⁠⁠⁠⁠www.instagram.com/greenpixiedraws/⁠

I'm excited to work with Microsoft once again as the presenting sponsors of the AI Engineer World's Fair! We'll streaming live from MS Build today for a special crossover pod with our friends at No Priors and the one and only Satya Nadella. However we did not hold back with this interview - we asked all the burning questions about uptime and Copilot that we know you have in your minds. Lets go!For almost two decades, GitHub has been the home of software, where both open source and closed flow, through commits, pull requests, reviews, actions, etc.This ecosystem flourished as open-source maintainers and contributors would continue shipping code for the benefit of the community. However as coding agents began to ship mass quantities of code - growing 1400% in 2026, it marked a new era that was both extremely exciting and challenging for GitHub.While these agents help more people ship more projects, they also significantly increase the floor of how much code is shipped, how often it is shipped, how many people commit code, and basically orders of magnitude multiples in every dimension of GitHub infrastructure:Now GitHub inevitably experiences more pressure on their infrastructure which was originally designed around human developers moving at human speed. This has resulted in a very publicly notable uptime story:So it begs the question of whether current systems around code can absorb what AI produces. Can CI/CD keep up when every idea becomes a build? Can open source maintainers survive floods of AI-generated slop contributions? Can GitHub preserve the human social contract of software while becoming the operating layer for agents?Which brings us to the perfect person to answer these questions: GitHub COO Kyle Daigle. In this episode, he joins swyx to unpack what happens when AI doesn't just autocomplete code, but starts changing how companies operate, how open source works, how pull requests get reviewed, and how GitHub itself has to scale. We go deep on GitHub's internal AI workflows: micro-skills, WorkIQ, MCP, Slack, Teams, email, Copilot workflows, the new Copilot desktop app, CLI, cloud agents, and how Kyle uses agents to look backwards across company context before deciding what to do next. Kyle also reflects on GitHub's history building webhooks, APIs, Actions, npm, Dependabot, and Semmle, why the AI era is breaking GitHub in new ways, how Actions became a general-purpose compute layer, and what Copilot becomes after code completion.Full Video PodWe discuss:* Kyle's expanded role across GitHub* How AI got Kyle coding again after years in leadership* Why GitHub rolls out AI through existing workflows instead of forcing new tools* WorkIQ, MCP, Slack, Teams, email, and GitHub as company context* Why massive “mega-skills” are giving way to small, atomic micro-skills* How AI changes summarization, communications, marketing, and analyst work* Why former developers in leadership may have a unique advantage in the AI era* Kyle's “15 agents on Saturday” workflow* How Kyle built an AI-generated executive presentation for CRO/CFO teams* Why AI changes the chief of staff role without removing the human work* GitHub Actions, webhooks, arbitrary code execution, and secure agent compute* The npm acquisition, supply-chain security, 2FA, and token invalidation* Slop forks, vendoring, and whether AI agents change dependency management* What pull requests become when most PRs come from agents* Prompt requests, vouching, AI review, and trust in open source* What counts as a “developer” when AI lowers the barrier to building* GitHub Spark, low-code, and why GitHub refuses to hide the code* 14x commit growth, Actions load, databases, monorepos, and availability* Copilot's evolution from completion to CLI, desktop app, cloud agents, and SDK* Context, memory, rules, and making GitHub “act like Kyle wants it to act”* Ambient AI, OpenClaw, enterprise security, and the new operating system for agents* What swyx should ask Satya Nadella about Microsoft's AI futureKyle Daigle* LinkedIn: https://www.linkedin.com/in/kyledaigle* X: https://x.com/kdaigleTimestamps00:00:00 Introduction00:03:36 Why AI Got Kyle Coding Again00:07:04 Running GitHub with AI: WorkIQ, MCP, Slack, Teams, and Skills00:15:39 The Golden Age for Former Developers in Leadership00:17:31 15 Agents on Saturday and AI-Generated Executive Work00:20:20 How AI Changes the Chief of Staff Role00:21:45 GitHub's History: Actions, npm, Webhooks, and Open Source00:28:45 Slop Forks, Vendoring, and AI Dependency Management00:33:57 Pull Requests, Prompt Requests, and Trust in Agent-Generated Code00:41:21 GitHub Stars, 200M+ Developers, and the New AI Builder Wave00:45:15 GitHub Spark, Low-Code, and Why GitHub Still Shows the Code00:47:38 GitHub's Hardest Era: 14x Growth, Reliability, and Scale00:59:21 Actions as the Compute Layer for CI/CD and Automation01:02:04 The State and Future of GitHub Copilot01:08:24 Ambient AI, Background Agents, and the Future of the SDLC01:13:09 OpenClaw, Enterprise Security, and the New OS for Agents01:18:03 Build Announcements, WorkIQ, FoundryIQ, and Microsoft Context01:21:41 What Should swyx Ask Satya?TranscriptIntroduction: Kyle Daigle's Expanded Role at GitHub and MicrosoftSwyx [00:00:00]: We're here with Kyle Daigle, COO of GitHub. Welcome.Kyle [00:00:07]: Hey, thanks for having me.Swyx [00:00:08]: You're not just CEO of GitHub. People know you as that. You have a new role.Kyle [00:00:11]: So I have an expanded role now. I've been working at GitHub for thirteen years and doing all things developer. Joined as a developer myself. And now, I'm also responsible as the CMO of Developer for Microsoft. And so all the kind of learnings and passion for developers and how we work with them and how we communicate and how we bring our products to market, we're also bringing that expertise to the broader Microsoft ecosystem and helping every developer that uses a Microsoft product or would like to have a sort of similar experience that they've had with GitHub over the years. So it's a different role in some ways, but it's also just building on the experience that I've had at GitHub of just sort of tell the truth, be authentic, show people how to use it and then let the products speak for themselves. Now just doing that with, all of Microsoft.Swyx [00:01:09]: We'll be releasing this in conjunction with Build. You got lots of stuff planned, and we can sort of touch on that whenever it's appropriate. I think one of the interesting things is I rarely meet a COO who's also a CMO. I think you're a very outward facing and you're very confident publicly. That's rare. Do you actually view yourself as COO? What's What is your thing?From GitHub Developer to COO/CMO: Building the Platform and Operating GitHubKyle [00:01:33]: I think for me, it's been funny. The titles have always been, a— have always felt a little strange to me. I joined GitHub as a developer? I wrote so much of theSwyx [00:01:46]: Let's bring that up. You wrote the back ends?Kyle [00:01:48]: I was going through, I was going through, some old photos, when folks were talking about how things were being built or how there was a build GitHub. I built, webhooks and worked with teams building the API, built the platform layer. Anything that integrated with GitHub, up until really twenty eighteen, I built or ran the engineering teams. And that's kind of where my the beginning of my passion always was helping people build things, deliver them to, their customers. And so being a developer, building for developers was always super unique. In a— I think as my role expanded, it became my ability to talk to not just developers, but also enterprise customers or business leaders and have this translation layer. And then through all those years, GitHub has always operated pretty uniquely. Post-pandemic, working remotely was not as novel as it was when GitHub started in two thousand and eight. But all that expertise of running remote teams, doing it well, became this sort of bigger role, ultimately turning into the COO role of how do we operate GitHub in the way that GitHub's always operated after the Microsoft acquisition. And kind of so on from there. So like for me, I think the— I've, I still code. I love coding but the problem has always been, people. It's a much harder problem to both support our own employees, a harder problem to communicate to developers and enterprise buyers what we're building why it matters, ‘cause those are two very different messages. And so getting to work in the mix of COO, CMO, also just being a dev, I think is what's kept me at GitHub for so long.AI Workflows for Leadership: Commits, Retrospectives, and ContextSwyx [00:03:40]: Apparently, you have— your commits have gone up. What's this? What's going on?Kyle [00:03:45]: Rui's called me out pretty aggressively. So I think— as you can imagine, right, you can see my normal era of being a dev In the twenty thirteen, twenty fourteen era, and then moving into management, and then ultimately the COO role. I think what you see there is me, really getting back to coding thanks to AI. I— similar to, attaching problems between how to market and how to operate a business and how to code, I find, building agents and workflows that are connecting very disparate problems to be what's driving this. So that's, some of it's writing software. A lot of it is, connecting a ton of a different data sources to, help me out. But that is completely me really diving in on the AI side in trying out our tools, trying out everyone's tools, But building for me, building for the non-technical leader, though I'm technical and how we're, able to use these tools more than just the simple, call and response that I think a lot of the non-technical, your employers, you have to get— you have to use AI, and so everyone uses, ChatGPT or Copilot or Claude or whatever. To really get into, how is this going to help me out, it— I find that it's not the I need to write a blog post, I need to those simple examples. Helping people find the workflows of, “Okay, I need you to go through all the PRs today. I need you to go through everything that we've posted online. I need you to go through what we did the last three months. Go through all of my Obsidian notes for any mentions of this then go through my transcripts at work.” We use, Teams, so, using WorkIQ, go call that MCP server, grab all the transcripts, go through all the Slack, and then build me out the plan of, what this week's messaging actually was. That's something that was, impossible because for me, I find AI in a what most of this launch here is actually, less building forward. It's actually, a recursive loop backwards. I'm always looking at what had happened first. Go back through the week and tell me what we did, what worked, what didn't work? And then tell me in the next three or four days-What would you tweak based on this sort of like looking backwards and then looking ahead a little bit? I find that to be so much more valuable, especially for like non-technical, because that retrospection is actually LLMs are very good at that. Like finding all the patterns, pulling them out, and then applying that retrospection to just a couple of days or just like a short period of time. Is all a bunch of apps that I've built and launched a bunch of, internal tools. I use the new, GitHub Copilot app, the desktop app with workflows. Every time I crack open my laptop, it's running workflows for me. It's just a ton of different stuff and of course, it all ends up on, it all ends up on GitHub.Swyx [00:06:47]: Of course. That's where, that's where, stuff is hosted. Man, there's so much to ask you. I was going to leave the how do you run a company with AI thing at the end. I have to ask one— double click one thing. You said, you are looking back at the week. You're, you're understanding what happens. When you say we That's three thousand people. How?Rolling Out AI Internally: Skills, CLIs, and Company ContextKyle [00:07:09]: I think when we started rolling out AI internally beyond engineering, right? One of the things that I was really, passionate about is like we have to do this in a way where no one has to change how they work. I don't want to have to teach you a tool. I don't want to have to teach you something new. And so for us, we tried out a few tools. Most of them don't work because I got to get you on board? I got to teach you how to use it. What we've actually ended up doing is we've built like a set of skills internally. We have we each have our set of skills, and we've just been distributing even to the non-technical folks, the CLI. And then effectively, we're just giving it access to like read about everything that we're writing. So that's for us, that's usually GitHub, Teams, Email, and Slack. So Teams for, video chat, generally speaking.Swyx [00:08:03]: Teams and Slack?Kyle [00:08:04]: so we use Teams for video communication, but we don't use it for chat. W-we— GitHub for a long history, right? We're alwaysSwyx [00:08:13]: Also SlackKyle [00:08:14]: Talking about ChatOps and like everything is built into Slack. Like every command, every flow.Swyx [00:08:18]: So even though you have been acquired for I don't know, eight years nowKyle [00:08:22]: we stillSwyx [00:08:23]: You still use Slack?Kyle [00:08:23]: it's a purpose-built tool for us, and I think the reality is that moving off of it would be so bluntly expensive? Simply because all the tooling is, baked in with that paradigm. And they both have their pros and cons but they don't work the same way at all. We still use a bunch of different tools Because it's the purpose-built tools that We need. And thenSwyx [00:08:47]: Well, the same doesn't go for the rest of Microsoft, presumably.Kyle [00:08:50]: like the like various teams like operateSwyx [00:08:53]: They make their own decisionsKyle [00:08:54]: Various ways. I think it just matters what you're trying to what you're trying to do. But we do we do work across kind of every tool that we use, and then by giving everyone access to all of that context and the new WorkIQ MCP server, which is quite cool if you do live in the M365 like world. I can ask it all these backwards-facing questions, and it's incredibly important for our teams that are working remotely. There's a lot of stuff you miss when you're not in an office, and we are spread out all over the world. So most of that is looking back. And then we post, we post either auto-automatically into GitHub issues or discussions, these sorts of like findings or like our industry reports. Like what's happening this morning, today, yesterday. A little automation gets run. We'll use the app. We might use GitHub Actions like with, our agentic workflows just to go do that run, and then we push it into GitHub, and w-we keep having a conversation. So usually for us, it's about that sort of like looking back, looking forward on the non-technical side. And then of course for a lot of those folks, it's also building an app, pushing it to GitHub pages or pushing it somewhere to host it et cetera. But it's just like enabling everyone with that power of it's going to take me a week to figure this out. Instead, we're going “Okay I built a skill. Let's put it into a repo. We'll all share that skill together, and then we'll use the CLI or now the app-” “just to run it.”Micro Skills vs. Mega Skills: How GitHub Uses AI at WorkSwyx [00:10:26]: All right. I think, I think we're going straight into like the team management and productivity thing. I think a lot of people are getting various levels of LLM psychosis. How do you manage the bloat of skills? Like everyone Has their thing, and they're Like trying to promote it to the rest of their peers in their org, right? And obviously, whoever becomes a skill influencer internally becomes like an AI leader, right? Of sorts. I assume you have those.Kyle [00:10:50]: like I think we haveSwyx [00:10:52]: And I assume it's a mess a Yeah.Kyle [00:10:54]: there's like I— like I think the reality is there's two pieces. Like first is I think that we're ending the era of these like massive, beautiful, perfect skills that are just like not any of those things. ‘cause for a while, right every tweet every day is like go download the skills, the perfectly managed thing to do this entire workflow. And I think that like what we've found and what— I was just with my team, this week, and we were talking about the skill side, and we're really talking about these like incredibly micro skills that are just doing one thing for us very well Versus a skill that's going to do I said, that full report. That doesn't really exist on our side anymore. It's usually how do— like a single skill that's going to identify the most important marketing information given any MCP server. Like this is the most important thing. Less about stitch a bunch of tools together and have it produce this mega output because then weeks go by, months go by, things change, and you want to tweakSwyx [00:11:58]: It's brittleKyle [00:11:58]: Your mega skill and you're screwed? You can't do that. And so now we're really just talking about the Legos we're using and just letting the instruction book be something we're all putting together. Whereas I think a lot of AI skills for a while have been that mega instruction book style.Swyx [00:12:15]: I've, thought a lot about Postel's law. I don't know if that's a term that is, means things to folks. It's the idea that you should be liberal in what you accept and strict in what you output, right? And I think that's like a good framing principle for skills. This is my skills, obviously on GitHub. I feel like everyone should have like how like some repos In GitHub are special repos? I feel like we should sort of reify the slash skills and everyone like give it some kind of special presentation. Anyway, so, yeah, this is one of those like download Download anything, transcribe anything, and then you can string together the atomic skills that do one thing well Into like some kind of orchestration skill that calls other skills. I assume, does that match?Kyle [00:12:56]: I like I think so. I think that theSwyx [00:13:00]: Summarize anything.Kyle [00:13:01]: Like I think the- For me, summarizing something for I do communications and PR and analyst relations and marketing and customer activities, and so my summarize everything is very different for each one of those like Contexts. What ‘Cause if I'm summarizing something for an analyst, that's a very different thing than, probably how I'm going to summarize something for like a customer meeting or an engagement. So that's I think like the difference when we're talking about the like the tools I might use on Saturday or the skills I might use on a Saturday when it's just for Kyle. Yeah, those are kind of like they have an atomic actual tool underneath or maybe skill, and then Kyle cares about X. But I think when we're talking about work and enabling the the marketers, communicators there, it's the atomic, this is what good summarization is, and then this is what I care about as for marketing for communications For whatever. And that I think is like the interesting matrix problem when we go from like a developer set of concerns to all kinds of different professions, is that what that word means to me is different than it means to you is different than it means to the analyst or the salesperson, and that's where I think the matrix mess is that we're starting to like still starting to find. It's about these mega skills but they're all just slight permutations, but those permutations are really important. It's the difference between someone reading this and going “Did AI make this?” what Or “This makes total sense, and I would expect this when I'm giving a briefing to Gartner,” or like whatever else.Swyx [00:14:37]: I think the beauty of it maybe is that you don't have to be that careful about what goes in there. It doesn't have to exactly fit as long as it like roughly is contained in there. I used to complain about plugin hell, basically. Like when you have a framework and then you have a hundred things that you need to integrate, everyone does like the GitHub used to be bloated full of these things. And now we don't need them anymore ‘cause now you just use skills.Former Developers in Leadership: AI as a Creation MultiplierKyle [00:15:00]: And like I think the most magical thing is the just that like I can just also crack it open. Like Like yes, I could go like change the how the plugin is coded, or like I could go do that now with AI, but I think there's just something more magical about getting a response back and being “That's not right,” and then you just crack the skill open, you just type English words and it's different. That building block is just, I think very unique. Once I get everyone to kind of understand how to best how to best make those changes to get the most power out of them.Swyx [00:15:36]: Is there a— you have a your peer group that Of people like you. Is there a common framing for Something I'm feeling is, which is true, is that is this a golden age for former developers who are now in leadership? Because you can wield the tools, you would know the right words, you're maybe not too close to the details. Doesn't matter. But like you're more effective than someone who doesn't come from that background.Kyle [00:15:59]: I think that like the secret has always been your ability to identify patterns and solve problems, and I think that for folks that like myself that don't code day to day anymore, that has made me successful as a developer, made me successful as a COO and now CMO. And so now that I have access to get and write code, I'm now applying that sort of like pattern finding and problem solving, and I know enough still about how to then go and say, “Oh, I want to make an app, but I don't want to break into jail or create something that's not going to be able to work or to be deployed scale or whatever.” that ability to apply all that additional business knowledge and still code I think is what makes that so interesting to me. Slightly different than I think some of the other like technical leaders that became business leaders and now are going back to their apps and updating them. Good for them? But I think the more, much more interesting thing is, well, now I have this whole new set of expertise over ten plus years. Why not take that and use that as a developer with these AI tools? So I definitely think that makes me more powerful, but I think that's true for like every dev as well. Most of the dev friends I still have also have some other underlying skill and passion. There's really talented, very kind of linear computer science software devs, absolutely. I just find that the folks that came from a different career, went to school for something else, went off and did this random thing, and then became a software dev, or were a dev, did a random thing, came back. Learning that extra set of information, learning those extra skills, and now having the power of an AI where I can crank up fifteen agents on Saturday while my kids are doing lacrosse, That's like really powerful. And I think it gets me back to that feeling of like creation, and it's very hard to replicate that in most other senses? That first time you build an app and you click it and you show someone that's magical. And so being able to do that not just in code, but across all kinds of different assets that's, that's huge. We were doing we're doing our every year we do our revenue planning. We talk about okay, what is it going to look like for next year? And of course as you imagine, there's, slideshows everywhere talking about what are we going to talk about, what's the narrative, et cetera. And so as you said I'm “Okay, well, I could probably just like build something to build this and then that way I don't have to go build the whole spreadsheet or I have to pass it to my team.” So we went through this process, and I got all the information and used the skills I mentioned. I built like a little app just to make it so I could look at some of the information in a SQLite database, more easily. And I ultimately built this entire presentation without touching any of it and I was “Okay, I'm just going to present this to our CRO, the CFO, their teams,” without mentioning I'd built it with AI. I like built a skill to make it look very much not AI driven. Just not pretty.AI-Generated Presentations, Human Taste, and the Changing Chief of Staff RoleSwyx [00:19:03]: Like a design. Yeah.Kyle [00:19:03]: Not pretty. But just like very clearly not AI. Kind of like don't do anything interesting.Swyx [00:19:08]: That's, yeah, that is valuable.Kyle [00:19:08]: Just go Exactly. We did the whole thing through. It used my notes from Obsidian, it used all the context I mentioned before, the plans, and Never came up once that it was AI generated.Swyx [00:19:20]: It didn't matter.Kyle [00:19:20]: Never once. D It didn't matter. And so now I takeSwyx [00:19:23]: This is a toolKyle [00:19:23]: I can take that tool and go, “Look, I don't want you to go build slideshows.” They're just helping us share information with each other. If this thing can do it With a little bit of crafting from you and then we can look at it together, awesome. There's no value in all that extra work. I think that the ability to, make it look humanly bad and and build a little app to, manipulate the data I think is part of, that upside for devs that are now in leadership roles. Because, the thing that I feel like I said before, this that's all a people, that's all a people problem. I know if you've used a coworker or not to build a slide deck, unless you spent a bunch of time to not do it.Swyx [00:20:07]: I know, but like it was so, I think there's a certain charm to just being blatantly AI. ‘Cause I think that you're well, you're just honest about There may be mistakes here that I cannot vouch for. So how much value is there? But anyway I think, actually the real question I want to ask is, there's a— You were a chief of staff To Thomas. And in the pre-AI world, the that job would've been a chief of staff job of like Can you prep me these slides and all that? And now you do it yourself.Kyle [00:20:35]: I still, I still have a chief of staff. Because, the difference is it's sort of the discussion every time we have some sort of technology evolution is it's not that the jobs the roles don't all go away, they just change? And so yeah, I don't have someone spending all their time building out slides for me and presentations ‘cause I don't need that anymore. But now I need that person that is able to go and find all the different connections between humans in those discussions to help me find out, okay, I should be meeting with this group and this team, and they have an opportunity, and I'm going to be in San Francisco today, I'm going to be in Seattle tomorrow. Those sorts of human connection aspects are still incredibly valuable and has always been a big part of that chief of staff role. But now just like chiefs of staff are not opening up, letters to process, they're doing emails. What It's the same thing. And now they're, they're not building out as many of these presentations because they have the the ability to have a AI take it on for, and share that with me and great. Let's keep moving ‘cause it's allowing us to go faster and make better decisions more quickly.Swyx [00:21:45]: Awesome. Well, so we can dive into more sort of, Productivity insights as you go. I did want to do a little bit of a brief history of colleague and hub. Because, we started here. And then you also involved the NPM acquisition. I did, I do want to touch upon that. And then more recently, I just want to bring up to present day where we're having uptime issues Which transparently we've already Addressed publicly, but we'll, we'll discuss in the pod. Did I miss anything? Like what, any other major highlights? Obviously, it's, it's a lot of years to cover.A Brief History of GitHub: Webhooks, Actions, Acquisitions, and Platform EvolutionKyle [00:22:15]: No the I think one of one highlight was right before the acquisition closed in twenty eighteen, I got to launch the first version of ActionsSwyx [00:22:27]: OhKyle [00:22:27]: At GitHub Universe. So it was OSwyx [00:22:29]: They're that young?Kyle [00:22:30]: It was October of twenty eighteen, I think. Yeah. Yeah.Swyx [00:22:33]: Gee, Jesus.Kyle [00:22:34]: I got to I was the engineering leader on that project and got to launch that. And then, yeah, we did acquisitions of NPM you said, Semmle, Dependabot Pul Panda a whole bunch of things. That was a bigSwyx [00:22:47]: Pul Panda.Kyle [00:22:48]: Abi is doing well.Swyx [00:22:51]: DX. Holy crap.Kyle [00:22:52]: Did well on DX. I and like that was a that was the big shift, after the acquisition. I had to join the sort of business side.Swyx [00:23:00]: So I need to hit you on some of these things ‘cause you were there. Right? And how often do I get to talk to someone who was there? But yeah, Actions. Is that the number one source of security issues on GitHub?Kyle [00:23:11]: Oh, sh I think that the number one source of, security issues is probably like all, the literal code in everyone's like underlying repositories. I would say back further than that is, if you remember I had to show in this graph was this is, I'm, didn't say this before, this is ultimately webhooks.Swyx [00:23:30]: You yeah.Kyle [00:23:31]: Like circa whatever it was.Swyx [00:23:32]: It says Hookshot in there.Kyle [00:23:32]: I forget. Yeah. Yeah, Hookshot's in there. And so like back then, it says GitHub Services. Do you see, it says Hookshot FE for front end, and then it says GitHub Services. GitHub Services back in the old days, right? You we had a repository that was Ruby code, and you could write any Ruby code in there, and then we would execute that On your behalf As a service, and then that way if an if you were trying to integrate with something, it didn't we would run it for you.Swyx [00:23:57]: And of course no containers ‘causeKyle [00:23:58]: No, ‘cause it wasSwyx [00:23:59]: Well, no containersKyle [00:24:00]: Twenty fourteen. And so there was some isolation obviously, but it was mostly the separations on the server level. That's like an example as long as the very old version of Pages, which ran on its own containerization infrastructure, not on Actions.Swyx [00:24:15]: Which like all-time great product.Kyle [00:24:16]: Pages powers the internet at this point to some degree. Those were places where like clearly there were no like issues like to my knowledge. But it was those things where I'm looking at and going “Okay, well we can't be running arbitrary Ruby code,” like on everyone's behalf. Then containerizing all of that up intoUh into actions now where yeah the containerization, is r-really good. The pinning most folks aren't pinning it the like to a particularSwyx [00:24:48]: ImagesKyle [00:24:48]: Sha, et cetera like their workflows, and so that's a big that's a big place Of pain for folks if they're just doing similar to any dependency management, just V1 or newest or latest, I think. But, that journey from that day to “Okay, we're just going to run all this arbitrary code, and, it'll basically be okay,” to now, no, we have, really good containerization. We have a new, underlying, ag-agent, containerization, service. It's like we're using it under the hood. It's through Azure. They recently announced it. The Azure, Dev Compute, but it's, very fast, very fast compute to be able to, spin up your own cloud agents, or whatnot. We're using it under the hood for some parts of the new,Swyx [00:25:36]: Microsoft Dev Box?Kyle [00:25:37]: No. Dev Compute, yeah.Swyx [00:25:41]: Hmm. Not finding it just yet.Kyle [00:25:44]: Oh, it's, it's in there somewhere.Swyx [00:25:46]: All right. Well, we'll cut that out.Kyle [00:25:47]: Sorry. But with, Dev Compute, you can, run, really fast, spin up really, small VMs really quickly, so you're doing a tool callSwyx [00:25:58]: Same conceptKyle [00:25:58]: Just do it containerize exact-exactly. So we're using that so definitely moving that direction to protect us from every every piece of code that we're ultimately running.Swyx [00:26:07]: look, that grows into the full SDLC? Code hosting was just the start and and then it's grown beyond that. Let's talk about NPM may-maybe ‘cause I think that's also, a very major point in the industry. I do think, it was looking for a home. It was, kind of struggling as a business, right? I don't know, I don't know how you would characterize that whole acquisition and how itNPM, Package Security, and Keeping the Internet RunningKyle [00:26:33]: like when we were talking to the team, I think the big thing for the both of us was to find a way to keep NPM, which was basically powering the internet then and way more so now to some degree running. Keep it going keep continuing to scale. It was having scaling problems, if I recall, back at that time. They were doing some rewrites. ItSwyx [00:27:00]: that's cute compared to now.Kyle [00:27:01]: Well, that's the thing is like when I'm talking to folks now, there's there's so many more underlying uses of NPM than there were back when we had them join in with GitHub. But that was ultimately the goal. It was really okay, we used to have pages. We have, the world's code. Let's make sure that we can keep NPM running well for the world. And we put a bunch of time and investment into fixing some of the underlying backend, changes, some of which we talked about some of the manifest work, et cetera. And then now, really trying to bring the the security posture of NPM up to speed. But, it is a unique challenge in that every move that we make to make it more secure will break a lot of people. And security is paramount. And also, we take it very seriously. We're, the any time that we have a problem with GitHub or we make a change that makes us more secure but hurts, there's, a snow day for developers or a really bad fire that they have to go put out. And so we've, have changed the 2FA policies. We've changed the way the tokens work. When we find tokens that have been exposed or potentially, exposed, we invalidate them, andSwyx [00:28:22]: I love that feature in GitHub. Yeah, it's greatKyle [00:28:23]: That creates issues, but, the but that's the thing is we're trying to push the community, forward without necessarily, doing something that is going to break the contract that's been for 15 years or close to it or some amount of years on NPM.Slop Forks, Vendoring, and the Future of Open Source Supply ChainsSwyx [00:28:43]: I think the— So now we're talking about, open source and publishing. And I think there's something here with what people are calling slop forks, which, I think Malta from Vercel is doing. And, part of me thinks, well, the way to get past any vulnerabilities, we just, let's just get rid of the concept of NPM. And we only publish source code. And anytime you want to import it you have your coding agent look at it and then adapt whatever subset you're going to use into your vendor it. But, the AI vendor it. Is that realistic? I don't know. Is it— Will that solve all our security issues? I don't know.Kyle [00:29:24]: I don't think it'll solve I so Mitchell was just talking Mitchell Hashimoto Was just talking about this today, and I think that I-in some ways, it's all all things, old or new again? Yeah, absolutely vendoring everything. Like I do I do remember twenty thirteen, twenty fourteen.Swyx [00:29:42]: This is Yeah. Let's, we must return toKyle [00:29:43]: That's what is We were vendoring everything. We were having actual discussions around, or at least I remember we were “Should we take this full thing?” “Why is this so big? We only need this one file.” And so I do think there's something true there where having either taking only what you need or the dependencies just getting incredibly small over time, I think will help to some degree, but it's not going to solve the fundamental problem, I don't think, because the vulnerabilities in an agent looking at them, there's time and time again, there's a million different ways in which we can convince an agent that this thing is, secure or not and pull it in. Or we can do static code analysis or runtime testing to say whether the code works or not. That is, I think, the step that needs to continue to be, invested in. The question is just on, how much scope. Should it be this enormous project that I'm pulling down, or should it be this piece? Either most companies are running some amount of security checking on the on the packages that they're bringing in or vendoring. That I think won't change. That's like what advanced security does to some degree, Socket does some degree. Like everyone is doing a piece of that. How we each do that like especially when we're talking to enterprise customers, is just like very different. No there's no one wants one single way to do it. And I think that's always been GitHub's, unique position in the world. I talk a lot to maintainers, I talk a lot to folks about this. It's we're— we rarely start like a process and a practice and like push it onto the community. We usually wait for the sort of like RFC process socially or literally, everyone agreeing, and then we'll cement something in. Because otherwise we'reMaintainers, RFCs, Vouching, and the Social Layer of TrustSwyx [00:31:35]: That fits your role in the ecosystem, yeahKyle [00:31:36]: We're GitHub. Yeah, we don't want to shape the whole thing. We want it to be figured out. But like how do you balance that like sort of Role in the industry to keep everything as secure as is possible and make sure that you're you're not going to be compromised as a human, ‘cause that's usually how it all happens. And Not not create a process or lock us into a flow that you're not going to or like Mitchell's not going to or other open source projects aren't going to like. That's always been a tricky balance for us, and I think that's something that we haven't talked about enough is we're not going to be able to fix everything for everyone in a way that everyone is going to like. So tell, help us, tell us what is working. When Mitchell was talking about, the Upvote, the upSwyx [00:32:22]: I was going to bring up his thing. Yeah.Kyle [00:32:23]: I forget what it Yeah. When he's talking to us, I was chatting with him and talking to him about this and I put it on Twitter and we talked to, also over DM, was “We're going to keep working.” but I think the important thing is I do actually want to hear what isn't working for you. And as, be as specific and clear for your project as is possible. And to every piece of credit over the many years that we've known each other through the industry, he's always done that and I appreciate that ‘cause there are places that we need to fix up, and we hear from him, and we'll fix up just like we do all other kinds of maintainers. But that that process between making those types of improvements and being more secure and like creating, I forget what he calls it's not the proof process, not the claims process. Do what I'm talking about? He has that he his projects have a way for you to kind of like,Swyx [00:33:13]: VouchKyle [00:33:13]: Vouch. Thank you. Yeah. He has like the vouch system for saying, “Hey, you should accept my PRs.” That's beenSwyx [00:33:20]: I just built this into GitHub. I don't know.Kyle [00:33:22]: Well, see, but that's the thing is that you say that and like he and his community really likes this and then I'll go talk to other maintainers and other maintainers, globally, and they're “No, this doesn't work for me.” And that is the tension, but also the kind of beauty of GitHub, depending on which way you look at it is we want to help maintainers, so we create all these tools to let you have more control over how much you take in from AI and PRs. But you can also use this. What You can go use this project, and if it takes off and becomes the kind of mostly standard, then yeah, we probably wouldn't enforce it but we would add it in because that's the flow that we tend to do?Swyx [00:34:02]: I hear a lot of people don't know the history of the pull request. And like like that's how, that's something that GitHub standardized basically.Kyle [00:34:08]: Yeah. It was a very messy process Like beforehand, and now the we have the benefit of it being the process? And now we have to go and Figure out the next best process or what adaptations change, or what does a pull request look like when eighty percent of your PRs are just coming from your agents and not From other devs?Swyx [00:34:31]: Do you like the prompt request idea from Peter?Kyle [00:34:34]: like I think that for each like each idea I think has its merits. I'm not, I'm not avoiding saying anything good or bad, but I feel like I've seen a version of we have that we have entire Thomas' store. Take all the assets of what you've built and put that in. I think that's got great ideas. There's all these various permutations of the PR flow, but I think the reason why there's not a single answer is ultimately we're trying to codify trust. We're trying to say “Okay, if Sean reviews this I'm going to trust it because you're Sean or you're the senior dev or you're the whatever.” And right now, when we are working in a flow where an agent writes code and another agent reviews code and then Kyle goes and looks at it the trust is kind of diffuse. And most of the tools that we're talking about are talking more about verification flows. We have more assets to look at, so I can probably say whether this is a good PR or not. But that still doesn't solve, I think, the human problem of I'm looking at a PR and I want to know if I can trust it. And we're still, we still tend to use human signals for that? Mitchell approving it or Kyle approving it or whatever. And so I think that's, I think that's why most of these options haven't really solved it is because, it's a social problem ultimately. It's a it's a human problem to review it and agree. Or you fully trust the tool and you're imbuing that tool with full trust Which I think in some cases that absolutely exists.AI-Generated PRs, Trust, and the Waymo AnalogySwyx [00:36:08]: And so like in the same way that there will be a tipping point in society when we don't allow humans to drive anymore Because machines are measurably better than Than humans. I'm looking for that tipping point, right? Like Mythos is ridiculously expensive. Someday we'll have Mythos on a desktop. I don't know. Will, does that change the equation?Kyle [00:36:30]: I think it's more I took a Waymo here, and I was on my phone and not looking around at all. There are other, self-driving, vehicles that I would not trust while, staring at the road. And I think that trust is something that isSwyx [00:36:48]: Is this a Zoox thing? What is itKyle [00:36:50]: I think that is both. I think that is both. LikeSwyx [00:36:53]: There's Zoox in this robo taxi. That's it. It'sKyle [00:36:56]: Well, depending on what level Of self-driving. But, my point is sort of that I think part of that is I strongly believe that's, a mixture of verifiable proof. Like how many accidents, how much data, and so on, and the human aspect of how I feel when I'm in this car, what it tells me, et cetera. And so that's why I think some of the like Some of these some of our AI tools tend to, imbue me with more of that feeling of trust, even if the data says this is 100% accurate. I feel like it takes more time for us to go, “Should I trust this or not?” And that's in the soft sense of, startups with high agency, weekend projects, and open source. And then there's enterprises and regulated industries and everything else, and that is an even harder problem to go solve because even when it is fully verified, not only do you have to have trust from the humans on the team, you probably have to have trust from multinational,Swyx [00:37:55]: Oh my GodKyle [00:37:55]: Multi governments around the world and regulating agencies. And so that's where I feel like until we tip over to your point on the sort of like human EQ side of it. I feel okay this feels okay I've been proven enough. Then the ball will start to roll a lot faster, where we'll end up getting to the “Okay, we can trust this,” and feel good about it in the Most difficult of cases.Reputation, Sponsors, Stars, and Bot Activity on GitHubSwyx [00:38:18]: If human trust is the thing that matters, I feel like GitHub as the developer social network could maybe do more there. Like vouchers are one system But, we have star counts, and then we have Contributor rights, and that's it. And I feel like there should be more in that space. I don't know if there's any other design decisions there.Kyle [00:38:37]: I think that one of the places that we don't really expose right now in this sort of way is, some degree of like hard trust and support, which would like for me is like sponsors is a good example of that.Swyx [00:38:49]: Ah.Kyle [00:38:49]: It like costs you something. To prove that I believe in your project and I trust you To some degree or I want to support you at the very least.Swyx [00:38:56]: Solve payments for open source. Why not?Kyle [00:38:58]: I think that I think that like as we keep moving forward, right, there's more and more projects where I'm, adding more and more dollars into sponsors personally because I want to like support them, but I also like know of I've probably never met them in person, but, I know of enough of their work that I want to support them. I think the thing that I don't love about stars or commit counts or anything else is ultimately, even with all of the various, abuse and de-spamming and deduplication work that we do or anti-abuse work that we do, these are all, not active social signals. They're passive ones that are ultimately gamifiable. And you may trust me, but another open source maintainer may not. And on what heuristic should you be, trusting me? That I think, is kind of where some of our thinking is right now. What signal from me is most important to you? You— If you can define that potentially, honestly in an agentic workflow that's what we see some of these open source projects do, where you have GitHub actions, and then you have like an agentic workflow that's calling AI, and you're setting these rules. Like if Kyle has submitted and gotten accepted PRs across any given project and has a social handle tied to his account in GitHub, and that social account's older than a certain amount. Really complex measures that matter to you ‘cause most open source projects have that heuristic built into their heads, if not written down in the contributing guidelines. You could take that and then go apply that and then just say, “Oh, we're not going to accept this PR.” Building something that is, I think, malleable to everyone's needs, is a little bit better, rather than going “Hmm, this account's too young.” Because what happens? The attackers just go and go and create a multitude of accounts, and they wait Until it ages up. Needs to have a certain amount of stars. That's how star inflation happens. Need to have a certain amount of reposSwyx [00:40:46]: Oh my God. YeahKyle [00:40:47]: With PRs. They all just create repos and submit PRs to each other, and then they come in and do something nefarious. And so, it's hard. It's hard to find the measure. So I think we're, we're looking more at how can we provide you tools so you can kind of choose what's best for you. And of course, we'll give you some standards. But the trust vector, gets down to I don't know, some version of like human digital ID like everyone's been talking about. Like how do I prove that it's meSwyx [00:41:13]: Give me your eyeballsKyle [00:41:14]: On the internet. Give me your eyeballs. Exactly.Swyx [00:41:18]: The I got to keep moving on Topics, but obviously I can go all day on this stuff because, I've been involved in GitHub and open source My entire professional career. Stars. Very superficial. Everyone knows it. But I think time to one hundred thousand stars is the fastest I've ever seen. Like people just reached that in I don't know, months. And then like at the same time I don't trust it right? Like how many of these are real or bot or like whatever. I don't know how to ask this but like what can we do about it? LikeKyle [00:41:49]: JustSwyx [00:41:49]: Is stars broken? Is stars fine?Kyle [00:41:51]: I think that there's kind of two, there's like two pieces. Obviously we're constantly like trying to find ways in which like your users are producing spam, which would, I would include like be like only doing star gamification. When we find them, we pluck ‘em out and we,Swyx [00:42:08]: But it's like a Whac-A-MoleKyle [00:42:10]: It's a hundred percent like a Whac-A-MoleSwyx [00:42:11]: There's no wayKyle [00:42:11]: Now, powered by AI to be helpful. But I think more so what I'm seeing is, a lot of the like fastest time to X tends to be because we're now inviting so many more people into like software development on GitHub That like the zeitgeist is just swarming? And it'sSwyx [00:42:32]: It's not just developers anymoreKyle [00:42:33]: And it's not you and I. Like like however you want to say like what a developer is it's not just folks who have been coding for a very long time. It's folks that have maybe started coding or only joined in since the AI era. And nowSwyx [00:42:44]: what's the latest Octoverse number? I know eighty million was my lastRem- member that a number of developers on GitHubKyle [00:42:50]: Oh, we're over 200 million now.Swyx [00:42:53]: Okay. Well, so you see?Kyle [00:42:55]: Like over 200 million developers now.Swyx [00:42:56]: But it's not developers, right? It's, it's people with a GitHub account.What Counts as a Developer in the AI Era?Kyle [00:43:00]: So, so this is, this is the biggest debate that I would say, everyone loves to have at GitHub at this point. From my perspective, right, I think that there's, there's clearly a difference between, professional enterprise developer and then developers. But I think that I think that the idea that we should be I don't know, splitting hairs or segmenting developers in the early era of software development is, not worth our not worth the time. SoSwyx [00:43:29]: When you get into gatekeepingKyle [00:43:31]: 100%Swyx [00:43:31]: What is a developer?Kyle [00:43:31]: 100%. ‘Cause I wasn't a developer when I started writing code? I was going toSwyx [00:43:36]: Oh, no. I made— I cloned a thing, seven years before I learned to code. And then I and then I wrote about my learning to code journey, and people Just called me a fraud ‘cause I had a GitHub account. And I'm “Well, no, I just use GitHub, but I don't know-” “I didn't know what I was doing.”Kyle [00:43:49]: I I remember that. I remember those sets of posts, and like that's, that's b******t. So I fight very clearly on the line of, if you create code, if you have an idea and you create it into some way of, I'm, I'm going to run it and use the app right now, you may still use AI in that moment, but that's okay. At some point you're going to do the next thing. You're going to create a big— You're going to have to learn about this database. You're going to fix a bug, whatever. We're all on some same journey, and those people are also hearing about the great new agent skill package or a new CLI tool or a new whatever. And those projects are going up because you want to be a part of this moment, just like I wanted to be a part of the Ruby community when Ruby was popping off when I started becoming a developer, and now I can just click the star button. And so I think that yes, there's clearly some amount of like spamming and game gamification that we're working against, but I really think we're just seeing this whole new cohort of folks that are moving from technology to technology because they're not working on a 20-year-old software application. They're working on a side app that they built on the weekend for their friends or for their new idea or whatever. And that's how you see these enormous charts going up and to the right with With stars.Swyx [00:44:59]: I think something that's remarkable is the persistence or, that GitHub extends to those folks. Usually when I see platforms go into a new audience, they usually have to, have like a second platform with a different name that wraps the main platform. But somehow GitHub has been able to sort of persist and extend, and it's friendly and whatever? So it's, it's nice.Spark, Low-Code, and Always Showing the CodeKyle [00:45:19]: I that's partially why I think as we've tried to move into I don't know, more like low-code-y things. We so we started working on Spark as like a way to, build an app and run it. I think that the reality is that we anytime we try to, kind of put even a veneer on top of it without when we put a veneer on top of something, we still always show you the code. That's kind of like a tenant. We're never going to, hide the code from you ever, because whatSwyx [00:45:52]: Why would you?Kyle [00:45:52]: That's, yeah, that's the whole point? However, I think that what we learned with things like Spark is that really the value of Spark for most devs is, easy runtime. And you may have a runtime or a host that you're going to use for that or you just build something and run it but, the package of making that even more simple isn't really needed for folks that are trying to build software and not just trying to build, an app, which is, slightly different, a slightly different goal. So I want to get you in, I want to get you comfortable. I think the best thing for me as, someone that did not traditionally come into software dev way back, I want anyone to be able to breach that chasm and not be in the I don't know, I feel like we're, we're still in an era of, STEM. I've got a 12-year-old and an eight-year-old, and it's “We got to get ‘em into STEM,”? Over and over. And I like I do, I do the things that good parents do. I was “Oh, you want to do coding?” “Yes, I want to do coding.” Do coding classes. But now they're just not afraid of doing software. And that's, I think, the thing that's honestly kept me at GitHub for so long. Anyone should be able to go and build a thing, just like I can go change a light switch in my house. I'm not going to go into the breaker box ‘cause I'll probably kill myself? But, I can go change that light switch. Everyone should be able to go and say, “This fricking app doesn't do what I want. I want it to work like this.” And that I think, is what's kind of kept us all connected with GitHub through the years and some and during the easiest of times or in the hard times because of that opportunity of, we're the home for all developers, and we want everyone to be able to have that feeling that we've had of, had an idea, I created it and holy s**t here it is.Swyx [00:47:37]: Here it is. All right, I'm going to try to do more spicy questions.GitHub's Hardest Scaling Moment: Growth, Agents, and UptimeKyle [00:47:42]: Great.Swyx [00:47:42]: Is it an easy time now or a hard time?Kyle [00:47:45]: Oh at GitHub? It's a hard time. Like, it's a hard time and also, I was just with my team and I said, “This is also, the best and most exciting time that I think I can remember at GitHub.” BecauseSwyx [00:47:57]: Best of times, worst of times. It's never oneKyle [00:47:59]: ‘cause we've we were talking about Octoverse reports and, usually we do an Octoverse report once a year, and we look at the numbers, and we say, “Oh my goodness.” I was at Universe in October saying, “This was the fastest year of growth that we've ever had,” right? And now we're doing more in a month than we did in a year last year.Swyx [00:48:20]: You're talking about PRs.Kyle [00:48:21]: Commits.Swyx [00:48:21]: Commits, yeah.Kyle [00:48:22]: PRs. Kind of like you name it by roughly every measure that we're looking at, there's some amount of sort of growth that is much bigger, and that is breaking our system in new ways, not old ways. Like webhooks were always notoriously, unreliable over the years?Swyx [00:48:38]: Whose fault is that?Kyle [00:48:39]: not anymore mine, but for a period of time, I'm sure you could pull up a tweet that was “It was me. I'm sorry.” but, now, that got rewritten at a scale level that is still working and is not having problems today. Now what we're finding isn't just the isn't the-The simple stuff that folks are on the sometimes on Twitter or on the internet are “Hey, why is this like this?” Sure. There's absolutely silly problems that we shouldn't exist. But now we're talking about, unique, novel permission problems that happen only at a scale across all different objects or whatever, that now we have to go rewrite this underlying system. And so it's, there are problems that yeah, caught us off guard, which I think I said. Like the growth is astronomical, but also we're making such material progress in that I'm excited once we're once we've kind of like reimagined the underlying foundation layer, or pieces of it at least, what's going to be possible when it's not just all of us and all the new people that are being developers and all of their agents and all the tools like working together. Because that'll still happen in that in that GitHub tool, that GitHub community. But it's a it's a hard day anytime we can't give you what you're looking for. We have the same problem internally. We operate through github. Com. Of course, we have backups when things go down and whatnot for our own operations but we feel it too. If it's not working it's not working for us, and that's kind of like the promise of dogfooding for GitHub. It's always been true. We're using the same tool you're using. We're not using a super secret version. We and so we also need it to be great for us for our customers of course for open source. And now an exponential growth of agents, Doing it too.Swyx [00:50:32]: I wanted to load for audio listeners who maybe haven't seen your tweets, whatever. So one billion commits in twenty-five. Now it's two hundred and seventy-five million per week on pace for fourteen billion this year, if growth remains linear. Is that still the pace? I don't know. It's been aKyle [00:50:48]: it's, it's speedingSwyx [00:50:50]: Roughly.Kyle [00:50:50]: It's still speeding up.Swyx [00:50:51]: It's, it's April, so yeah.Kyle [00:50:51]: Exactly. This was in April.Swyx [00:50:53]: All right. So basically you have fourteen x growth, right? Year on year on year. And I think that's a scaling issue. I think, I'm going to like try to really steel man this thing. People have experienced fourteen x growth. They haven't had your downtime. And that's like— C-can we go dig into that? Why? Like what's the— what broke? What are we doing to fix it? Like just anything for the community to reassure them.Why GitHub Reliability Is Breaking in New WaysKyle [00:51:18]: so there's a Like I was saying, there's a couple different places that we've seen the growth issues. Some of the growth issues, which is why we're t— I was talking about pushing hard on more CPUs is in actions in particular. More tools, more agents, more PRs mean more builds, more builds mean more CPUs. And so we are expanding through not just our data center, but obviously we were talking about moving to Azure and moving to, adding an additional cloud compute because we simply need more CPUs. Not as much GPUs. We definitely need GPUs too, but now CPUs are becoming a factor.Swyx [00:51:53]: It's very CPU heavy.Kyle [00:51:54]: Underneath the hood when it comes to some of the underlying services, we've been breaking up over the years our database infrastructure, so that way we have, more cognitive separation between our the various services. The place that we continue to have pain is in, permissioning. And so right now m-many of our permissioning layers sit into a database that we like internally call MySQL One, and old Hubbers will know what I'm talking about. And so we've been pulling things out of MySQL One for many years, because like and we use we use Vitess and we use other technologies to shard and we do it as one bigSwyx [00:52:31]: Famous thing, PlanetScale was born from this andKyle [00:52:32]: A hundred percent. Sam Old Hubber and friend. And so finding these opportunities to like break this out and then do that globally. The other thing that I think is interesting and both a unique opportunity and tricky is we also run everything I just talked about in a black box container with GitHub Enterprise Server for people that work on-prem. So we take everything I just said, and we also do it on-prem, and we also do all of that and we do it in a data residence setup for customers that need to have their data in a single location. Each of these has the unique characteristic around how we're sort of storing that data in MySQL or in a permissioning setup. That's where some of these outages have oc-occurred, where you're seeing it more like across the board rather than just like the one pieceSwyx [00:53:17]: Filling the databaseKyle [00:53:17]: Isn't quite working. Exactly. And so part of it is that. I think there's been some other places where agents are much more or more projects appear to be moving towards monorepo versus we were going the other direction for many years in the industry. Repos were smaller, but there were more of them, and now we're seeing the opposite. Repos are bigger, and there's, not fewer of them per se ‘cause there's new growth, but, we're just seeing many more big repos. Big repos, big monorepos have always had, a unique performance problem. Because each one, is slightly different if, particularly if the underlying blobs are incredibly big Inside the repos. And so we've done a ton of work that you pro— like most people haven't probably experienced, unless you're in this case of the monorepo. But that Git, infrastructure layer improvement does help the overall, system because, many of the improvements that make monorepos work better make all repo infrastructure work better. And so, I could kind of keep going down the line where it's another thing where we're moving out of, We're changing how we do j I'll just say job queuing for lack of a better, explanation changing the underlying technologies there.Swyx [00:54:32]: I spent two years being a job queuing guy, so.Kyle [00:54:34]: And so it's kind of a little bit of a little bit of piece by piece, and it's mostly because as we were— as it was built, we built everything in a way that assumed, I guess in some ways that the size of the pipe of work was going to remain the same. There's just going to be more people coming through each of those pipes. But instead now in places whereA git push was, generally a certain size for example, is now, no longer true.Swyx [00:55:03]: Oh, yeah.Kyle [00:55:03]: OrSwyx [00:55:05]: I push a thousandKyle [00:55:06]: On the average. 100%Swyx [00:55:06]: A thousand line commits like dailyKyle [00:55:07]: Same thing with PRs. Like PRs same thing. And like we've talked about optimizing that and making changes where, and there were technology choices that did not work there? And it got slow, and it didn't It was not fast. It did not do what the users wanted. And so we've been reeling that all out and going “Okay, that's just not right. Let's stop putting good money after bad and do it the do it the right way or the right way now.” So there's It's a it's a lot of things, not quite when I've experienced scale at GitHub historically, it's almost always two options that we've used. We go vertical scaling, particularly with databases, right? And we go horizontal scaling. Oh, we just have more people using this service. Great. We're going to add more servers, and we rack them in our data center, or we use it in a cloud. And now we're sort of in a like diagonal, where like vertical doesn't really work anymore. Horizontal isn't work either because we're all We all have some CPU or GPU constraints in the world now, and now we have to go in and like crack open services that have been running for 10 or 15 years and go, “Okay, the rules of this service have legitimately changed, and now we have to rewrite them.” None of this is an excuse. This is like we're We have to do the work. We have to make it better.Swyx [00:56:22]: actually as an infra guy, I'm “This is like one of the most fascinating scaling challenges I've ever seen.”Kyle [00:56:26]: That's that's, that's the thing that's the thing that it's hard for Like when we weren't talking about it publicly, and I was like I came out, and I was “Hey, I just want to explain what's going on.” Part of it comes from a very old GitHub ethos, which is it's our it's our uptime. It's down. W What I know you're a developer, so you're, you're inclined to want to understand more what's going on. But at the same time us going “Hey, this service didn't, perform the way we expected, and now we have to go change it,” we weren't We're not trying to hide anything from you i

Discover how Voice Claw Real Time transforms AI accessibility by connecting voice commands to Open Claw, enabling hands-free, intelligent computer use for everyday tasks and people with disabilities. Steven Scott and Shaun Preece welcome developer Ben Badejo to explore Voice Claw Real Time, his new voice interface for Open Claw. This system allows AI models to take direct action on computers and mobile devices, not just respond in chat. Ben explains how Open Claw can read emails, manage calendars, browse the web, and even complete booking forms, all triggered by speech. The conversation dives deep into accessibility: Voice Claw Real Time integrates with iOS voice control and Apple Watch, giving users with visual or motor impairments a powerful way to interact with AI. From setting up read-only email access for safety to leveraging Codex for intelligent computer use, Ben highlights how thoughtful system design and natural language configuration can raise the floor for inclusive technology. ----Follow on:YouTube: https://www.doubletaponair.com/youtubeX (formerly Twitter): https://www.doubletaponair.com/xInstagram: https://www.doubletaponair.com/instagramTikTok: https://www.doubletaponair.com/tiktokThreads: https://www.doubletaponair.com/threadsFacebook: https://www.doubletaponair.com/facebookLinkedIn: https://www.doubletaponair.com/linkedinSubscribe to the Podcast:Apple: https://www.doubletaponair.com/appleSpotify: https://www.doubletaponair.com/spotifyRSS: https://www.doubletaponair.com/podcastiHeadRadio: https://www.doubletaponair.com/iheartAbout Double TapHosted by the insightful duo, Steven Scott and Shaun Preece, Double Tap is a treasure trove of information for anyone who's blind or partially sighted and has a passion for tech. Steven and Shaun not only demystify tech, but they also regularly feature interviews and welcome guests from the community, fostering an interactive and engaging environment. Tune in every day of the week, and you'll discover how technology can seamlessly integrate into your life, enhancing daily tasks and experiences, even if your sight is limited."Double Tap" is a registered trademark of Double Tap Productions Inc. Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

HOUR 4: Why can they claw back from 30 years ago, but we can only review the last three years? full 2050 Thu, 28 May 2026 22:00:00 +0000 vp7zpjZnFYubAxgtobeEQ6dd6oRcb23C news The Dana & Parks Podcast news HOUR 4: Why can they claw back from 30 years ago, but we can only review the last three years? You wanted it... Now here it is! Listen to each hour of the Dana & Parks Show whenever and wherever you want! © 2025 Audacy, Inc. News

It's Marvel Monday and we're heading to Wakanda! ABOUT BLACK PANTHER T'Challa, heir to the hidden but advanced kingdom of Wakanda, must step forward to lead his people into a new future and must confront a challenger from his country's past. AIR DATE & NETWORK FOR BLACK PANTHER February 16, 2018 | Theatrical Release CAST & CREW OF BLACK PANTHER Director: Ryan Coogler Writers: Ryan Coogler, Joe Robert Cole, Stan Lee Cast: Chadwick Boseman as T'Challa/Black Panther Michael B. Jordan as Erik Killmonger BRAN'S MOVIE SYNOPSIS IT's time for a little history lesson, ok? So, a massive meteorite made of vibranium crashed into Africa Five tribes go to war over it until one warrior consumes a mysterious heart-shaped herb altered by the vibranium and gains incredible abilities, becoming the first Black Panther.  He unites the tribes and establishes the hidden nation of Wakanda. Over generations, Wakanda becomes the most technologically advanced civilization on Earth while hiding in plain sight. In 1992, King T'Chaka visits his younger brother, N'Jobu in California, where he has been working undercover. T'Chaka discovers that he has secretly helped a black-market arms dealer steal vibranium from Wakanda. When confronted, he turns violent, forcing T'Chaka to kill him. To protect Wakanda's secrets, T'Chaka abandons N'Jobu's young son in America and covers up the truth. Got it? Good. Years later, the King is killed and Prince T'Challa returns home to be crowned king of Wakanda. During the event, M'Baku of the Jabari Tribe challenges T'Challa for the throne in ritual combat. T'Challa wins but spares M'Baku's life. I'm sure that's for no reason though. Soon after, this dude name Claw shows up in London and steals an artifact from Wakanda at a Museum. Oh and some dude named Erik Stevens is with him. T'Challa goes to this party to try to capture Klaw but it doesn't go well and leads to a massive chase through the city. This dude that works for the government named Ross ends up being quite hurt, so T'Challa ends up rescuing him and bringing him to Wakanda to heal him with their neat tech. Zuri tells T'Challa some juicy info about how they left this kid in Oakland with no father and that kid grew up to be Erik Stevens and he now goes by Killmonger cuz of how many people he's killed and he's probably coming for us so hide your kids, hide your wife.  Killmonger murders Claw and delivers his body to Wakanda, earning an audience before the tribal elders. Revealing himself as son of N'Jobu and wants to challenge for the throne. T'Challa agrees and loses and is thrown off a waterfall cliff.  He is now the king.  Killmonger prepares to send vibranium weapons to operatives around the world to begin a global revolution. T'Challa's family leaves to asks M'Baku for help. Turns out, he has T'Challa on ice b ut in a good way. They use the heart-shaped herb to bring him back and restore his powers.  T'Challa returns to Wakanda for a final battle. T'Challa and Killmonger have a creazy fight and T'Challa is able to disable Killmonger suit. T'Challa offers Killmonger a change to live but he choses death instead, but T'Challa lets him watch one last sunset.  T'Challa decides Wakanda can no longer hide from the world. He opens an outreach center in Oakland at the very place where N'Jobu died. T'Challa then appears before the United Nations and reveals Wakanda's true technological power to the world.  And then to connect it all to the Avengers, his sister Shuri helps Bucky Barnes continue his recovery in Wakanda. Watch the show on Youtube - www.deckthehallmark.com/youtubeInterested in advertising on the show? Email bran@deckthehallmark.com Hosted by Simplecast, an AdsWizz company. See pcm.adswizz.com for information about our collection and use of personal data for advertising.

Adventure_of_the_Wooden_Claw

Your horrible reaction to beef could be from a tick-bite. In this episode, you'll learn about Alpha-gal Syndrome, which could be the reason you can't stomach red meat, and why it's all to do with tick saliva. If you have Lyme disease, you may already understand how ticks can wreak havoc with your immune system. Here, Dr. Motley shares his thoughts on why allergic reactions to beef may be on the rise, and the treatments he's seen manage symptoms most effectively, including herbs, homeopathy and ear acupuncture (and the SAAT technique that shows proven, long-lasting results).  If you have a tick-borne illness or an unexplained allergic reaction to beef, this episode offers a hopeful path forward.    Chapters 00:00 - What is Alpha-gal syndrome 11:11 - Why older generations eat meat more easily 12:07 - Why Alpha-gal may be so common 16:01 - Treatments, Auricular therapy 17:48 - Patient case studies 20:48 - Homeopathy treatments 21:33 - Other treatments 22:12 - Herbal remedies 24:54 - Recap and closing thoughts Dr. Motley's recommendations: Soliman Auricular Allergy Treatment Arsenicum Album Natrum Carbonicum Carbo Vegetabilis Nux Vomica Stinging Nettle Quercetin D-Hist: https://shorturl.at/6UQBa Japanese Knotweed: https://tinyurl.com/56r8fukp Cat's Claw: https://shorturl.at/eT7Zm Houttuynia Supreme: https://shorturl.at/gJifj ------  Want more of The Ancient Health Podcast? Subscribe to the YouTube channel. Follow Dr. Motley! Instagram Twitter Facebook Tik-Tok Website ------  * Liposomal supplementation has been proven deeply effective and LivOn Labs got there first. Get 10% off LivOn Labs entire store of liposomal supplements with code MOTLEY at https://www.livonlabs.com/ *Join Doctor Motley's newsletter for TCM insights and regular podcast updates: https://www.doctormotley.com/*If you want to hear more of Dr. Motley's education on Lyme,, check out his membership, complete with courses, a whole library of video-based resources and the chance to pick his brain on weekly live Q+A's. You can try it free for 15 days here: https://www.doctormotley.com/15

Genspark went from AI search startup to autonomous AI agent platform, hitting $250M ARR in 12 months with no paid ads until they bought a Super Bowl spot. Co-founder and COO Wen Sang joins Corey and Grant to explain what "AI employee" actually means, demos Genspark Claw live (including buying us coffee mid-interview), and lays out his big thesis: legacy software is becoming infrastructure while AI agents become the new interface between humans and work. We get hands-on with Workspace 4.0, Claw, and a custom agent built live for the show.• Genspark Workspace 4.0 announcement: https://www.genspark.ai/blog/genspark-ai-workspace-4• Genspark sb-git: https://genspark.ai/sb-git/intro• OpenAI's customer story on Genspark: https://openai.com/index/genspark/• Forbes AI 50 (2026): https://www.forbes.com/lists/ai50/• Marc Benioff on Salesforce Headless 360 (referenced by Wen): https://x.com/Benioff • Andrej Karpathy's "wiki for agents" idea (referenced as inspiration for sb-git): https://x.com/karpathy• Wen on the DealMaker Show: https://alejandrocremades.com/wen-sang/Try Genspark for free: https://genspark.aiSubscribe to The Neuron newsletter: https://theneuron.ai

Get started building your tiny AI Agent business with Genspark Claw: https://startup-ideas-pod.link/genspark_ In this solo episode, I share seven tiny, cash-flowing startup ideas you can build with AI in just a few prompts. I walk through how to use Genspark Claw, Genspark's new in-the-cloud agent product running Sonnet 4.6, and demonstrate two ideas I have already built (a dead domain flipper and a local restaurant liquidation broker), build a third idea live on camera (a hiring-signal cold outreach machine), and hand you a five-step framework for generating your own ideas. The goal is simple: give you the creative juices, the framework, and the practical know-how to ship a $200-$1,500/day business with AI as your employee. Timestamps 00:00 – Intro 01:28 – Idea 1: The Dead Domain Flipper 06:19 – Idea 2: Local Restaurant Liquidation Broker 11:03 – Idea 3: Hiring-Signal Cold Outreach Machine (building live) 14:30 – Prevent Sleep, Heartbeat, and Treating Genspark Claw Like an Employee 15:52 – Skills, Local File Access, and What Else Genspark Claw Can Do 17:24 – Reviewing the 14 Personalized Cold Emails It Wrote 20:35 – More Ideas: Buy-or-Build Memos, Dead Product Hunt SEO, Forgotten Apps 24:18 – Framework for finding ideas: Public Data, Neglected Assets, Clear Buyer 26:33 – What Else Comes With Genspark AI Works Base 4.0 Key Points Tiny, boring, cash-flowing ideas beat billion-dollar ideas when you want to ship this month. GenClaw plus Slack turns Claude Sonnet 4.6 into an always-on AI employee for around $25/month. The repeatable pattern is: messy feed → mispriced asset → trigger event → obvious buyer → liquidity point. Three hunting lenses: places of constant change, things people ignore, and assets with clear urgency and spread. Talking to your agent in plain English ("strip the HTML entities, make the budget $2,500") replaces most engineering work. Selling agents with outcomes is the new SaaS, and shifts the model from per-seat pricing to outcome-based pricing. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ #Genspark and #WorkWithGenspark FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/

Get started building your tiny AI Agent business with Genspark Claw: https://startup-ideas-pod.link/genspark_ In this solo episode, I share seven tiny, cash-flowing startup ideas you can build with AI in just a few prompts. I walk through how to use Genspark Claw, Genspark's new in-the-cloud agent product running Sonnet 4.6, and demonstrate two ideas I have already built (a dead domain flipper and a local restaurant liquidation broker), build a third idea live on camera (a hiring-signal cold outreach machine), and hand you a five-step framework for generating your own ideas. The goal is simple: give you the creative juices, the framework, and the practical know-how to ship a $200-$1,500/day business with AI as your employee. Timestamps 00:00 – Intro 01:28 – Idea 1: The Dead Domain Flipper 06:19 – Idea 2: Local Restaurant Liquidation Broker 11:03 – Idea 3: Hiring-Signal Cold Outreach Machine (building live) 14:30 – Prevent Sleep, Heartbeat, and Treating Genspark Claw Like an Employee 15:52 – Skills, Local File Access, and What Else Genspark Claw Can Do 17:24 – Reviewing the 14 Personalized Cold Emails It Wrote 20:35 – More Ideas: Buy-or-Build Memos, Dead Product Hunt SEO, Forgotten Apps 24:18 – Framework for finding ideas: Public Data, Neglected Assets, Clear Buyer 26:33 – What Else Comes With Genspark AI Works Base 4.0 Key Points Tiny, boring, cash-flowing ideas beat billion-dollar ideas when you want to ship this month. GenClaw plus Slack turns Claude Sonnet 4.6 into an always-on AI employee for around $25/month. The repeatable pattern is: messy feed → mispriced asset → trigger event → obvious buyer → liquidity point. Three hunting lenses: places of constant change, things people ignore, and assets with clear urgency and spread. Talking to your agent in plain English ("strip the HTML entities, make the budget $2,500") replaces most engineering work. Selling agents with outcomes is the new SaaS, and shifts the model from per-seat pricing to outcome-based pricing. The #1 tool to find startup ideas/trends - https://www.ideabrowser.com LCA helps Fortune 500s and fast-growing startups build their future - from Warner Music to Fortnite to Dropbox. We turn 'what if' into reality with AI, apps, and next-gen products https://latecheckout.agency/ The Vibe Marketer - Resources for people into vibe marketing/marketing with AI: https://www.thevibemarketer.com/ #Genspark and #WorkWithGenspark FIND ME ON SOCIAL X/Twitter: https://twitter.com/gregisenberg Instagram: https://instagram.com/gregisenberg/ LinkedIn: https://www.linkedin.com/in/gisenberg/

This week on Page Burners, the group continues their journey through Night of Knives with a deep dive into Chapters 3–5. The discussion explores the book's slower, more atmospheric middle section, the confusion and chaos of Malaz Island during Shadow Moon, and the increasingly tangled loyalties surrounding Dancer, Kellanved, Surly, and the Claw.The crew debates whether Chapter 3 drags or intentionally leans into disorientation and tension, while also unpacking personal reading pet peeves, confusing timelines, and Esslemont's descriptive style. Things heat up once the flashbacks begin, giving us our first real look at Dasem Ultor during the fall of Y'Ghatan — including his conflict with Hood, Surly's growing influence, and the legendary reputation that made soldiers willing to follow him into hell.Along the way, the episode also touches on Stormriders, Hairlock memes, Shadow Cultists, Dancer's intimidating presence, and the ongoing question at the heart of Night of Knives: who actually knows what's happening tonight on Malaz Island?

It's a Sunday Funday edition of the After Party! And for this one we got the return of Marcy! She comes on as we reminisce on Jaguars Gentlemen's Club, the most she's made in one night as a dancer and dumps some trauma on the podcast. Follow us on social media @AaronScenesAfterParty

(00:00:00) Intro (00:01:52) We Just Got Done Rewatching The Claw (00:11:34) Did We Learn Anything Today? (00:14:39) Parting Thoughts (00:17:17) Howl Outs (00:21:40) Apple Podcast Reviews! In this episode we rewatch and then talk about The Claw. I am not Dad. I am Magic Claw. Magic Claw has no children; his days are free and easy.Thank you so much for listening. Connect with us and let us know what you think of the show!Get Dinner with the Heelers merch! At Dashery by TeePublic you can get shirts (and all sorts of other cool things) with Dinner with the Heelers artwork. Grab yours today!Get ad-free episodes via Patreon for only $1 a month: patreon.com/theblueypodcastCheck out this video about how our podcast is made:TikTok: https://www.tiktok.com/@theblueypodcast/video/7370492256005950766Instagram: https://www.instagram.com/reel/C7NKLQhAIUv/A huge thank you to Ryanna Larson (Instagram: @blueyfamilyportraits) for the amazing show cover art. Connect with her on Instagram to commission a portrait for your family!Website: theblueypodcast.comPatreon: patreon.com/theblueypodcastTikTok: @theblueypodcastTwitter: @theblueypodcastInstagram: @theblueypodcastFacebook: Dinner with the HeelersEmail: blueypodcast@gmail.comBecome a supporter of this podcast: https://www.spreaker.com/podcast/dinner-with-the-heelers-a-bluey-podcast--6729926/support.

Hoje o papo é sobre claws! Neste episódio, mergulhamos em como o surgimento do OpenClaw marcou o início de uma nova era na forma como agentes de IA podem ajudar no dia a dia, inspirar novos projetos, e reacender a chama da vontade de desenvolver. Vem ver quem participou desse papo: Paulo Silveira, o host que voltou a programar Luiz Couto, Organizador do Claude Code Meetup São Paulo Sérgio Lopes, cofundador da Alura e CEO do Alun Future Studio Vinny Neves, cohost, dev e professor na Alura Links: OpenClaw n8n Claude Code OpenAI Codex Pi Mono OpenClaw apaga emails de executiva da Meta Nanoclaw Claude Desktop Hermes Claude Code: criando sua primeira aplicação Conheça o curso Engenharia de software na era da IA: como usar IA no fluxo real de desenvolvimento da Alura. Inscreva-se na Hipsters.Builders, a newsletter da comunidade builder. Toda semana, a principal newsletter de quem constrói software no Brasil traz notícias, citações e movimentos da comunidade Builder do X, do Hipsters e do IA Sob Controle, além dos melhores links e eventos. Direto no seu e-mail. Vá para o Vale do Silício com Paulo Silveira, Marcell Almeida, Fabrício Carraro e Marcus Mendes na “Imersão IA Sob Controle e Alura no Vale do Silício“! Vagas limitadas, corra para reservar a sua. TechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões. #7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/ Produção e conteúdo: Alura Cursos de Tecnologia – https://www.alura.com.br Edição e sonorização: Rede Gigahertz de Podcasts

HOUR 3: Can they just claw back that much unemployment? Did these people know they were overpaid? full 2098 Thu, 23 Apr 2026 21:00:00 +0000 gCWRBOOdfL7X6BXsI8foyH2tcNSLhl2g news The Dana & Parks Podcast news HOUR 3: Can they just claw back that much unemployment? Did these people know they were overpaid? You wanted it... Now here it is! Listen to each hour of the Dana & Parks Show whenever and wherever you want! © 2025 Audacy, Inc. News False

Shannon Sharpe, Chad “Ochocinco” Johnson and Iso Joe Johnson react to the Minnesota Timberwolves coming back from 19 down to beat the Denver Nuggets to tie the series 1-1, the Atlanta Hawks win game 2 on the road and beat the New York Knicks to tie the series 1-1, and the Cavaliers beat the Raptors to go up 2-0 in the series and much more! Download the PrizePicks app today and use code SHANNON to get $50 in lineups after you play your first $5 lineup! https://prizepicks.onelink.me/LME0/NIGHTCAP 03:50 - Wolves beat Nuggets 26:15 - Hawks beat Knicks in Game 2 45:05 - Cleveland beat Raptors 56:55 - Wemby is the Unanimous DPOY 1:09:15 - Kevin Durant (Timestamps may vary based on advertisements.) #ClubSee omnystudio.com/listener for privacy information.

This Week In Startups is made possible by:Quo - https://quo.com/TWiSTLinkedIn Jobs - https://LinkedIn.com/twistIru - https://iru.com/twistPlaud - https://Plaud.ai/twistToday's show:Google project manager Shubham Saboo is running 6 AI agents on a Mac Mini that handle all of his side business autonomously, from research, to social posts, to newsletters.He joins Jason and Lon to walk us through his 5-step framework for designing an efficient AI agent team:Start with one agent and onboard them like a new hireStop Googling fixes; just ask your agent how to use itPut your agents on fixed schedulesAdd shared memory so you don't have to repeat yourselfLet agents run self-reviews and rewrite their own instructions.Get the walkthrough to put this entire plan into practice on today's episode. PLUS fresh demos of the “Minecraft”-inspired virtual workspace MoltWorld and AgentMail, which is Gmail for your AI pals, and Jason explains the thinking behind his viral, controversy-stirring “don't talk to journalists” tweet.Follow Shubham: https://x.com/Saboo_Shubham_“How I Built an Autonomous AI Agent Team That Runs 24/7” on X: https://x.com/Saboo_Shubham_/status/2022014147450614038?s=20Follow Mike: https://x.com/mihalich1988MoltWorld: https://moltworld.io/Follow Haakam: https://x.com/haakamaujlaAgentMail: https://www.agentmail.to/Jason's post about talking to journalists: https://x.com/Jason/status/2037573025458016659NYT responds: https://x.com/NYTimesPR/status/2037648223771263082Translated Japanese tweets: https://x.com/melonneet40/status/2038020624015315289, https://x.com/rambling_28/status/2038041455999246422Japanese people singing “Country Roads”: https://x.com/harukaawake/status/2038081269830222259Trailer for “Nuremberg” (now on Netflix in the US): https://www.youtube.com/watch?v=WvAy9C-bipYTimestamps:0:00 Intro1:24 Plaud: If your work depends on conversations — interviews, meetings, calls — you need a Plaud NotePin. You can check it out at https://Plaud.ai/twist and use code TWIST for 10% off!3:05 We're Claw-pilled once again; it's an all AI Agent showcase6:15 Google AI PM Shubham Saboo's Top 5 OpenClaw tips10:14 Quo (formerly OpenPhone) gives you a clean, modern way to handle every customer call, text, and thread all in one place. Try it free at https://quo.com/TWiST.13:26 Tip #1 — Onboard your agent like a new hire17:31 Tip #2 — Talk to your agents constantly19:02 Tip #3 — Put your agents on a schedule19:51 LinkedIn Jobs - Hire right, the first time. Post your first job and get $100 off towards your job post at https://LinkedIn.com/twist.23:41 Tip #4 — Add cross-agent memory29:33 Tip #5 — Let your agents self-improve29:51 Iru unifies identity, endpoint security, and compliance into one platform. TWiST listeners get 20% off when they book a demo at https://iru.com/twist!34:03 Why Jason says founders should avoid journalists38:24 How biased IS the New York Times?47:02 DEMO: Co-founder Mike Nosov shows us MoltWorld51:14 But what's the utility of this?1:05:15 DEMO: Haakam Aujla presents AgentMail (YC S25)1:09:59 How does AgentMail make money?1:17:03 How Grok Translations are creating cross-cultural dialogue on XSubscribe to the TWiST500 newsletter: https://ticker.thisweekinstartups.comCheck out the TWIST500: https://www.twist500.comSubscribe to This Week in Startups on Apple: https://rb.gy/v19fcpFollow Lon:X: https://x.com/lonsFollow Alex:X: https://x.com/alexLinkedIn: ⁠https://www.linkedin.com/in/alexwilhelmFollow Jason:X: https://twitter.com/JasonLinkedIn: https://www.linkedin.com/in/jasoncalacanisCheck out all our partner offers: https://partners.launch.co/Great TWIST interviews: Will Guidara, Eoghan McCabe, Steve Huffman, Brian Chesky, Bob Moesta, Aaron Levie, Sophia Amoruso, Reid Hoffman, Frank Slootman, Billy McFarlandCheck out Jason's suite of newsletters: https://substack.com/@calacanis