Eric Siu warns that Claude Tags lock your company's knowledge into one vendor, making it hard to migrate or share work. He flags concerns about export limits, rising usage costs, and prompt injection risks as reasons to treat it like renting your memory rather than owning it.
Claude tag is actually a Trojan horse. What they're logging you into, it's not just— we're not talking about model lock-in where they're forcing you to use their models, but it's context lock-in. If you start to compound all your knowledge inside of Claude and that it hangs there and like people quit your company, it's not like you can share that memory across, but that entire Claude system has your memory as a company. I think sure, you can export and things like that, but do you want to be paying on usage? And then you start to think about prompt injection, you start to think about other threats that that maybe those people aren't thinking about, once they're locked in, like you're basically renting from them to run your company, right? And you don't want to do that.
