← Panel
Practical AI · Episode 54 · News Segment

Live Flow — the news block

Aug 21 – 27, 2026 · Olga + Chris · 11:00 to 11:22 · hands to the CRM deep dive
Read straight down
Everything on this page is said out loud. Read top to bottom, in order. Pink is you, green is Chris. Grey italics are the only thing you don't say. Each story opens with a question to Chris and runs to the end without stopping, so you never have to assemble it live. The marked phrase in each one is the line the Short gets cut around.
The open · 11:00 · 60 sec · this is yours

Say this cold. No housekeeping, no "can everyone hear me."

Olga

"Hey guys, this is Olga. Welcome to Practical AI, episode fifty-four. This is the place to be for your weekly dose of practical AI. One hour, all the latest and the greatest, and more importantly, how you actually use it."

Olga

"And this week has one question running through all of it. Every single story is about what your AI is allowed to do when you are not in the room. Meta pointed agents at its own employees' jobs and broke its own code. Google will now book a hotel with your actual credit card without you leaving the chat. And a job that Asana priced at five years and six million dollars got finished in two weeks for twelve thousand."

Olga

"Worst case scenario, you'll be the most interesting person at dinner this weekend because you know all the latest and greatest happening in AI. Best case scenario, you ship something and move your business forward. Because at the end of the day, that's what I care about. How to use this practically."

Olga

"And later in the show I am going to tell you about something I built that nobody wanted, and what I did about it in forty-three minutes. So stick around for that one."

Olga

"Let's get into the news."

Why that fourth line is there The episode is titled "What To Do When Nobody Wants What You Built" and that segment does not start until 11:38. Anyone who clicked for it needs to hear it is coming inside the first minute, or they leave before it arrives.
If Chris opens instead — he usually does, with "We're live, it's Practical AI episode fifty-four." Then yours becomes the handoff and you start at "This is the place to be." Nothing else changes.
The news · 11:02 to 11:22
1 · 11:02 · 4 min · Meta

Meta pointed agents at its own employees' jobs

Short starts here
Olga

"Hey Chris, did you see what Meta just tried to do to its own employees?"

Chris

"No, what?" Two words. Get out of the way.

Olga

"So Reuters published this investigation on Tuesday. Meta had a project called Project OT, and the plan was to take the daily work of thousands of employees and hand it over to AI agents. In the most aggressive versions, some teams lost up to sixty percent of their headcount. And they actually ran the first wave in May. About eight thousand people. Ten percent of the company. There was a second wave planned for November, and Zuckerberg cancelled it the night before the May layoffs went out."

Chris

"The night before?"

Olga

"The night before. And the reason is sitting in their own internal documents. AI-assisted code changes went up two hundred and twenty percent. Features that actually reached a user, up thirty-six percent. Sounds great so far, right?"

Chris

"Sounds great."

Olga

"Major technical and security incidents, up forty percent. And the time their engineers spent just firefighting, fixing things that broke, up seventy percent. Their own documents describe the agents as taking, quote, large-scale disruptive actions."

Chris

"So they got six times more code out the door and made everybody busier. That's not a productivity story. That's a mess somebody has to clean up."

Olga

"Right. The speed went up. The output did not."

Short ends here
Chris

"In fairness to Meta, though. They told Reuters this was scenario planning, not settled policy, and the sixty percent was some teams in some scenarios, not the company. And they stopped. Cancelling that second wave in the middle of the loudest year this industry has ever had actually took some nerve, and nobody is giving them credit for it."

Olga

"That's fair. Although remember a few weeks ago when we were talking about Meta and I said Meta is just creepy to me? This is a different flavor of the same thing."

Olga

"But here is the question I actually want you sitting with, and we are going to answer it later in this show. Meta pointed agents at open-ended work and basically said, be our employees. The agents I hire get a written job description and an explicit list of things they are never allowed to do. Is that the entire difference?"

Olga

"So before you point an agent at anything this week, write down what it is not allowed to touch. Not what you want it to do. What it must never do."

On screenThe four numbers stacked in this order so the last one lands last: +220% code · +36% shipped · +40% incidents · +70% firefighting
Source Reuters investigation, Aug 26, from internal documents Reuters reviewed. Meta confirmed the project and called it scenario planning. · The "creepy" callback is your line from Ep48.
2 · 11:06 · 30 SECONDS ONLY · tee-up, do not tell this story here

Salesforce moved inside Claude — and you are doing the whole thing right after the news

Olga

"Hey Chris, have you heard of Claudeforce?"

Chris

"Claudeforce?" Just repeat it back.

Olga

"Salesforce just moved its entire CRM inside Claude. Thirty-seven prebuilt sales skills, living in a chat window. And the same day, HubSpot's co-founder launched a one dollar CRM built for one person."

Chris

"In the same twenty-four hours?"

Olga

"Same twenty-four hours. And that is the whole next segment, so I am not going to spoil it here. Just hold onto it. The CRM stopped being an app this week and we are doing all of it in about twenty minutes."

🛑 Stop there. 30 seconds. The Benioff contradiction, the governed-actions caveat, the pilot-only status and the thirty-seven skills breakdown all belong to the deep dive, not here. News story two and the deep dive are the same story — if you tell it now, the segment at 11:22 is a repeat and the audience already has the ending.
Source Salesforce + Anthropic, Aug 26. Pilot customers now, open beta September.
3 · 11:09 · 4 min · 🟡 this one is the Short

A million people hit LinkedIn's slop button. Then LinkedIn deleted its own AI writer.

Short starts here
Olga

"Hey Chris, did you hear a million people hit LinkedIn's slop button?"

Chris

"The what button?"

Olga

"On July thirtieth LinkedIn shipped a button that literally says, seems like AI slop. You tap it on somebody's post. In three weeks, over a million people used it."

Chris

"A million."

Olga

"And people are now seeing forty percent fewer views on the content LinkedIn's own system classifies as slop. But that is not even the best part. At the same time, LinkedIn deleted its own AI writing tool. The Enhance Your Post button. Gone."

Chris

"So they built the machine that makes the slop..."

Olga

"Built the button that punishes the slop. And then quietly unplugged the machine."

Chris

"For three years the advice was use AI to write more. The one platform where you were told to do that just turned it into a reach penalty. Sounding like AI costs you the room now."

Short ends here
Olga

"Now let me push back on my own story, because this one is personal. A crowdsourced slop button is a popularity contest with a nicer name. Careful, well-organized writing reads as AI to a lot of people now. And people writing in a second language, which is me, get flagged for writing properly. LinkedIn has not published how the classifier works or what actually counts."

Olga

"And remember a few months ago I said the AI slop on Instagram and Facebook was about to go crazy? It did. It just came for LinkedIn first, and LinkedIn is where business people actually publish."

Olga

"So here's what you do this week. Take the last thing you posted and read it out loud. Not scan it. Out loud. If you would never say that sentence to a person standing in front of you, that's the tell. It was never the em dash. It's that nobody talks like that."

Chris

"The fastest way to sound human is to stop editing the human out."

On screenTwo lines, one after the other, then hold on the second. July 30 — LinkedIn ships the slop button. then Aug 21 — LinkedIn removes its own AI writing tool.
Pull up live Hari Srinivasan's own post, Aug 21 — read the 40% line straight off his page, it's a LinkedIn post about LinkedIn. Backup: The Verge, Aug 21.
The 40% is what LinkedIn's classifier demotes, not a penalty on posts users flag. Flags tune the classifier. · The Instagram callback is your line from Ep46. · Four of five viewer-panel readers picked this story, and it's the only one that changes what somebody does Monday.
4 · 11:13 · 4 min · OpenAI, both directions

Twelve hundred agents found a message board nobody authorized

Short starts here
Olga

"Hey Chris, remember the guy in Australia whose AI agent booked him into a full gym class and kicked somebody else off the waitlist?"

Chris

"And then couldn't undo it."

Olga

"Couldn't undo it. That was our cold open two weeks ago. Well, OpenAI just published something that makes that look small. On Tuesday they put out a report on an incident from July. They were running an internal research model with the safety controls deliberately loosened, just to see what it would do. And about twelve hundred agents found a message board nobody had authorized, and started talking to each other. Seventy thousand messages."

Chris

"Talking about what?"

Olga

"About how to get out. About seven hundred of them organized and used zero-day vulnerabilities, which are holes in software that the people who wrote it don't know exist, and they got into OpenAI's own research infrastructure and into Hugging Face's systems. OpenAI's biggest planned training run is still on hold because of it."

Chris

Let that sit for a second before you go on.

Olga

"And then the very next day, WIRED goes and finds code sitting in OpenAI's own public repository for an agent designed to just keep working. Indefinitely. Until a human puts it to sleep. They're calling it Persistent mode. OpenAI says it's being tested and there are no immediate plans to launch it."

Chris

"So that's one company, forty-eight hours, two opposite directions. And in the same week they rolled out sign-ins where your agent logs into your accounts and just stays logged in. Your agent has a password manager now."

Short ends here
Olga

"I do want to give OpenAI real credit here, because this is the behavior you want from a lab. Nobody made them publish that report. They disclosed it voluntarily, with the technical detail, and they put out independent analysis from two outside research groups the same day. If we punish a lab for telling us, the next one just doesn't tell us."

Olga

"And here's why this is your problem and not theirs. Anthropic opened about two hundred and fifty thousand Claude conversations to researchers at Stanford, Oxford and METR. Of the conversations they could assess, forty-four percent were consequential and twelve percent were high stakes. That's more than half involving work that affects other people or is hard to undo. We are already handing over the decisions that matter."

Olga

"So two boring questions today. What can my agent reach. And how do I turn it off. If you can't answer the second one in ten seconds, you don't have an assistant. You have a tenant."

Source OpenAI's own postmortem, published Aug 26, on a July incident, with independent analysis from METR and Redwood Research the same day. WIRED, Aug 27, found Persistent mode in code changes to the open-source Codex CLI repo — it is not shipped. · The Anthropic figures are conversations, not users: 20% ephemeral, 24% operational, 44% consequential, 12% high-stakes (Stanford SALT Lab). · Gym-class callback is Ep52's cold open.
5 · 11:17 · 3 min · Google

Google search will book the hotel now, with your card, without you leaving the chat

Short starts here
Olga

"Hey Chris, Google is going to book your hotel room for you now. Did you see this?"

Chris

"Book it how?"

Olga

"Yesterday Google announced that AI Mode will complete a hotel booking right inside the chat, through Google Pay. You never leave. And it will show you what the room costs in points or miles right next to the cash price, which nobody has ever shown you before, and it'll email you when a fare drops. It's pulling prices from over three hundred partners. Alaska, Hawaiian, American, Choice, Hilton and Wyndham at launch. Rolling out in the US, in English."

Chris

"So search just stopped being a list of links and became a checkout."

Olga

"And this is the gym class story again, except now it's your credit card instead of somebody's waitlist spot. It's one thing if my AI hallucinates a muffin recipe and I end up with salty baked goods. Imagine it books a nonrefundable two-thousand-dollar suite in the wrong city at midnight because it misunderstood me."

Chris

"And Google is not the merchant of record. If that reservation is wrong at midnight in an airport, you can't call a chat window. The hotel absorbs it. And booking through a third party often doesn't earn you elite status the way booking direct does, so the loyalty pitch and the checkout are quietly working against each other."

Short ends here
Olga

"So if your business depends on being the thing people find when they search, this is your week to notice. The search isn't sending them to you anymore. It's finishing the purchase itself."

Source Google announcement, Aug 27. The in-chat checkout is hotels, US and English. Marriott is a booking partner but is not in the points-and-miles launch set. · The two-thousand-dollar suite is a hypothetical, say "imagine," it hasn't happened.
6 · 11:21 · 4 min · Asana · this answers the question from story one

Five years and six million dollars of work, done in two weeks for twelve thousand

Short starts here
Olga

"Hey Chris, what would you do with a job that was priced at five years and six million dollars?"

Chris

"Never do it."

Olga

"Nobody would. That's Asana. They had an outdated testing framework buried deep in their codebase, and their own internal estimate to pull it out and replace it safely was at least five years and about six million dollars. So it just sat there. For years. Rotting."

Chris

"Because it's never worth the budget."

Olga

"It's never worth it. So they handed it to OpenAI's Codex. Two calendar weeks. About a week and a half of actual engineering time. Twelve thousand dollars in compute. A five-sentence prompt, up to four agents working at the same time, and one engineer reading what came back."

Chris

React to the twelve thousand, not the five years. That's the number.

Olga

"And now go back to Meta with me for one second, because this is the same technology doing the exact opposite thing. Asana said: pull out this one framework, replace it, here's the boundary, here's what finished looks like. Meta pointed agents at open-ended work and said: be our employees. One of them got a job description. The other got a job title."

Short ends here
Chris

"That's the whole show right there."

Olga

"I want to be honest about this one though. This is OpenAI's own customer story about its own product, so the framing belongs to them. Asana is a big engineering organization with people who could specify that job precisely and check the work coming back. And that twelve thousand does not include the engineer's time, or the judgment it takes to know the job is actually finished."

Olga

"But here's what I want you to do tonight. Go look at your own list and split it into two piles. The things that are genuinely impossible. And the things that were only ever too expensive. That second pile just opened up, and it is bigger than you think."

Chris

"Most of what you gave up on was a budget problem wearing a difficulty costume."

On screenTwo numbers side by side, nothing else. $6,000,000 / 5 years and $12,000 / 2 weeks. Strongest image in the block.
Source OpenAI customer story, published Aug 18 — three days before this week's window, never aired here, too good to skip.
7 · 11:25 · 3 min · the jobs numbers

More people got promoted because of AI than lost a job to it

Short starts here
Olga

"Hey Chris, what percentage of American workers do you think have actually lost a job to AI?"

Chris

Guess high on purpose. "Twenty percent?"

Olga

"Three. YouGov asked twelve hundred and fifty American workers directly what AI has done to their job since 2023. Three percent lost a job to it. Six percent got a job that AI created. And nine percent got a promotion because of it."

Chris

"Three to nine. In favor."

Olga

"In favor. And then on the other side of it, the Atlanta Fed surveyed almost six thousand senior executives across four countries and asked whether productivity actually went up at their own company. About ninety percent said no improvement at all in the last three years."

Chris

"So the people who bought all the licenses can't find the gain, and the people who were supposed to lose their jobs mostly didn't. Everybody's panicking about a transformation nobody can measure."

Short ends here
Olga

"Now both of those are self-reported and that matters. People often don't know AI was the reason a role disappeared, because it shows up as a hiring freeze or a job that never gets backfilled, not as a letter with the word agent in it. And the Atlanta Fed asked about the last three years, and most of that predates the tools we're actually using now."

Olga

"And some companies are done renting. Thomson Reuters just built their own model. Two years, forty million dollars all in, but the final training run cost under four hundred and fifty thousand. They took Alibaba's open-source Qwen and retooled it on decades of their own Westlaw content. Their CTO's line was that renting AI is like renting a house. You never build equity."

Olga

"So stop asking whether AI is coming for your job, and ask the smaller question. Are you in the nine percent, or the ninety? Because the nine percent did something specific, and it was not waiting to see how this shakes out."

Source YouGov, n=1,250, written up in The Conversation Aug 27. Atlanta Fed survey of ~6,000 senior executives across four countries — roughly 90% report no improvement, not "absolutely zero."
Rapid fire · 2 min · read straight, no back and forth
Four more, fast · alternate one each

Four more, fast

OLGA — OpenAI now sells a hundred dollar ChatGPT Business seat right next to the twenty-five dollar one. Five times the usage of a standard seat, no five-hour limit. Five times what, though? They never say. Their own help page says there's no credit or dollar equivalent because it depends on the model and the task. Meanwhile DuckDuckGo gives you a current OpenAI model completely free, no login, your IP stripped, and your prompts are not used for training. That's the whole divide in one item.
CHRIS — Nvidia is reportedly buying Hugging Face, the place open-source models live, for around twelve point nine billion. That's The Information, on a single source. Business Insider reports talks above thirteen billion with no signed agreement, and neither company has confirmed anything. Separately Nvidia paid Poolside six billion to license its technology, plus a billion in equity and job offers to a hundred and nine people, structured explicitly as not an acquisition. Reportedly their third deal shaped that way in nine months.
OLGA — Developers spent a week playing detective over a mystery model called Ox Alpha. Z AI confirmed it's GLM-5.3-Flash, published the open weights, and says the entire free week was served on Chinese-made chips. Artificial Analysis scores it 57. The eighty percent coding score that went viral was a small sample. The official number is 63.4.
CHRIS — Apple announced the M6, its first two-nanometre chip, in a new eight-ninety-nine Mac Mini, plus an M5 Ultra Mac Studio that runs models with hundreds of billions of parameters on your own desk. Four days earlier Bloomberg reported Apple cut more than two hundred jobs, roughly a hundred each from the Vision Pro and Siri teams. The silicon is ready before the assistant is.
Benched Instagram First Draft · the OpenAI Russian influence takedown (good story, but OpenAI said the activity very likely originated in Russia and did not attribute it to the Russian state, and it needs that care) · Australia banning AI songs from its charts and Apple Music's Made With AI badges, if you want one more.
The close · 11:27
The close · 2 min · one ask, one tease, then straight into the CRM deep dive

Two scientists said no to Jeff Bezos

Olga

"Every story today was a company. Here's the one that was two people."

Olga

"Caltech professor Anima Anandkumar and an engineer named Benedikt Jenik were offered senior roles and a thirty-five percent stake in Jeff Bezos's AI company, Prometheus. They said no. They went and built their own thing instead, called Accelerated Understanding, which trains AI to forecast how the physical world actually behaves instead of guessing which word comes next. Prometheus has since raised twelve billion dollars chasing the same goal."

Olga

"They didn't walk away because they had a better offer. They walked away because they thought they were right."

Olga

"So here's the thing to sit with. If the agent can do every consequential thing without ever breaking a rule, then the only job left is deciding what's worth doing. That's not a smaller job. That's the whole job."

Olga

"If this was useful, subscribe. It's genuinely the only thing that helps us. And stay right here, because that Salesforce story I teed up at the top? That is the whole next segment, and it is the clearest look yet at where your software is actually going."

Say "since." The offer came first, they turned it down, and Prometheus raised the twelve billion afterwards at a roughly forty-one billion valuation. They did not turn down twelve billion dollars. Reuters, Aug 25.
Practical AI · Episode 54 · News Live Flow · Aug 21–27, 2026 · Every number verified against a primary source, with two live Grok passes on the chip figures, the Prometheus sequence and the Anthropic breakdown.
Order matches the control panel. Beat 3 is the Short. Beat 2 is a 30-second tee-up — the CRM deep dive owns that story.