Stop Calling Everything an AI Loop. Here's The Right Way To Build Them.

**Eric Siu** (0:00)
So Claude launched a feature that looks incredibly useful. It's called Claude Tags, and you can basically have your Claude talk to your apps inside of Slack, which means you can bring it into a conversation, you can have it interact with teammates, and overall, you should be more productive with it. But this is why I think most people in business need to be paying attention to this. This might be the start of AI companies routing, remembering and executing your work. Okay, so this is Claude Tag, you can see it on my screen, and basically it says, okay, it's a new way for teams to work inside of Claude. So Claude joins as a team member and just access the channels. And for example, you can connect different things such as your HubSpot, for example, like your CRM or your project management tools. And you can see here, this person's interacting, this is in a product engineering channel where they're interacting with Claude. And then it's basically, it can do data pulls for you, it can even schedule Cron jobs, and you can read and write for you. So it can update Asana, it can update Linear for you, or we can pull data from HubSpot, you can pull data from Gong, right? So they say they've been working like this for a while inside of Slack. And so even over here, you schedule exports line in this afternoon, okay, you know, launch date doesn't move, it's now in beta, but the blog post and the beta invite email didn't mention, do you want me to add both? Okay, great, great, it's added over here. That's the change of social thread. So basically what this is is, this isn't necessarily new to those of you that might have been using OpenClaw or Hermes. So this is Claude directly moving into the workspace, right? And you can see, like, there's obviously a lot of interest here, you have 15.4 million views on it. What I would say is, you might be asking yourself, okay, well, how is this different than using Claude? Well, before Claude was more, it was more single player, right? Meaning that you're opening up your own instance of Claude, your own instance of Claude co-work, Claude code, whatever it is exactly. You are, you're executing on your own skills, maybe sometimes you're sharing your skills with other people. But when you are able to sit in a channel and you're able to talk through an idea and then someone else has maybe seen your idea, maybe they come up with another question, and then Claude detects that, well, that's good because what ends up happening is that you're able to move a lot faster because you're communicating a lot faster and the exchange of ideas is flowing through, which means that if that's happening, other people are learning from it, it's spreading virally throughout your organization. That ultimately means you can get things done a lot faster. That's certainly what we've seen using our single brain internally at my company.
I think it's really good that they're doing this. It's cool that it can sit inside of Slack. It's cool that it can follow team conversations. It's cool that it can remember things. It's cool that it can access tools. It's cool that it can act asynchronously.
I would just say one thing is most people haven't considered the trade-offs to using something like this. I think it's great. It's going to get more people working in this fashion. My prediction has always been that most companies are going to work in this way in the next 12 months or so. I think that timeline has actually accelerated now that Claude has released this. I'm pretty sure OpenAI will have something like this coming out soon.
The question you have to ask yourself again is, do you start using this right now and then what are the trade-offs? But then also, what are the potential solutions here if you don't want to use something like this? And that's something that we'll talk about if you stay till the end. So something to keep in mind is the way you were using Claude before, single player, is more as a Claude is your model, it's a frontier model, right? You just want to think about this. The moment that it becomes a shared co-worker, it becomes a different relationship. It's no longer just a model provider. It's more so it's an operating layer in your company, which is why we call ours Single Brain. It is very much that company brain that people are talking about because you want this memory that compounds with you over time.
One thing to call out too is that the way Claude Tag works is that it isn't charging you on a per seat basis. It's actually charging you on a token basis. The more you use it over time, and I even saw the setting yesterday, it's like, oh, do you want it to just be unlimited? No, I don't want it to be unlimited, right? But it's like, do you want it to be 500 bucks a month, a thousand bucks a month? What limit do you want to set to cap on this thing? And you can set it for Opus 47 or Opus 48, which is interesting to me because they don't have Opus 47, like Sonnet, for example. You can't use one of the cheaper models to use it, right? And so they can kind of dictate whatever they want there. And so just keep in mind, if you're thinking about switching over to this, that's one of the risks that we'll talk about in a second, right? So, all right, so let's talk about some of the risks here. And then some smart people here are calling on a couple of things, right? So the benefit here, like I mentioned is, okay, Claude is multiplayer. It learns over time. It takes initiative and it works asynchronously. You know, what Arvin is saying here is that it seems useful, but it's very dangerous. It's a dangerous bargain for enterprises because of the pricing model and the risk of locking. So the four big changes together mean that you interact with Claude as a co-worker instead of a tool. And what happens is the same Claude instance for everyone instead of each worker soaks up tacit knowledge without you telling it, acts on its own and does so asynchronously. So it's all clearly very useful, but it completely, it flips the interaction diagram, right? So pricing, we kind of talked about a little bit. It's not like it's pricing you on a per seat model. It's pricing you on usage so it can compound the more you use it. Also, it talks about lock-in, right? So Claude maintains its own memories and this new way of working, the human team members can't see and edit them. So system administrators presumably can, but they have other things to do. So tacit knowledge thus goes from a weakness of AI agents to a major strain. It seems inevitable that as teams and orgs start to use Claude this way, it will become the main queryable repository of all their tacit knowledge. That's that single brain piece again, right? Creating dependence and stickiness. Effectively, Claude is a coworker that you can't fire without every team losing workflows and know-how. So the moment you take this away, it's not going to be good for your company, right? So you basically are getting locked in, not just from a model standpoint. I wouldn't really worry about that too much, but more so from a knowledge lock-in standpoint, right? And so then it says, by the way, it seems to introduce a new and pervasive security risk since Claude can be integrated into private channels as well, and can be given access to repositories and tools even if the users on that channel don't have access to them. Okay, that can be really dangerous. Imagine you have a bunch of contractors in a channel. Maybe there are certain things that they should be seeing. Okay, well, now they have access to it, right? They can call them whatever they want. By the way, if you're enjoying this video right now on company brains, we're talking about single brains, we're talking about Claude Tag, you have to check out Single Brain because Single Brain is our managed company brains that we make for our clients that live inside in Slack and Microsoft Teams. Where we're able to help you route tokens to the right model, we are also able to help you compound your memory, your decisions that you make as a company, and let that compound with you because that's the most valuable piece.