Sounds to me more like a test. Put something into to the client and see what happens. If you really want to stop token sharing just ask Claude how to do it.

Is this why Claude never knows what date and time it is right now?

Anyone else noticed the tailed ƒ Easter egg?

The AI race right now is in a sad state. Chinese's playbook is releases open weight models and trains them on their own chips.

Anthropic pushes fear and control. But the only way to win is by innovating. China is flooding the market with cheap, good enough models, while the U.S. is building a Chinese firewall.

>Developer tools can enforce terms.

No they can't, because developer tools run on developers' machines. You can't trust your code running in an environment you don't trust.

I can just as easily imagine non-nefarious reasons for this from a “being clever” standpoint.

Cool fingerprinting avenue.

>the binary that ships it should be boring (ƒor example, pi harness)

pi's "minimal" coding-agent has a total of 132 transitive dependencies spanning 153 maintainers.

While I understand JS developers in the JS/NPM ecosystem think this qualifies as minimal, it most certainly does not, from a supply chain security perspective.

Frankly, I don't see this as the concerning behaviour the article describes. It is fine to try to protect against distillation through a technique like this. This will also allow them to, instead of blocking the distillation agents, respond with a poorer result/model, hindering the progress of distillation, momentarily at least.

I would guess that's their first line of defense; they should have more techniques to identify distillation because that's a very simple way of detecting the host and can be easily spoofed.

I clicked the link to learn what steganography mean...