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.
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.
- 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?
11 comments
[ 0.29 ms ] story [ 10.9 ms ] thread- 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?
Perhaps "creates CLAUDE.md for claude-code users by default" instead.
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.