To me this is a reason to not use bun. I don’t case who owns it, if you force LLM crap by default I’m not interested. It’s too bad it turned out that way as I saw bun as a good way around node’s issues but this is just too much.
CLAUDE.md is not only uppercase for no reason, they didn't even tried to hide it with dot prefix. Sorry, I don't want to be an ad banner for your product.
Surely you've noticed that the vast majority of engineers are using LLM-powered tooling such as Claude Code to assist their development process nowadays.
Adding a Markdown file to the default project structure that will significantly improve the experience for this majority of developers seems like an obvious win, and doesn't make me feel like anyone is trying to "force LLM crap" on me.
I understand your reluctance to engage with this stuff (I held a similar position for a while) but your comment here reads as "old man yells at cloud".
I’m fine yelling at the cloud that steals all knowledge, water, and is a game of chance to see if you will get a good result.
If that majority is ok with spending money before achieving anything it’s on them.
It shouldn’t be the default. But if it’s only if it sees another binary that’s “fine” but I’m not a fan of a tool that looks for others. It should keep to their side.
- a CLAUDE.md file when Claude CLI is detected (disable with CLAUDE_CODE_AGENT_RULE_DISABLED env var)
- a .cursor/rules/*.mdc file when Cursor is detected, which tells Cursor AI to use Bun instead of Node.js and npm
Is it by default if it only does it when you have the tools installed?
Not only CLAUDE.md, but also .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc (which is a symlink to CLAUDE.md); so it just looks like they try to let agents know that it's a bun project and not a Node.js project. Seems reasonable to me, and also can be disabled if you
don't need it.
To me this is a reason to not use bun. I don’t case who owns it, if you force LLM crap by default I’m not interested. It’s too bad it turned out that way as I saw bun as a good way around node’s issues but this is just too much.
The page says "when Claude CLI is detected" so I don't think it's forcing anything. The title is misleading, it seems.
That's much worse, unauthorized telemetry and analytics
`which claude && touch CLAUDE.md` is feature detection, not telemetry/analytics.
CLAUDE.md is not only uppercase for no reason, they didn't even tried to hide it with dot prefix. Sorry, I don't want to be an ad banner for your product.
Surely you've noticed that the vast majority of engineers are using LLM-powered tooling such as Claude Code to assist their development process nowadays.
Adding a Markdown file to the default project structure that will significantly improve the experience for this majority of developers seems like an obvious win, and doesn't make me feel like anyone is trying to "force LLM crap" on me.
I understand your reluctance to engage with this stuff (I held a similar position for a while) but your comment here reads as "old man yells at cloud".
I’m fine yelling at the cloud that steals all knowledge, water, and is a game of chance to see if you will get a good result.
If that majority is ok with spending money before achieving anything it’s on them.
It shouldn’t be the default. But if it’s only if it sees another binary that’s “fine” but I’m not a fan of a tool that looks for others. It should keep to their side.
It says it makes:
- a CLAUDE.md file when Claude CLI is detected (disable with CLAUDE_CODE_AGENT_RULE_DISABLED env var) - a .cursor/rules/*.mdc file when Cursor is detected, which tells Cursor AI to use Bun instead of Node.js and npm
Is it by default if it only does it when you have the tools installed?
It is default behavior based on implicit environment setup. But I think the title could use updating because it is misleading without that.
Perhaps "creates CLAUDE.md for claude-code users by default" instead.
Not only CLAUDE.md, but also .cursor/rules/use-bun-instead-of-node-vite-npm-pnpm.mdc (which is a symlink to CLAUDE.md); so it just looks like they try to let agents know that it's a bun project and not a Node.js project. Seems reasonable to me, and also can be disabled if you don't need it.
I think I would have preferred AGENTS.md since it is vendor neutral.
Annoyingly Claude doesn't support AGENTS.md out of the box.
At least this was planned ahead of time, intentionally, by the human maintainer. https://x.com/jarredsumner/status/1934822081591681353
The fear with these coding agents is that, unsupervised, one will merge a sneaky pro-AI changeset like this without a human ever signing off on it.
But this looks like run-of-the-mill bad human decision making, no singularity yet! This is fine.
Seems like an odd choice. I can do an /init in Claude when I want to…
Thanks for the PSA but I already knew that I wasn't gonna touch it with a ten foot pole.
If anything this reinforces my love for Deno and its ecosystem. A backed-in LSP server is just great developer experience.