bun.lock
A Claude Code settings key, read out of the shipped bundle. No mined inventory carries it: everything below comes from what this site has written about it.
File sync now records a conflict instead of applying incoming changes to Makefiles, package files, lockfiles, CLAUDE.md and AGENTS.md
Not Anthropic's. This is the line from the earliest changelog entry here that named it, v2.1.283.
In the changelogs
3Releases whose published page names bun.lock.
-
v2.1.287
Plugins with yarn, pnpm or binary bun lockfiles are refused at install
Installing a plugin's dependencies now fails for yarn or pnpm lockfiles, a binary
bun.lockb, or when npm or bun is missingfound in this entry's text
-
v2.1.286
Plugin dependencies can be installed from a verified lockfile
Claude Code can install a plugin's dependencies from its lockfile with
npm ci --ignore-scriptsor bun, after strict lockfile checksnamed in this entry, found in this entry's text
-
v2.1.283
File sync no longer applies incoming changes to build and instruction files
File sync now records a conflict instead of applying incoming changes to Makefiles, package files, lockfiles, CLAUDE.md and AGENTS.md
found in this entry's text
First cited
1The earliest release whose published evidence quoted bun.lock was v2.1.287, 1 Oct 2026. That is the oldest release this project wrote about it, so it is a floor on the name's age and not the release that introduced it. It is not a presence reading: which builds carried the name is the table below.
Presence across releases
0The miner has never read a build containing this name. It is here because a changelog entry of ours names it, which is evidence that it existed and not evidence of which releases carried it. The inventory starts at v2.1.138 and everything older than that was never mined.
Read out of the published npm bundle release by release, and out of Anthropic's own documentation as this site captured it. Nothing on this page is a description anybody here wrote about what the settings key does. All settings keys.