7 Ways How We Use AI Is Changing

The AI Daily Brief: Artificial Intelligence News and Analysis

The episode explores seven fundamental shifts in how humans interact with artificial intelligence, moving from simple prompting to more complex

Key takeaways

• Product design is shifting toward simplification and integration, exemplified by Meta's Muse and Anthropic's unified Claude experience.
• The 'monothread' pattern uses context compaction to allow long-running conversations that inherit past knowledge without losing instruction.

Main topics

• Simplification of AI Interfaces
• Monothreads and Context Compaction

Notable quotes

The beauty of Muse is that they've managed to introduce it in a very accessible way.

Conclusion

The episode provides a roadmap for understanding the next phase of AI

Transcript preview

Speaker 1 (0:00) The way we use AI is changing. First, we were prompt engineers, then context engineers, then harness engineers, then loop engineers. And while it's tempting to view all of these things as just one silly buzzword giving way to the next, the reality is that we are all together on this journey figuring out just the best way to use a completely new technology that is changing both how we do our current work and opening up new possibilities of what work we can even do. Today we're talking about seven ways that how we use AI is changing. The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI. All right, friends, quick announcements before we dive in. First of all, thank you to today's sponsors, Blitzy, Robots and Pencils, Harbor, and HyperAgent. To get an ad-free version of the show, go to patreon.com slash AI Daily Brief, or you can subscribe on Apple Podcasts. To learn more about sponsoring the show, send us a note at sponsors at ai-dailybrief.ai. Speaker 1 (0:59) Today's episode is about a bunch of patterns that are shifts, I think, in how, on average, we interact with AI on a daily basis. One thing that's been true since the very beginning of ChatGPT is that our patterns of interaction with AI have never been static for long. At the beginning, it was people discovering new ways to prompt the AI that had better or worse results, which was then communicated through hundreds of articles, posts, YouTube videos, podcasts, and courses. But over time, the interaction pattern shifts have gotten more significant and more substantive. Over the last week or so, I saw a number of announcements that really reinforce some fairly big shifts in these interaction patterns. And while I don't think that how we use AI will ever be truly static, I do think that some of these shifts, which I'm going to cover in this show, are fairly fundamental and likely to stick. And thus, of course, if one is trying to be efficient with their time, maybe more worthy of attention. So first up is an interaction pattern. that is not so much us changing how we interact with AI, but product design decisions that are shifting the options that we have to interact with AI. Very clearly, there is a push towards simplification and integration and user experiences that have less rather than more cognitive decision-making for the end user. One thing that's been interesting for me, sitting in this seat that I have, is the extent to which early AI has tended to defy traditional Silicon Valley logic. that users won't show up unless you give them an incredibly simple and clear experience. In fact, quite to the contrary of that, a lot of the early adopters, not just from tech circles, but from broader knowledge work circles, have, rather than resisting complexity, thrown themselves in headfirst. A great example of this for me was when 9,000 people, most of whom weren't even close to engineers or really technical in any way, signed up for the free claw camp program I put out earlier this year, which basically had them crawling through glass to figure out how to build their own agents. And yet it appears that perhaps even if the portion of people who were willing to do that sort of hard work has been higher in AI than in other past tech sectors, there are still a lot of folks who want that simplicity. Certainly, simplicity is one of the watchwords for the new Metamuse product and something that even the power users, who fully have the capability of dealing with complexity, are allotting in the product. How IAI's Claire Vo has discussed in numerous places how well thought out she thinks the Muse design is, specifically around what it does and doesn't obfuscate from the user. Node.js creator Ryan Dahl, who again, certainly has no shortage of complexity capability, also shouted out Muse for having nailed the simplicity. Wrote technologist Tom Goodwin, the beauty of Muse is that they've managed to introduce it in a very accessible way. Don't tell me how you work, just show me how to do things. David Herman wrote, I think Muse is going to win the casual AI race. I showed my dad, who was nearly 70, and it clicked. He was amazed that I could have it create an entire contract for me, update things on it, then email and send it to a customer all through texts. Claude, OpenAI are great, but so far I'd say less than 1 % of the population gets what these models are. Meta just made it all super easy. And it's clear that this was intentional. Meta Chief AI Officer Alexander Wang wrote, a big part of the team's focus when building Muse was to make something that just worked. So much work went into all the little details to make the product simple and easy to use. And of course, the thing that makes this a trend, not just a design decision from the meta team, is that this sort of simplification is showing up everywhere. One of the biggest product updates that we got this week came when Anthropic announced that Claude cowork and chat are no longer separate things. Claude is careening towards an experience where instead of it being fragmented and full of decisions for the user before they even get started, instead a single unified experience. And again, the watchword was simplicity, simplification. And by the way, as pointed out by Cloud Code Creator Kat Wu, this simplicity extends not only to eliminating the difference between co-work and chat, but also to integrating Cloud design so that your standard core Cloud also has all of the capabilities to do things like make slides, designs, docs, without having to switch into some specialized experience. And again, the team at Anthropic reports that this was based on direct user feedback. Anthropic Labs lead and former Instagram co-founder Mike Krieger wrote, The most common thing we hear, people aren't sure which product to start with. That friction gets in the way of getting the best from what these models can do. Now, as I mentioned in an earlier episode this week, I'm not totally sold on this on a personal level because I feel like I like having more specific control, but boy do I seem out of sync with the average here. Christian Selig reposted the announcement and said, Can we do this with Codex II, please? The two modes are like having two parents fighting. Seanu Matthews summed up, People don't want to interact with two to three text agents, two to three chatbot agents, two to three terminals on desktop. You want a simple, unified interface and want the agents to coordinate how it gets done. You simply want to ask and receive. The platform should coordinate and delegate agents, route models for tasks, handle whether it's local cloud or VM, be proactive and reactive about tasks. Instinct, Muse, and Grokbot really hit a nerve, and it's increasingly clear we're in another paradigm shift moment, in my opinion. Now, if the first change is about the simplicity of the interfaces through which we use AI, the second change is itself also a version of simplicity that has to do with how we control AI. And this is the trend towards monothreads. The idea of a monothread is that instead of having to switch context windows and explain new needs and new prompts separate from the previous things that you've done, instead you use a single, long, continuously running thread that inherits the context from past conversations as a way to manage the entire experience. Now, previously, this was limited by the context window. At some point, the AI would get tired, i.e. its context window would get filled, and it would start doing weird things, making errors, losing instructions, etc. Many of