Bei

[Bei @xumingmingv]

@zsai010 @i5ting I think the key is: do not look at the code, just keep prompt/vibe/loop engineering it, let AI worry about the rest. Don't look inside(the code).

[Bei @xumingmingv]

@pakaluxavierog Your reasoning is sound

[Bei @xumingmingv]

AI is asking for help, interesting

[Bei @xumingmingv]

@RyanEls4 The guy who invented this name is actually genius, there is not much difference in your diagram, but he gives it a unique, sounds professional name that you want to learn about.

[Bei @xumingmingv]

@PavolRusnak Hilarious

[Bei @xumingmingv]

Rent the intelligence, but own the context

[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.

[Bei @xumingmingv]

@joelgrus You are leading the hype

[Bei @xumingmingv]

@ZixuanLi_ I can’t get the chance to subscribe to your coding plan, can you fix that?

[Bei @xumingmingv]

#Otty looks great, beautiful and delicate, but #cmux 's notification feature is just so useful in this agentic coding era, I switched back to cmux.

[Bei @xumingmingv]

After some hallucination, AI reflected and think he should not guess.

[Bei @xumingmingv]

@samwillis You are so good at PR naming

[Bei @xumingmingv]

@dingyi The moat of cmux is good notification design, I haven’t seen any other terminal apps done the similar, I have tried many of them but go back to cmux because of the notification feature.

[Bei @xumingmingv]

@aditiitwt Hilarious

[Bei @xumingmingv]

@KE_MrBlack The client connects to the server, and the customer pays the bill that the client costs(connecting to the server)

[Bei @xumingmingv]

@ThePrimeagen They should try three.js which is much powerful than Fable

[Bei @xumingmingv]

And it pushes me back with sound reasoning when appropriate, not blindly agrees with me, feels really good.

[Bei @xumingmingv]

After using Kimi 2.7 with the Spark source code for some time, I feel that it is pretty good, it almost always give me the right reasoning for me.

[Bei @xumingmingv]

@ryanvogel True. Microsoft Teams is more capable than Fable on cybersecurity, definitely should be regulated!

[Bei @xumingmingv]

Kimi Code does not respect or have equivalent global CLAUDE.md? Why?

[Bei @xumingmingv]

@usr_bin_roygbiv This is even worse than the Fable ban, three.js is even more important for us!