5 Ways Claude Tag Could Change How You Use AI

Speaker A: Today on the AI Daily Brief. Why Claude tag and approaches like it might change how you use AI. Before that in the headlines, an anthropic customer has sued the US over losing Fable. But can it possibly help? The AI Daily Brief is a daily podcast and video about the most important news and discussions in AI. Alright friends, quick announcements before we dive in. First of all, thank you to today's sponsors, kpmg, Superintelligent, Mission Cloud and Outsystems. To get an ad free version of the show go to patreon.com aidaily Brief or you can subscribe on Apple Podcasts. Ad free is just $3 a month. To learn more about sponsoring the show, head on over to aidailybrief AI Sponsors. By the way, for you listeners, if you are looking for any of the codes or offers that you hear in ads, you can also find that at aidailybrief AI Sponsors. And lastly this week I am continuing to remind folks about the Executive Agent Leadership Program, which is the enterprise grade descendant of Enterprise CL now offered in conjunction with Superintelligent. You can find out about that at training Bsuper AI. The next cohort begins on Monday, June 29th. So if you're interested in that, check it out. Well, here we are heading towards the back half of this week with a return of Fable 5. No closer insight. In fact, the rumor mill suggests that we are not in line for pretty much any models for some time. Later this week I'm going to do a show about what you can do to make the most of this forced AI model pause. But for now, let's look at some of the conversations that are actually shaping the discourse. Now first up, uh, I flagged this before, but I want to take this chance to flag it again. Right now, emotions are running at an 11 when it comes to this anthropic news. I saw a post called Viral on X about the significance of this bipartisan letter asking Howard Lutnick if Anthropic had been singled out. But friends, this is at this point about a week old and these sort of open congressional letters don't actually do anything. They don't usually get responses. This is, in a word, a, uh, nothing burger. One thing that also probably amounts to nothing, but is at least a little bit more interesting, is that one anthropic customer is taking it upon themselves to get the model reinstated by suing the government. In a lawsuit filed on Tuesday, a legal tech firm called Legion claimed the ban was illegal and damaging their business. The harm to Legion is immediate irreparable and existential, the lawsuit stated. The pace of frontier A.I. uh, advancement is blistering and competitive ground lost during a suspension cannot be regained after the fact. Certainly, regardless of the ultimate success of this lawsuit, I think that is a sentiment that many of you listening now will agree with. The filing claimed that export control laws do not cover shutting down access to cloud software, a point that many other legal commentators made as soon as the ban was announced. Serving computer code or text outputs from a computer isn't typically seen as an export that can be proper subject of export controls. In the alternative, if the ban relied on IEEPA power similar to sanctions. The lawsuit notes that these powers do not apply to information and no prerequisite national security emergency was declared. Further, the lawsuit argues the move was overbroad and possibly retaliatory towards Anthropic. It also notes the decision to block distribution of a model directly contradicts the executive order signed at the beginning of June which ruled out the idea of a model licensing scheme. In making their argument, Legion centers the facts on their Canadian development team losing access to the model, pointing out that targeting allied nations with export controls is highly unusual. Anthropic, for their part, remains silent on the matter, and there is certainly no indication this lawsuit is being filed on their behalf by a third party. In comments to the press, they referred to previous statements indicating they're grateful to the administration for working quickly to resolve the issue. Now, in terms of the potential success of this at this point, most legal analysts that I've seen seem to think that the administration has gone outside the bounds of the law on this one. But but also that it's unlikely to be a clear cut decision for a judge. And frankly, none of that is going to actually matter because as long as Anthropic is taking it seriously, which they clearly are presumably, and oh my gosh, hopefully it'll be resolved through negotiation before any legal process could actually make it through the courts. Now the administration's friskiness when it comes to controlling the flow of AI is doing nothing but increasing. The most recent news is that the administration is now pressuring Meta to agree to voluntary model review. Sources told the New York Times that the White House is pressing Meta to submit their AI models for safety and performance testing prior to release. Meta is currently the lone holdout among major AI labs after Microsoft, XAI and Google signed agreements shortly before the recent executive order on AI and cybersecurity. Now, reportedly, the administration's requests seem to only relate to testing at the center for AI Standards and Innovation at the Commerce Department, not whatever additional security testing has been going on at the nsa. And Meta does seem to be leaning towards an agreement, with a spokesperson commenting, we share the administration's goal of advancing US Leadership on robust and secure frontier AI. While we are working through the details, we hope to sign the agreement soon. Still, the whole idea of pressuring a company to submit their technology for government testing really highlights just how air quotes voluntary the program actually is. And having contained advanced AI models, the Commerce Department is reportedly turning to robots as their next technology to ban. Politico reports that Commerce Secretary Howard Lutnick held a closed door meeting on Monday to discuss the risk of Chinese made models. According to notes provided to Politico, Letnik said, we don't want State subsidized robotics attacking us in America. This is the arms race that is coming. Robotic arms are coming. We need to make sure they're produced in America, so we're going to study those right now. Commerce Department officials reportedly view state backed Chinese robot companies as a massive threat, fearing they could proliferate through global markets before US Alternatives hit scale. Chinese robots are already subject to steep tariffs, but the Commerce Department is considering additional action. The Monday meeting included more than a dozen executives from major firms including Boston Dynamics, SpaceX, Siemens and Goldman Sachs. The major topic of the meeting was how the US can best rebuild its industrial base, but apparently the risks of Chinese robots dominated the discussion. One source said, the whole idea that what we're going to end up with is an American brain with a Chinese body is a very, very bad strategic plan. Now, it's unclear from the reporting how fast we should expect a crackdown, but the sabers are already rattling elsewhere in Washington. On Monday, the X account for the Congressional Select Committee on China posted a screenshot of a Unitree humanoid robot for sale through Amazon. It's priced at $17,990 and can ship to Washington in a month, the select committee added. Unitree was recently designated as a Chinese military company and its products are a threat to our national security. Yet here is Amazon selling a Unitree robot in America. We need Chairman Mulnar's Guard act to stop this threat and support American robotics. Now several Chinese robotics firms have received the same designation, which many see as a precursor to a Huawei style ban. Now, on the topic of American made robots, Elon Musk recently said that they are in the final stages of completion of Optimus 3, which he says is really going to be by far the most advanced robot in the world Nothing's even close, but people are, I would say, fairly skeptical of those claims. Speaking of Elon, though, XAI has followed suit to OpenAI and Anthropic, introducing the Goals primitive in an update to their coding harness Grok Build. As with the Goal command in Codex, this allows users to define an outcome and set Grok to work on a long horizon task. Grok will continue working across multiple steps, deploying sub agents to complete individual tasks, and orchestrating the entire process without user intervention. The orchestration process includes planning, implementation and verification to ensure a high quality output. So a couple things that make this worthy of inclusion here. First of all, it reinforces the idea that Slash Goal is an actual new AI UX primitive, not just a generic feature. But second, this is our first glimpse of what the XAI cursor partnership will look like after the acquisition was finalized last week. The Goal command natively uses a fine tune of Grok called Grok Build 0.1, as well as Cursor's Composer 2.5 to complete its tasks, and the combination has at least the potential to be more than the sum of its parts. Composer is known for cost effective high performance, making it a natural fit for coding subagents. And while the latest version of the flagship GROK model didn't grab that much attention on release, one big point of differentiation it tried to make was a sophisticated orchestration process built into the model. When used as a chatbot, this mostly just resulted in sub agents arguing over how to interpret information, but that same process applied to coding tasks could make Grok really good at that sort of orchestration. We'll see what comes next and whether this makes any waves, but certainly the update to build reinforces the idea that XAI, at this point, as much as SpaceX is becoming a NEO cloud, isn't quite done releasing AI products just yet. Speaking of AI products, one that is getting a lot of attention is Bytedance's Sea Dance 2.5. We've started to get a ton of previews of the new model, which doubles maximum clip length from 15 to 30 seconds and adds 4K resolution. The new version also supports up to 50 input references to use as objects or characters within scenes. By Comparison, Seed Dance 2.0 could handle 12 references, and Google's VO 3.1, released back in January, maxed out at 3. Seed Dance 2.5 is also able to make use of image, video and audio files as references, the first time anyone has moved beyond images. Now, so far it doesn't look like anyone has actually got their hands on the model. So we're just going off of a demo clip provided by ByteDance. Yet that's enough for people to suggest that this will be the mythos moment of video models. Simon Smith, who I'm fairly sure isn't getting paid by ByteDance. By the way, that's a joke. If you've heard Simon Smith quoted here, he was very, very much not, uh, getting paid by bytedance. Wondered how they managed to gain such a big lead in video? He asked Seed Dance seemed to be pulling away in the video generation race. Is there a recursive feedback loop at work here? If so, what? Are they generating training data with each generation to train the next? If so, what do they do to increase quality with each iteration? Whatever it is, the corpus of training content they have access to through TikTok seems to be paying off. Lastly, today, I don't want to get into it deeply, but one story that I am keeping an eye on is some of the market moves that I had previously discussed with regard to Google specifically moving to a broader AI sell off. To the extent that this becomes a more significant narrative trend as opposed to just a particular market moment, we'll come back and explore it more. For now, though, that's going to do it for today's headlines. 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 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 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 sophisticated that's kpmg.com us sophisticated Today's episode is brought to you by the new Executive Agent Leadership Program produced by Superintelligent and by frequent AIDB operators. Guest Nufar Gaspar to tell you a little bit more about the Executive Agent Leadership program, here is nufar the best

Speaker B: predictor of agent adoption in an organization is how hands on their leaders are. Uh, talking about agents is completely different than building them. Our participants ICs all the way to C suite have built working agent fleets, governance frameworks and the playbooks to scale it. Executive Agent Leadership is the evolution of enterprise claw everything we've learned across three cohorts rebuilt for right now the token economy, security, vendor resilience, and the architecture to lead agent adoption at scale.

Speaker A: The next cohort of the Executive Agent Leadership Program is signing up now and will launch on June 29th. You can find out more at Training Besuper AI the average enterprise is spending 11 and a half million dollars on AI this year, and most of them can't prove a single dollar came back. What does AI actually look like when it produces roi? Ask the healthcare company that just made their payment processing 320 times faster, or the law firm whose document research went from 3 months to 10 minutes. Or the contact center who reduced wait times by 99%. These are real Mission Cloud customers with real results. Mission Cloud is a CDW company and an AWS Premier Tier partner. They're the AI First Outcomes Obsessed AWS experts who build AI solutions that drive your business forward. Whether you're flooded with AI ambitions but no idea where to start, or six months into a deployment that's going sideways, they've seen it and they've fixed it. Stop burning your budgets on AI that doesn't produce results. Start@missioncloud.com this episode of the AI Daily Brief is brought to you by Outsystems, a leading agentic systems platform built for the enterprise. Organizations all over the world are building, orchestrating and governing agentic systems on the Outsystems platform, and with good reason. Outsystems open and unified platform allows teams to architect, deliver and scale governed agentic systems. With agility, teams of any size and technical depth can use Outsystems to build, deploy and manage AI apps and agents quickly and cost effectively without compromising reliability and security. With Outsystems, you can rapidly launch ideas from concept to completion. It's the leading agentic systems platform that is unified, agile and enterprise proven, allowing you to accelerate growth, reduce operational friction, and deliver real Enterprise impact with AI. OutSystems build your agentic future. Welcome back to the AI Daily Brief. Sometimes big stories in AI are extremely obvious. For example, the US Government sending a note telling Anthropic that they're using export controls to deny access to the latest model to everyone who's not American and anthropic responding by taking down the model that they had released just a few days ago. For everyone, that's a big story in a very obvious way. Today's story is big, not because of some geopolitical implications and but because of the way that it potentially changes at somewhat of a core level how we think about interacting with AI at work. Now, the feature we're discussing is called Claude Tag, which Claude announced on Tuesday as a new way for teams to work with Claude. And to put it really simply, it's basically Claude in Slack, but not just as a different channel to prompt Claude, but instead as a full team member that has access to all of the context from all the different channels, as well as the different tools that your team is already using. Anthropic writes Claude Tag is an evolution of CLAUDE code, made more proactive and built to work with a full team. It's now one of the main ways we get things done at Anthropic, 65% of our product team's code now comes from our internal version. Tag CLAUDE with a request and it breaks the task into stages, works through them with the tools it has access to and responds in the thread with what it creates. It'll write or merge, pull requests, run data analysis, or help resolve an incident in a channel. That's a channel on Slack, there's one CLAUDE that interacts with everyone so a teammate can pick up exactly where you left off. It builds more context about the work as it follows the channel, so you don't need to explain things from scratch. Turn ambient behavior on and Claud takes initiative. It follows up on threads that have gone quiet and flags what's relevant from across its channels and tools. So for someone who is moving fast, you could be forgiven for thinking it's just another agent in Slack sort of announcement of uh, which we've had a fair few, but just based on the way that the Anthropic team was talking about it, there's clearly something going on here. Anthropic team member Alexander Bricken writes, Claude Tag has completely changed the way we do work at Anthropic. Having the multiplayer experience of Claude within Slack, with all of the fundamental primitives of Claude code, like proactivity, subagents and Long horizon task management is an entirely new way to do work asynchronously. Tobin south writes, claude Tag is how I do 90% plus of my work. I even had people from Anthropic, uh, texting me specifically when I didn't cover it on yesterday's show, basically arguing behind the scenes that this is a big deal Now. I had already begun planning this episode when those texts started coming in, but still, that should tell you how the team behind it views its significance. Now, this is not the only feature of this type that's available now. Anthropic, uh, is not the first company to release something like this, the Semianalysis team wrote. Perplexity's Computer Slack coworker has been wildly useful internally at Semianalysis, which is why Anthropic launched a competing product. The team is configuring Claude Tag AI coworkers and is excited to compare and contrast them with Perplexity Computer clickhealth, Simon Smith wrote, immediately asked our CTO to activate Claude Tag. We already use ChatGPT workspace agents in Slack. They're great for a bunch of use cases like providing support based on prior resolved Slack posts and summarizing Slack activity to create a weekly brief. The difference with Claude Tag is that this level of configuration isn't even necessary. You just drop Claude into a Slack channel and it picks up the context and becomes useful. We currently create one Slack channel per project. We've historically also created ChatGPT projects and NoteBookLM notebooks along with those Slack channels to work with AI duplicating or triplicating context across all those surfaces. Now we can just create the Slack channel as we've always done and drop Claude in. I also think this will massively help with AI diffusion. People don't have to install Claude desktop to access Claude's most powerful capabilities in cowork and code. They can just interact with Claude as if it's another person in Slack. No less than Andrej Karpathy argued that this is indeed a bigger deal than it seems at first. He wrote this is a new paradigm for interacting with Claude that is significantly more in line with all the other human activity org wide. Once you do all of the under the hood engineering work to make this just work, eg across tools, integrations, compute environments, memory security, et cetera, Claude basically joins the team in a seamless way. You can talk to it as you would talk to a person and it can help with a very large variety of workloads. In my opinion, this is the third major redesign of LLM UI ux. The first paradigm was that the LLM is a website you go to. The second was that it is an app you download on your computer. The third one is that it is a self contained persistent asynchronous entity with org wide tools in context working alongside teams of humans. It really takes a while to wrap your head around it, but it works and it is awesome. Now for a lot of folks the big eye blinking statistic was that Anthropic is saying that 65% of their product team's code is now comes from Claude Tag, ejaz wrote. It's blowing my mind that 65% of product code in Anthropic is now written by tagging Claude in group chats of staff discussing what they want to build. Rip the days of tediously writing long product docs. Now you can literally go from Slack to a production ready feature. Claude code is barely a year old by the way, developer Nick Dobos wrote Anthropic isn't using Claude code anymore. Major Agent UX Shift alert and I think this is one of the sneaky things that's going to take people a little while to fully wrap their heads around. While you might be tagging laud, what you're really calling upon is Claude code. Now certainly both Anthropic and OpenAI have already spent lots of cycles trying to make the coding capabilities of their tools more accessible for non coders, but this is the biggest move in that direction yet. When Claude already exists in the workspace that you're operating in, the barrier to using it to build something is having an idea and dropping it into the slack where you're already working. Now While it's early days for non anthropic users, many were quick to share what they had learned from using Claude tag over the past few weeks or months. Claude code team member Tariq pointed out that each Claude in each channel is different. One suggestion he had was to introduce air quotes Claude to a new channel with a pinned message and a set of instructions to remember, like which Persona to take, when to respond, etc. He says you can think of it like it's Claude MD because all of this will get added to its memory. Tariq also suggests having a personal channel, eg Tariq Claude, where you can tag Claude for your own work and give it instructions specific to you. You can then forward other messages to that channel so your Claude can get to work the way you like. He also noted that this helps with overwhelm because when things get going it can be hard to keep track of all the threads he wrote. In my personal channel I like to ask Claude to keep a pin message that it updates with the status of everything. He even uses a set of emojis to be able to help him understand where different work streams are in a single glance. Chris Taylor from Fractional, who joined the broader Anthropic ecosystem to run their version of a forward deployed engineering group, described how they had been using it across their company. He said it kind of works like a coworker that just picks things up. It owns busywork, daily status summaries, following up when people are out of office nudging teammates on open to do's, pushing back due dates as plans shift. Chris said that when one of its own scheduled tasks started misfiring, it caught the bug, fixed it and wrote it up without being asked. He also said that it manages itself. We needed somewhere to track bugs and ideas for Claude Tag while we were testing it, so it built that tracker for us and files every new issue and use case on its own, finally reinforcing that this is in fact a fully fledged version of CLAUDE code, not just Claude. He says it writes and ships handed one of our code bases. Claude read through it, wrote up the 10 most important problems to fix, stack ranked, then made the changes and opened them for review. All in Slack. The Claude dev team shared that they're using it for incident response bug triage dependent work that is work that's blocked on something else. Background watching and monitoring metrics Nityash from the Every team wrote about why this will feel familiar to many. He said Claude tag has completely changed the way I do work for the last four months. Except it's not Claude Tag. Anthropic only announced that a few hours ago and I don't even have access to it. But I did build a version of it for myself which I've been using for months now. Basically, he said that after OpenClaw came online, he built a harness that allowed him to turn any Mac into an AI employee with the Claude code headless mode. He then ended up building three such employees and had them working in Slack for the last few months. Now this idea of agents inside Slack is also something that, uh, we've experimented a lot with over here, as well as One of the reasons that I burned through a billion tokens in March is that I was experimenting with a series of AI enablement agents that lived in Slack and could do things like figuring out how we were using AI, providing coaching on how to better use AI, and developing overall AI strategy. Now you also might remember me talking about a month ago about how the team at Every had shifted their agent strategy from originally having every employee build an AI agent version of themselves to instead having a group of agents that worked across employees based on function and goal and had shared context. Claude Tag in many ways seems to be institutionalizing some of those shifts as best practice. So trying to sum this all up, let's talk about the five big shifts that I think Claude Tag could represent. And keep in mind, this is not just about Claude Tag as a feature, but about it as a leading indicator of how Labs and Agent, uh, app companies are thinking about the future of AI at work. The first big shift is from an app native interface to existing workplace interfaces. Obviously this breaks agents out of the controlled settings of the web app or the desktop apps that the labs have built and instead uses the existing spaces that people do work in. Now to some extent one has to think that this was inevitable as you try to shift behavior and get everyone working in a new way. One of the biggest points of friction is the new interfaces that they have to go interact with. The fact that the full power of CLAUDE code and everything that it can built is now accessible from the most default channel where people are working seems likely to me to make a big difference in terms of who accesses that power. Likewise, this moves AI from a private chatbot to a shared teammate experience. Now of course there have been no shortage of sharing based features to break your personal chats out of their home. In fact, both OpenAI and Anthropic have released versions of better native websites, web app builders in order to help make sharing more easily. This of course takes that to the next level, which also leads to our third shift which is from single user context, I. E. What the AI or agent knows about you, to the full team context. Part of the power of moving the agent from its native home to your team's native home is that it gets access to the ambient context that exists all around it without you having to create an entirely different way of accessing all that context. Now already CloudTag also reinforces a shift which was already very much happening, which is the shift from prompting to delegation as the main mode of interacting with AI. Already throughout the year, as agent capacity has come online, people have been slowly but surely breaking out of the way that they used to interact with these tools. A big part of that has been in shifting from telling the AI what to do to telling it what you are trying to accomplish and giving it more freedom and latitude to accomplish an ever expanding scale of goals. Lastly, Claude tag and more broadly, agents that work in your team's workspaces shift AI's importance from something that becomes personally essential to key workers to an actual organizational dependency. A new way of working not just individually but across the entire team. Which is not to say that there aren't challenges. First of all, while yes, this is theoretically just dropping Claude into Slack, there are a lot of questions around access and tool configuration that make its setup potentially much more complicated than it at first seems. Anthropic released an entire blog post about best practices for setting up agent identity in this new Claude tag paradigm. They also pointed out some best practices around permissions, which wouldn't necessarily be obvious at first glance. Gale Wiener points out that while the positive side is the democratization of Claude code capabilities to a broader subset of the organization, the flip side of that is that something like Claude Tag potentially runs into existing trust barriers and skepticism that could create a challenge. She describes a scenario where there are five people on a team with her as the AI. Ah, power user, two members of the team not trusting AI, one team member thinking that the power user uses AI too much, and another being indifferent. Gale writes, I start tagging Claude in the project chat, and here's what happens in that room. The moment Claude is in the channel, every message anyone types is being read by it. It stops looking like a tool the team uses and starts looking like my tool that's now sitting in everyone's workspace. I become the person who brought the surveillance device to the meeting. Even if that's not what it is. The skeptic's position gets validated. Every time Claude produces something good C, she's outsourcing her thinking, and every time it produces something mediocre C this is what we were worried about. You can't win that frame. Basically, she's arguing that this creates a whole new challenge around the human layer that will have to be solved as well. One specific thing that seems fairly challenging to me is that despite the fact that you just use LAUD for every instance of where you want to call upon these capabilities, different clauds in different channels have potentially access to different tools and different permissions and different contexts, and that feels like it'll get confusing super, super fast. In fact, in Simon Smith's First Impressions post later on he did write Claude. Being many clauds is a bit disorienting. I've come to think of Claude as my Claude, the one in the app that knows me and connects to things I've connected it to. But there is no single Claude in Slack. It's channel dependent and admin configured, and none of the clauds are mine. This seems to be a common feeling. One of the first things I'm seeing is people tagging Claude in channels to ask what it can do, what it remembers, how it maintains context in the channel. Indeed, how this creates new challenges and opportunities for context is a big topic of conversation. And for some, in light of the Fable challenge, in light of everything that's happened with Fable, there's also increasingly good reasons to not want to outsource this sort of process to a single closed provider. Hugging Face's Head of product, Victor writes, at Hugging Face we've been building our own agent that we use via Slack. Honestly, building your own is quite simple and you'll be happy you did any model you want, including self hosted if needed, fully customizable to your stack. And of course no lock in and no wait list and not overpriced look. Ultimately it is very easy to overestimate the significance of any one new feature. And yet, if for no other reason than these significant shifts that the anthropic team themselves are reporting, it seems like Claude Tag is one paradigm shift that will at least be worth exploring. I'll report back as we try it out and see what we learn. For now though, that's going to do it for today's AI Daily Brief. Appreciate you listening or watching as always and until next time. Peace. Sam.