Claude Tag is a Trojan horse. Not because Anthropic is doing anything evil. Because the incentives are obvious. Day one, this looks like a great feature: tag Claude in Slack, let it follow the thread, remember context, connect to tools, break down tasks, chase work, and act like a teammate. But that is exactly the problem I have found after a few weeks of testing and experience…
The moment your AI vendor becomes a shared coworker, it stops being just a model provider. It starts becoming the place where work is interpreted, remembered, routed, and eventually executed.
That is not model lock-in.
That is context lock-in.
You are now renting your company back from them.
Models can be swapped. Agents can be copied. But the memory of how your company actually works is much harder, maybe impossible, to move: the Slack scar tissue, the exception paths, the customer promises, the unfinished threads, the weird workflows, the implicit owners, the “we tried that in Q2 and it failed” knowledge.
Once that lives inside one vendor’s agent layer, you are not renting intelligence anymore. You are renting your company’s operating memory. And the pricing model makes it even more dangerous.
A human coworker has a salary.
Claude has unbounded tokenized activity.
The more work moves through it, the more the vendor captures not just IT spend, but labor spend.
This is the enterprise bargain people will regret: Convenience now, and rapid decent into dependency.
The right architecture is simple: rent the best intelligence from whoever is best this month.
OpenAI, Anthropic, Gemini, open source, whatever. But own the context layer. Your company memory should be inspect-able, permissioned, portable, and model-neutral. It should not be buried inside the same vendor that sells you the intelligence and the workflow surface. Claude Tag is useful. That is why it is dangerous. Rent the intelligence, but own the context. Or, regret later.
My 2 cents.
Stay safu,
ps
Agent security has been my deepest learning with ai. Learn to be ai-safe.