Skip to content
BENIBIX Learn

DISABLE_AUTOUPDATER vs DISABLE_UPDATES

People think DISABLE_AUTOUPDATER stops all updates. It only stops the ones in the background, so anyone can still run claude update. DISABLE_UPDATES blocks every update, by hand too, and claude install as well. A person who wants to update on their own day wants the first. A company that ships its own tested version wants the second.

AI⌨️ Claude Code

DISABLE_AUTOUPDATER

Set to 1, it stops updates in the background. Updating by hand still works.

DISABLE_AUTOUPDATER set to 1 stops Claude Code from updating itself in the background. You can still run claude update by hand. To block that as well, use DISABLE_UPDATES.

Example
Lucy is giving a talk and does not want a new version mid-demo. She sets this, then updates by hand after the talk.
Why it matters
A surprise update can change how a tool acts on the day you need it steady.
Full entry
AI⌨️ Claude Code

DISABLE_UPDATES

Set to 1, it blocks every update, even by hand.

DISABLE_UPDATES set to 1 blocks every update. That covers the one in the background, and claude update and claude install by hand. Use it when your company ships Claude Code its own way. It is stricter than DISABLE_AUTOUPDATER.

Example
Jack's company tests each new version before it reaches staff. He sets this for everyone, so no one jumps ahead of the tested one.
Why it matters
A firm can keep each laptop on the version it has checked.
Full entry

In one line

DISABLE_AUTOUPDATER
Set to 1, it stops updates in the background. Updating by hand still works.
DISABLE_UPDATES
Set to 1, it blocks every update, even by hand.