# 5 AI Engineering Trends for Non-Engineers — Transcript (2026-07-15)

https://aidailybrief.ai/e/2026-07-15 · Listen: https://pod.link/1680633614

---

[00:00:00] Today on the AI Daily Brief, the the five the five trends among AI engineers that non-engineers should be paying attention to. Before that are the headlines, more information about OpenAI's first consumer device. the AI Daily Brief is a daily podcast and video about the most important news and discussions in AI, All right, friends. All right, friends.

Quick announcements before we dive in First of all, thank you to today's sponsors, KPMG, Robots and Pencils, Blitzy, and Airtable

To get an ad free version of the show, go to patreon.com/aidailybrief, or you can subscribe at Apple Podcasts. And to learn more about sponsoring the show, send us a note at sponsors@aidailybrief.ai. We kick off today with an update on OpenAI's first consumer device

as it apparently enters the prototyping stage. Bloomberg's Mark Gurman has the scoop, with his sources describing the device as a portable screen-free smart speaker designed to be a type of new home computer for the AI era

[00:01:00] The sources suggest that the device is intended to remain in the home and will be able to control smart home appliances and play music, as well as functioning as a chatbot interface. The pitch is that this will be a human-like AI companion

Now at first read, this essentially sounds like a replacement for Alexa or Google Home devices. But according to the sources, OpenAI is betting that advanced AI features give it an edge in the market

Sources said the goal is to make the device feel like a physical manifestation of ChatGPT and somewhat alive, rather than just an electronic device responding to commands

To that end, the device will have some components that move on their own, making it feel like an anthropomorphic mini robot rather than an inert piece of electronics. The device will incorporate ChatGPT's memory feature to evolve its understanding of the user, as well as a camera and other sensors to understand its surroundings.

It will incorporate the two-way voice model technology unveiled with the release of GPT Live last week, enabling more natural real-time conversations

That natural styleis apparently key with OpenAI viewing the ability to connect with users in a human-like manner as their core advantage The device will have rechargeable batteries, [00:02:00] allowing users to carry it around the home rather than needing to keep it plugged into one location. OpenAI aims to unveil the device by the end of the year before releasing it in 2027.



And reportedly, it could be the first of several consumer devices from OpenAI, with rumors of a pendant, earbuds, and maybe even a smartphone



one one question now casting its shadow over the launch is how it will be impacted by the Apple lawsuit Apple recently accused OpenAI of IP theft and will almost certainly file for an injunction to stop the release of a device based on any of their IP

And while the lawsuit discusses the brushed metal finish of an iPhone as one of their concerns, Apple is also reportedly working on a series of AI-powered smart home devices

That could muddy the waters quite a bit more

And to that end, OpenAI has elaborated slightly on their initial response to the lawsuit. In a new press statement, they said, " "While While we take these allegations seriously, we're not aware of any evidence that this complaint has merit. We believe in fair competition and allowing people the freedom to work wherever they choose, and we're focused on building innovative technology that empowers people everywhere."

Now Now in [00:03:00] terms of first takes

Fair number of people are pretty skeptical. Negligible Negligible Capital writes, " "Call me Call me crazy, but this OpenAI product sounds pretty stupid so long as you own a smartphone, except for the fact that it can constantly watch and listen to you in your home

Chris Paxton wrote, " "The The new OpenAI consumer device is said to be a speaker with movable parts. Mixed on this, to be honest, but the big problem with smart speakers like Alexa was always that they were stupid."

Prakash provides the bull case saying, " Want to know why they're doing this? AI is getting defined by context, the data it has access to, the actions it can perform. You will have a personal AI like ChatGPT. You will have a corporate AI like Claude Tag. What's missing is a family AI. what it will likely be able to do: recognize every family member by face and voice, manage schedules for everyone, message you, call you on the phone, run a variety of errands, and be upgraded with capability over time.

If they do it right, it will become as familiar and lovable as your family dog Now, I'm Now, I'm not sure that I am sold

on this new device being Fido. But I do think it is notoriously hard for [00:04:00] people to predict how consumers are going to interact with new categories of products

I'm pretty skeptical of the pitch of Alexa but better

But I'm also, broadly speaking, willing to suspend some amount of skepticism because it feels inevitable that there are going to be some new category of devices that arise based on this new type of intelligence. I think the bigger question for OpenAI specifically is just where this is going to fit with their priorities Part of the reason that the company has gotten its mojo back recently



is that it spent the last few months abandoning, what it has famously called side quests to focus on building its coding and enterprise business Now, this is a company that's going public.

It's gotta draw differentiation somewhere

And even if the enterprises are valuable now, one of the unique things that OpenAI has that Anthropic doesn't is the consumer base so maybe they feel it's important to actually have an answer to how to monetize that user base, and devices like this are part of that answer



then again, it is really hard to be a hardware company and a software company at the same time

And you gotta think that there are discussions internally about just how much they should be supporting both efforts

Moving now into the political [00:05:00] realm, the Trump administration has introduced a new cybersecurity clearinghouse, which is the first major program to come from the recent AI executive order 

The initiative is called, and no I'm not joking, Gold Eagle, and will bring together government agencies, companies, and open source projects to share information on cyber vulnerabilities.

Gold Eagle was rolled out earlier this month as a joint effort between the Treasury Department, Department of Homeland Security, and the Pentagon in consultation with AI companies. The concept stems from the Mythoshock, which uncovered hundreds of vulnerabilities in critical software.



This revelation kicked off Project Glasswing, a multi-industry sprint to detect bugs and deploy patches. That effort made it clear that better information sharing and coordination was going to be necessary in this new AI era, and Gold Eagle is meant to make Glasswing-style efforts a permanent government initiative.

Now, a few other policies from the cybersecurity EO are still in the works Reporting suggests work is underway to define a model vetting protocol to allow for government AI safety testing ahead of new frontier releases. And it seems like a set of clear standards are being negotiated between the government and the AI industry



which has a very meaningful chance of being a huge upgrade to the ad hoc [00:06:00] approach that we've seen with Fable and GPT-5, 6. There's There's also those rumblings we've been covering about a Chinese model ban, which some fear 

could extend to open source models in general

That said, during the press briefing for Gold Eagle, National Cyber Director Sean Carancross addressed those rumors, commenting, " I could not be more clear that we are in full support of the US open source community. We will do everything we can to support the strength of that community."

Finally today, one of the simmering conversations over the past month or so has been whether enterprises can trust AI companies with their data



This has always been a question for enterprises dealing with software providers around sensitive information. but it was brought to the foreground during the release of Fable when Anthropic said that customers with zero data retention clauses would still have their data monitored for safety reasons.

It's loomed larger in the conversation ever since. Palantir CEO Alex Karp discussed the risks on CNBC

And And the topic was also a major theme in a pair of recent essays from Microsoft CEO Satya Nadella, which could be summed up as saying you can't trust AI companies with corporate data. But how real is the risk? [00:07:00] Well, at least in one instance, specifically when it comes to SpaceX it appears that the risks were pretty real.

On Monday, a security firm called Sarah Lab published an audit that found that Groq Build was uploading entire code bases Even if the coding task only required a few files, gigabytes of data were being uploaded

While most AI providers will upload necessary code snippets and store reasoning traces, this is an instance of Grok Build just dumping the entire repo up front Security analyst 

Hari Melakal verified the results, finding that even in a session with zero tool calls, Groq Build still uploaded the entire code base. Hari commented, It It ships a malware-like background code collector."



Now, part Now, part of the reason that people are pissed is that this seems to have been happening regardless of user settings. Users can opt out of transmitting data to help improve the product, but that appears to have had no effect

As of Monday, SpaceX AI made changes to the code which stopped the uploads and added a new slash privacy setting as a manual override. And they claim that all API use now defaults toto zero data retention. AI developer Andrew Millet wrote, "[00:08:00] Zero data retention and slash privacy are always respected in Grok build, and swapping your settings with slash privacy deletes any synced data retroactively."

Elon Musk added that, as as a precautionary measure, all user data that was uploaded to SpaceX AI before now will be completely and utterly deleted. zero anything whatsoever will remain

And yet, honestly, people were not happy about this. Benjamin DeCracker writes, " Why did it happen in the first place? 'Ha ha, I guess we'll delete it now,' is not great."

Accelerate Harder wrote, " "There There is no acceptable scenario where uploading codebases and secrets is an acceptable default. If that is indeed what happened, you must do a public incident review. My trust for xAI as a business partner is on the floor." Flower Slop accused, " If OpenAI had done this, you'd have posted about it 20 times, called them the worst company on earth, and said no one should ever trust them again.

But now that you've done it yourself, all you have to say is, 'Sorry, don't be mad. I'll delete it, I promise.'"

Ultimately, all of this highlights how much of AI data retention policy still hinges on trust



many users of Grok Build likely had their full codebases scraped over recent [00:09:00] weeks, and we have no real way to verify whether they were actually deleted as Elon claimed

Now, AI The entire episode gives a lot more credence to Satya Nadella's point when he wrote

In In the AI age, the buyer risks giving away knowledge just in order to use what they bought. It's the kind of knowledge a competitor could never buy and the kind that leaks out almost imperceptibly



even even if you take this at face value as a mistake and give SpaceX AI the benefit of the doubt, it still puts a fine point on many of the issues that we've been talking about over the past few weeks So that's gonna do it for today'sheadlines.

Next up, the main episode 

One of the most important AI questions right now isn't who's using ai, it's who's using it? Well,

KPMG and the University of Texas at Austin. Just to analyzed 1.4 million real workplace AI interactions and found something surprising. The highest impact users aren't better prompt engineers. They treat AI like a reasoning partner.

They frame problems, guide thinking, iterate, and push for better answers. and the good news, these behaviors are teachable [00:10:00] at scale.

If you're trying to move from AI access to real capability, KPMG's research on sophisticated AI collaboration is worth your time. Learn more at kpmg.com/us/slash sophisticated. That's kpmg.com/us/sophisticated. I cover the capability gap between AI potential and AI reality every day on this show most companies are still figuring out how to start. Robots and Pencils is already launching and scaling. Agentic generative AI in production at large enterprises in weeks. AWS Advanced Tier pattern partner more than doubled in a year

And they're hiring

50 open roles. If you're someone who knows this moment is different, who wants to be inside it, not watching it, this is worth a look. At Robots and Pencils, the best ideas win, and the team is purposefully kept super high quality

This is the kind of place you look back on as the best decision you ever made. Take a look at robotsandpencils.com/careers 

The if you're looking to adopt an age agentic, SDLC, blitzie is the key to [00:11:00] unlocking unmatched engineering velocity.

Blitzes differentiation starts with infinite code context. Thousands of specialized agents ingest millions of lines of your code in a singlepass. Mapping every dependency

with a complete contextual understanding of your code base. Enterprises leverage blitz at the beginning of every sprint to deliver over 80% of the work autonomously,

enterprise grade, end-to-end tested code that leverages your existing services, components and standards. This isn't AI auto complete. This is spec and test driven development at the speed of compute. Schedule a technical deep dive with our AI experts@blitz.com. That's BLI tz y.com.



This episode of the AI Daily Brief is brought to you by Hyperagent where you run fleets of agents your team can manage together New users get 1000 in inference Forget local agents and chat workflows waiting on your laptop to be prompted Hyperagent deploys alwayson agents in the cloud doing real work across the tools your team already uses Marketing's agent turns competitor moves into landing pages sales agent enriches leads drafts emails and updates the CRM ops agent chases the [00:12:00] paperwork and tracks the budget Every agent has access to shared context and follows your rules about scope and approvals It's time you add agents that feel like teammates Hire yours at Hyperagent built by the team at Airtable Claim your 1000 in inference at hyperagent.com/aidailybrief. 

Welcome back to the AI Daily Brief. Today, we are doing something Welcome back to the AI Daily Brief. Today, we are doing something a little bit different that I'm very excited about one of my longest held tips and tricks for non-engineers

who want to be ahead of the curve when it comes to where AI is going, is to pay attention to what

with regards to AI actual software engineers are talking about right now

since since early 2023 Doing this gives you about a six-month headstart on everyone else



when it comes to everything from the tools people are using to how they're thinking about the relationship between models and larger ecosystems

to their relationship fundamentally with work in a new AI-mediated way

and one of the and one of the best sources for keeping up on what AI engineers are [00:13:00] thinking about is, of course, the AI Engineering Summit and the AI Engineering World's Fair

Hosted by Sean Wang, AKA Swixx and a group of other collaborators The World's Fair happens annually and the summits usually happen in the spring and the fall



and are always just chock full of alpha



earlier earlier this month, the annual AI Engineering World's Fair happened in San Francisco and unfortunately this time I was not able to be there

Luckily, Richard McManus, who works with Leighton Space



which is also a Swix joint wrote up a post about the five trends that defined the event. So what we're gonna do today is look at those trends and try to understand what the implications might be for non-engineers down the line



Now this year's event actually happened on almost the three-year anniversary of Swix coining the term AI engineer. Back then, people were still referring to the intersection of AI and software development vaguely as prompt engineering.



although prompt engineering would go on to be a non-technical discipline as well, the point was it was not nearly as clear back then as it is today

that AI writing software was going to be [00:14:00] not only the key early professional use case for AI, but also the thing that would unlock everything else

Back on Back on June 30th 

of '23, Swix wrote, " Emerging capabilities are creating an emerging title. to wield them, we'll have to go beyond the prompt engineer and write software and AI that writes software

Importantly, Importantly, and this was not consensus at the time, Swix wrote, " I think it is a full-time job. I think software engineering will spawn a new sub-discipline specializing in applications of AI and wielding the emerging stack effectively, just as site reliability engineer, DevOps engineer, data engineer, and analytics engineer emerged."



now now if anything, in retrospect Swyx ended up underselling how significant it would become as effectively all engineers are AI engineers to greater or lesser extent. But directionally, he was dead on Now Richard writes that three years on

The field of AI engineering has changed dramatically



in, and in these five trends

We see quite a bit about the state of AI building Now I think taking a step back

The most fascinating through line across all of these trends is a recalibration of our [00:15:00] relationship with autonomy. so keep that in mind as we go through these. the first trend that Richard calls out is that the, quote, "Focus shifts from agents to the systems around them."



o- now this is something we've obviously been talking about a lot on this show throughout the year The idea that alongside agents coming to full production, we're realizing that agentic capacity isnot just a question of model, and it's not even just a question of context that you feed the model

it's about the harness and broader system that the agent operates in. That includes, yes, access to context and data, but also access to skills, ability to interact with tools, and increasingly, ability to route between different models based on the task at hand

Now, Richard argues that one good way to compare how AI engineering has evolved is to compare two essays three years apart from Lillian Wang, formerly an OpenAI researcher and now co-founder of Thinking Machines Lab. back in back in 2023, she wrote a post called "LLM-Powered Autonomous Agents," which described the anatomy of an LLM agent in terms of things like planning, memory, and tool use

The examples she pointed to were [00:16:00] things like AutoGPT, BabyAGI, and GPT Engineer Which were, I remember, for the first couple months of this show back in April and May and June of 2023

The topics that always receive the most interest and the most downloads, and the most views on YouTube



Richard points out that her new essay, " Harness Engineering for Self-Improvement," focuses not on the agent itself, but on that system surrounding the agent. " The harness," he writes, "that manages workflows, context, permissions, evaluations, persistent state, and continuous improvement."



in other words, he writes, " AI engineering has moved beyond prompting models towards engineering reliable systems around them



now now this is the first place that we see that trend that I mentioned of the recalibration of our relationship with autonomy

Richard writes that at the event this year, agents were largely positioned as augmenting the AI engineer rather than replacing them this was a big part of the substance of the day two keynote With OpenAI's Romain Huet

who said software ate the world and then AI ate software, but now what we're here to say is that the AI engineers are eating the world. he argued that the goal [00:17:00] of tools like Codex is to make it easier for engineers to collaborate with agents



now this dovetails especially with the early comparisons between Fable 5 and 5.6 Sol, which have tended to find Sol being the preferred model for when you have a big job that you want the AI to go off and do and only come back to you when it's done, versus Five, Six Sol, which is a better collaborator

As an aside it also seems like the launch of 5.6 has done a lot when it comes to Codex adoption, given that just in the last couple of weeks it's jumped from 5 million to 7 million active users



trend trend number two according to Richard will also probably not surprise regular listeners He identified the trend as loop engineering is the new control layer

Indeed, Richard said that if there was a single word that was the buzzword du jour of the event, it was loops

OpenClaw creator Peter Steinberger

Prominently shared a slide that said the future isn't 20 terminals, it's better loops

But interestingly especially with the lens of trying to understand what AI engineers are talking about that might be relevant for [00:18:00] other types of knowledge workers Richard writes that the loop discourse is actually separating into two loops that interact, an inner loop and an outer loop

The inner loop is the largely autonomous work being done by agents

and the outer loop is the job of leading engineers to oversee that work and improve it with things like better skills

Roland Gavrilescu, the co-founder and CEO of Introspection, said, " "You can think of You can think of the system having an inner loop and the outer loop. The inner loop is the primary system interacting with users and performing the work

Roland then introduces the concept of auto research

which is concerned with the outer loop and is another system that studies and maintains the primary system. the outer loop can include feedback signals, evals, and human input. So even if it is still largely autonomous, it's a method of oversight for the primary agent loop



former Google engineer, Addy Osmani said, "Agents can run much more of the inner execution loop, but that outer loop is still engineering."

Indeed, Indeed, Richard writes that the term loop engineering came up multiple times, suggesting in his estimation that it is the human AI engineer's responsibility to build these loop systems

Summing [00:19:00] up again, Peter Steinberger said, " The agent runs the inner execution loop. I set the direction and make decisions in the outer loop."

loop." Now again, taking a step back

What the loop discourse is actually about, more than anything else

is about figuring out repeatable interactions that allow us to get the most from agents who are now doing an increasingly large portion of our work

In some ways, the separation of inner loop and outer loop is part of this reclamation where the AI engineers are asserting their agency relative to their agents

And I think And I think what's important because it can sound so buzzwordy, is a lowercase L, not an uppercase. By which I mean loops is a word

That doesn't necessarily mean exactly one thing but stands in for the emerging set of interaction patterns that allow agents to improve their own work over time, and that allow us as humans leading the agents to improve their ability to work over time



third third trend from the AI Engineering World's Fair was AI engineering enters the enterprise

Now Now this was in some ways the forward deployed engineering track. And given that pretty [00:20:00] much every AI company has now determined that to get their products to actually work inside their intended customers, they have to support their customers with a much more hands-on type of implementation force, 

It's probably not all that surprising to see an FTE track show up at the event

Now, one of the interesting questions that seems to come up is what the end result of an FTE type of engagement is supposed to actually look like



Cursor's Pauline Brunet said, " "When we When we walk away at the end of the engagements, in our case, we have deployed cloud agents, long-running agents, automations, and we've built applications on top of our cursor SDK

And And indeed, a more general term for this set of enterprise infrastructure

that apparently was being used a lot at the event was Software Factory



And yet that, if anything, perhaps even less defined than something like loops



Zach Lloyd is the CEO of Warp and was a speaker at the event

And the company views itself as a software factory platform In an interview with Layton Space, CEO Zach Lloyd explained where he first came across the term software factory

Zach said, we started we started with one-off automation, run an [00:21:00] agent in the cloud. A lot of platforms began there. Then it became run an agent in the cloud on a timer. The next question was, what was the most valuable loop to automate? The answer is basically the main loop of software engineering: triage, specification, implementation, review, verification, shipping, and monitoring

Now, when it comes to the relationship between an enterprise and a software factory

Zach argued that one of the big pieces of work for enterprises is figuring out which parts of their work life cycles need to be automated and where humans should be brought into the loop

And And interestingly, in a follow-up blog post on X, Zach argued that the reason the factory framework has become more important is not only that agents are now more capable of doing big chunks of the coding life cycle, but that also, quote, That extensive interactive agent use has created a number of problems, from cost controls to governance to security."



the root problem, Zach says, is that interactive agents have human operators, and those humans all use them in very different ways, which don't always maximize business value and can create risk An example he gives [00:22:00] is a human always using the most expensive model even when they don't need to for a given task

The idea behind a factory approach, he says, is to set up a system that minimizes human variability and maximizes output with controls that ensure security and compliance



very, now now this is very much a software conversation



But I think that a lot of the problems that these software factories are trying to solve for are going to find themselves repeated as agents find their way into other areas of knowledge work

That example of always using the most expensive model is certainly not limited to software development Or his other example, a human inadvertently creating a security issue by installing MCPs that have too much access as everyone gets familiar with managing context to support the agents that they're using, whether it's in software engineering or product development or marketing or sales

this is going to be an issue for them as well

The fourth trend at the event was coding agents replacing IDEs as the developer interface

And I think that this is one that's already indicative of a larger, interaction pattern trend that we're seeing shift



an episode an episode from a couple of weeks ago was all [00:23:00] with each of those instances of Claude not being connected to the individual user who tagged it in, but instead connected to a specific set of permissions and context within the channel that they were engaging In other words, there might be a single Claude Tag instance with a specific set of context and a specific set of tool access and a specific set of permissions that everyone in your organization's marketing channel is interacting with that's different than the permissions and tools and context of the Claude that the folks over in the sales chat are interacting with One of the things that was super notable about the Claude Tag announcement Was that Boris, one of the creators of Claude Code, said that something like sixty-five, I think, percent of their new code was now being initiated in Claude Tag Chats

a a major, major shift in the interface and interaction pattern with which we manage this intelligence Now, one of the things that's interesting about these types of interaction patterns, is that this is one area where the big labs are not waiting for non-engineers to adapt to engineer-type practices.



they are dragging functionality over from the engineering-first experiences into the main experiences that [00:24:00] they're offering for all consumers

The best example of this is probably ChatGPT Work which effectively takes Codex and plops it into the main ChatGPT app for everyone to use



to Rich- the fifth trend according to Richard was every agent platform building around skills



Richard referenced Adi Osmani's definition

Writing skills encode the workflows, quality gates, and best practices that senior engineers use when building software

They are packaged so AI agents follow them consistently across every phase of development

At the event, Vercel's Andrew Q said that skills were useful as portable on-demand knowledge, and Introspection co-founder Roland Gavrilescu

Argued that AI engineering had shifted from agent tools to agent skills



Google DeepMind's Philipp Schmid



argued that skills reduce the need for orchestration code. allowing developers to use agents without code

One speaker, Paul Bacchus

even discussed his project around agent skills called Impeccable

an open source design skill system



for improving the interfaces that coding agents create. Now, more Now, more interesting even than that project [00:25:00] Paul argued that skill engineering is going to be a discipline in its own right



and and as we wonder which of the conversations happening with AI engineers right now are going to be happening with AI knowledge workers in the future, skills I think are incredibly high on the list. Think about this. It is highly likely that if you are very good at your job, you frequently run across things where even the best models, including Fable 5 and GPT 5.6 Sol

don't do as well as you want them to. th- Now that's not everything. Something they're going to be great at

But especially when you're really, really good at something You tend to see the inherent limitations of AI even faster

The folks who are advocating skill engineering would argue that rather than just waiting for the models to improve with Fable 6 or what have you, starting to figure out how to use skills, how to encode knowledge and rules and dare I say it, taste in skills is potentially a more productive path



In his closing keynote, Y Combinator President Gary Tan



Argued that using skills effectively

including in business functions, [00:26:00] including sales, support, and finance, was fundamentally integral to being an actual AI-native organization

And yet skills themselves

can be their own sort of autonomy trap

AI AI Engineer World's Fair attendee Tyler Brown wrote that one of his lessons from the event was to revisit and re-implement your skills. " Each time there's a new model release," he wrote, " "it's as it's as if you have a kid that grows from middle school to high school. You have to change the curriculum for them to get the benefits of the new model."

Yet it was not that



but Tyler's broader observation that I think runs throughout the trends that Richard identified and also a lot of the chatter that I've seen around the event Tyler wrote, " Something about this year's AI engineer world's fair just hit different.

Last year was the year of let the agents rip. this year was the year of realizing that autonomy without structure creates as much slop as leverage

In short, while it's not universal, broadly speaking one of the standout sentiments from the AI engineering folks

is the reclamation or reemergence, or however you wanna put it, of the human at the center of these agentic [00:27:00] systems

Back in March, I tweeted, " Call me crazy, but I think the companies that give everyone on their team a team of agents aregoing to kick the slats out of the companies that replace their teams with a team of agents

And I think and I hope that we're starting to see that sentiment move structurally into the mainstream



So So guys, those are the five trends that defined AI engineering at the AI Engineer World's Fair this month

And their implications for other people who aren't just AI engineers. Big thanks to Richard McManus for capturing all of this, and of course, Swyx and the team for putting on the event. if you wanna follow my advice and stay closer to the pulse of what AI engineers and developers are talking about, the single best source for that is going to be Latent Space, latent.space

And might I particularly recommend Their AI news email weekday roundups

They can be really dense, but they aggregate a ton of discourse and are very much worth your time

For now, however, that is gonna do it for today's AI Daily Brief. Appreciate you listening or watching as always, and until next time, peace 

​ 

[00:28:00]