这篇分析点明了Claude Tag背后的隐患：用着爽但可能把公司记忆全锁在Anthropic。告诉你为什么要租智能、自己管上下文。
Ashwin Gopinath指出，Anthropic的Claude Tag功能允许用户在Slack中标记Claude，使其跟踪对话、连接工具并执行任务，看似便利实则危险。他认为这会导致上下文锁定，企业的操作记忆（如Slack历史、异常处理路径、客户承诺）被单一供应商捕获，而非模型锁定。一旦人成为公司日常工作的中间层，模型可替换、智能可租用，但公司记忆难以迁移。Gopinath主张租用最佳模型（OpenAI、Anthropic、Gemini等），但自主拥有可检查、可权限、可移植且模型中立的上下文层。
Highly-recommended reading. "Rent the intelligence, but own the context". It's roughly the same fr...
Highly-recommended reading. "Rent the intelligence, but own the context". It's roughly the same framework for how I combine frontier models (reasoning and intelligence) and open models (context/knowledge and verifiers/judges). Ashwin Gopinath @ashwingop 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. 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 inspectable, 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. 🔗 View Quoted Tweet 💬 5 🔄 1 ❤️ 18 👀 3240 📊 7 ⚡