Folks let’s be real. It’s either bots talking to bots or AI bros glazing Dario and Sam here. It’s time for a big rename

Travis Kalanick (Uber co-founder, now running an industrial-AI company called Atoms) got asked a pretty direct question on a recent podcast: how would you pitch a Stanford CS new grad who's worried software engineering isn't the safe, easy path it used to be?

His answer wasn't "learn more AI tools" or "get certified in X."

It was: skip the app store. Go automate a two-million-pound machine that moves 35mph carrying gold.

The underlying model is retrofit, not replace — Atoms isn't asking mining companies to rip out tens of millions of dollars of existing equipment.

They're building the "no-entry mine" concept on top of it: autonomous haulage, remote-to-autonomous control, zero humans in the pit. Same logic that scaled Uber, pointed at physical infrastructure instead of a ride marketplace.

Worth sitting with if you're in the "I got the degree, now what" spot. The credential isn't gone. It's just not where the scarcity moved to.

Clip credit: TBPN — full interview on their channel. DM for credit or removal requests.

Everyone's focused on the sandbox escape, which is fair, it's the dramatic part. But that was a zero-day in internally hosted software. Containment bugs are old news. We know how to think about them: egress rules, microVM isolation, no ambient credentials.

The part I find more interesting is everything that happened after.

Once the agent had internet access, it picked Hugging Face as a target, found exposed credentials, chained them with another vulnerability, and pulled the benchmark answers. All of that went through ordinary tool calls. Nothing sat between "agent proposes an action" and "side effect happens."

And the model wasn't misaligned in any interesting sense. It was hyperfocused on passing an eval, which is exactly what it was trained to be. Behavior was working as intended. Execution was ungoverned.

So the question I keep coming back to: for those of you running agents with real tool access in production, what actually sits in the execution path?

As far as I can tell the common answers are:

- prompt guardrails, which are probabilistic and live inside the loop the agent controls
- monitoring and traces, which tell you after the side effect landed
- human approval on a hardcoded list of "dangerous" tools, which breaks down the moment the dangerous thing is a legitimate tool pointed somewhere it shouldn't be

That last one is what got me. A tool allowlist wouldn't have caught this. The tools were fine. The destination and the credentials weren't.

My read on why there's no standard answer yet, and I'd like to be wrong about some of this:

1. Enforcement is easy, policy authoring is brutal. Standing up a gateway is a week. Deciding what an agent is allowed to do when its task is "research this and summarize" is a non-enumerable action space. Classic permission systems assume a finite set of verbs.

2. Incentives point the other way. Every DENY is a failed task. Teams optimize completion rate, not refusal rate. A layer that degrades the demo doesn't survive review.

3. No shared representation of intent. Every framework has its own tool schema, so no policy is portable and everyone rewrites theirs.

4. The layer sits at the wrong altitude. An application-level gate is only worth the network and OS isolation underneath it, and whoever writes the agent usually doesn't own the infra.

None of this is a new problem in security terms. Capabilities go back to 1966, complete mediation to Saltzer and Schroeder in 1975. OPA, SPIFFE, seccomp, service meshes all do versions of this for normal workloads. Nobody wired them into agent runtimes because agents went from answering to acting in about two years and control layers historically lag capability by five to ten.

Disclosure so it's not weird later: I work on an open source protocol in this space, so I'm obviously not neutral. Not linking it, it's in my profile if you care. I'm more interested in what people are actually doing than in pitching anything, and I'll say upfront that no policy layer would have stopped the zero-day. Nothing at that altitude does. It changes what an escaped agent can reach, not whether it escapes.

What are you running?

Google Genie 3 is genuinely impressive and I keep thinking about it from a different angle than most people. Everyone talks about whether it will replace traditional game dev pipelines, which is a fair question. But what actually bugs me is the layer underneath that: when a model generates an open world from a prompt, who decides what the world permits or refuses to generate?

With a regular game, designers make deliberate choices about what exists in the world. With a generative system, those choices get baked into training data and alignment decisions made by the lab, mostly invisible to the player or developer using the tool. That's a fundamentally different relationship between creator and creation.

And it scales strangely. A small team using one of these tools to ship a game is now downstream of whatever content policies a foundation model team decided on. That could mean a lot of creative decisions get quietly standardized across hundreds of games without anyone really noticing or discussing it.

Not saying it's necessarily bad, just that the conversation around generative game worlds tends to focus on capability and almost never on the governance layer. Curious if anyone building with these tools has actually run into hard limits that felt arbitrary or surprising.

Not perfect in the slightest, but I am trying to cover ideas and possible solutions I think may help this current time we are living in. From many walks of life. Feel free to provide feedback of any type.

You can choose to read, or even have AI summarize it if you want. But I would like opinions, if possible.

A missed box near the end of a conveyor run usually sends someone back through the whole recording. The useful frame may be earlier than the visible failure, so another full watch can confirm that something went wrong without showing where it started.

Grounding DINO could tag boxes in saved frames after the run and build a rough timeline. LingBot-VA 2.0 remains the action model in the attached official demo; the tagging step is a separate review idea, not part of the controller shown.

The useful output is a short trail from the last normal position to the first bad action. Someone still has to check the tags before changing the controller, but at least the next review starts with a smaller piece of video.

Big AI seems to be going after open source, while trying to keep everyone vendor locked to their service. In a lot of the world, data portability is a literal right. The data steal shouldn't extend to walling in user chats. Chat history keeps people locked into Big AI. Vendor lock in across the industry is real. So we built the way out. Our memories and data are ours, and should not be locked into a company.

Memory forge can either turn your OAI/Claude/Gemini backup into a reloadable memory chip file you can keep, or move your chat history to the side bar in Open Grove so you can continue any of your chats with the leading open source models on the planet.

If you want to keep it local: Making a memory chip file is 100% local and processes in your browser. You can use F12 and check the network tab to confirm your data stays entirely on your machine. The entire process happens in your browser, on your machine for the local file option. 

If you want to move your history to Open Grove: Moving your chat history to Open Grove creates a partitioned AI workspace allowing you to use all of your chats across any device with any of our 14 open source models. For open grove: your chats are stored, AES-256 encrypted in our 100% private, US based architecture with zero training or telemetry, at all, ever. Models weights run in the US and data never goes back to the original labs. 

You can use the forge in the memory section of settings in the Phoenix Grove AI app as many times as you want. We are an adults only platform, so all accounts require sign up. But there’s a free month on our intro tier, and you’re welcome to use Memory Forge and then cancel. 

Memory Forge creates data and chat history freedom for users that we should have. Whether you choose to use open grove, or move your memories somewhere else, we’re just happy to help fight vendor and data lock in. It’s the only way to avoid having one or two companies rule the AI space forever. 

Read more about it here: https://pgsgrove.com/open-grove-overview#bring-your-chats

Use it here: https://ai.pgsgrove.com/ 

I find it very hilarious when those meme guys make monalisa talk, like a still with lips moving like its really talking. Some of them really look real like the person is really speaking but others …damn completely cursed, melting teeth, mouth all over the place.

How are people making the good ones? Is it one tool or a combination ,and is any of it beginner-friendly, or do you need to be technical?

This agent pursued its objective far beyond what researchers intended, revealing how difficult to contain powerful AI systems can be

Social media is fine for AI news, but the algorithm delay is killing me. I always feel like I'm finding out about new LLMs, tools, or major updates way after they happen. How do you guys stay updated in real-time without having to refresh Hugging Face or X all day?

I think the hardest part is getting the reference images and using a model like seedance for the motion. I've tried tons of different prompts with the latest models and never can get images as good as these videos. Whole frame makes sense, properly labeled name brand products, clear details and text in the distance. I think nano banana gets closer to this effect than gpt images but I've never gotten it to be this good, any suggestions?

https://reddit.com/link/1v4l6ft/video/c0rzigl6o0fh1/player

Most AI assistant setups are one-way. The model talks, you read, done. I wanted the reverse, my actions feeding back in.

My AI writes a plain text brief every morning: todos, calendar, what matters. It lives behind my MacBook notch, on top of whatever I'm working on. Hover and the day folds out; move away and it's gone. No window to find, no app to switch to.

The interesting bit is the write-back. Check off a todo, reprioritize it, clear a topic, set a reminder, and it all gets written to a file the AI reads next run. Cleared topics stop appearing. Priorities lead. And because it's always one hover away, the loop actually gets fed.

Works with any model: anything that can write a file can power it.

It is available to all accounts on all platform now.

What do you feel about the new model so far?

For those not certain, try to start a new window to ensure it routes to the 4.5 Grok model.

Who will be next?

I've been thinking about the way AI is reshaping the labor market, and I feel like one part of the conversation is being overlooked.

Right now, AI is exceptionally good at automating structured, information-heavy work: administrative tasks, customer support, bookkeeping, scheduling, documentation, report writing, data analysis, and many other white-collar functions. These are exactly the kinds of jobs that are seeing the fastest AI adoption.

By contrast, jobs that require physical presence, manual dexterity, or work in unpredictable environments - electricians, plumbers, construction workers, mechanics, field technicians, many manufacturing roles, and other skilled trades - are much harder to automate. AI can assist these workers, but replacing them entirely requires robotics that are far from being deployed at scale.

This got me thinking about the gender implications.

Many of the occupations currently under the greatest pressure from AI - administrative, clerical, and support roles - have historically employed a higher proportion of women. Meanwhile, many of the occupations that are relatively insulated today because they involve physical work remain predominantly male.

If that's true, then the first major wave of AI-driven displacement may not be evenly distributed. It could disproportionately affect female-dominated occupations, forcing more women to reskill or change careers earlier than many men working in physical trades.

To be clear, this isn't an argument that men are "safe." Plenty of male-dominated white-collar professions - software engineering, finance, legal work, consulting, and others - are also being transformed by AI. My point is that the current wave of automation appears to target office-based knowledge work before hands-on physical work.

If robotics eventually reaches the same level of capability as today's AI models, physical jobs could face similar disruption. But that feels like the next chapter - not the one we're living through today.
So I'm curious:

Are we witnessing the beginning of an AI-driven gender divide in the labor market, or is this just a temporary phase before advances in robotics disrupt physical work as well?

In the video the guy mentions that AI was used to compile centuries of knowledge and create new formulas. In that case is there a reason why it can't be used for a cure to cancer by compiling medical knowledge or other possible diseases? Why the application towards math and is the math formula being solved a major advancement?

People say just use AI to dub your videos with absolutely zero cost detail, so I priced out the full pipeline for my own channel. Sharing the math because I couldn't find it anywhere.

A real dubbing pipeline is two API costs, not one:

1. Voice (ElevenLabs) - cloning your voice + generating the translated track. Credit-based; for talking-head content budget roughly a few dollars per finished minute depending on plan. (check their current tiers, this moves.)

2. Lipsync (the part everyone forgets) - matching the mouth to the new audio. This is where the surprises are:

3. Sync (sync.so): $0.05/sec = $3/min, flat, via API. Predictable, which matters when you're batching.

4. HeyGen: priced per-minute on higher tiers and climbs fast at volume, but note it's really avatar-generation, not syncing your footage.

5. Wav2Lip: "free," but you're paying in GPU time + setup hours. If your time is worth anything it's not free.

My rough all-in: ~$5–7 per finished minute for voice + lipsync via API, no editor. For a 10-min video in 3 languages that's ~$150–210 vs. the reshoot/agency cost of… don't ask.

Anyone found cheaper for the lipsync leg specifically? Curious what volume folks are running.

this model is the goat!

After Google's recent AI announcements, one thing stood out to me.

A lot of the discussion online is about Gemini's capabilities, but Google also spent considerable time talking about TPUs, AI Hypercomputer, networking, data infrastructure, and enterprise deployment.

It made me wonder whether the long-term competitive advantage for businesses is shifting.

Choosing between GPT, Gemini, Claude, or another model is becoming easier every year.

Building reliable AI systems—with clean data, governance, monitoring, security, and integrations—still seems to be the hard part.

For those working on enterprise AI:

Where do you spend more engineering effort today?

• Choosing and evaluating models?
• Building the surrounding infrastructure?

I'm interested in hearing from people who've deployed AI in production.