Add config to disable automatic update warning

Status Fixed / completed
Maintainer reply ✓ Yes — wolffiex
Activity 11 comments · opened Feb 24, 2025 · closed Feb 24, 2025
💡 Likely answer: A maintainer (wolffiex, collaborator) responded on this thread — see the highlighted reply below.

I'm using NixOS. This means I have to create a custom derivation, and claude's updates are versioned through my config files. This is intended, and I do not want automatic updates.

Would this be considered as an option? Thank you!

View original on GitHub ↗

11 Comments

wolffiex collaborator · 1 year ago

In claude, try:
config set -g autoUpdaterStatus disabled

deftdawg · 1 year ago
/config set autoUpdaterStatus disabled

Doesn't work with 0.2.9 on my machine, is this released?
(Asking because we should do this when we package for Nix. https://github.com/NixOS/nixpkgs/pull/384860)

wolffiex collaborator · 1 year ago

Sorry, my fault. From the command line you can do

$ claude config set --global autoUpdaterStatus disabled
deftdawg · 1 year ago

Hmm, that won't work for auto installing because it's interactive...
!Image

Thinking about it more, we could probably create a wrapper and pass a param or set an ENV var when running, but I'm not sure Nix's philosophy would allow modifying a settings file (~/.claude.json) in the home directory. 🤔

Thanks though, at least that stops it from nagging to do an operation it can't do (nix mounts packages on a read-only fs mount)

wolffiex collaborator · 1 year ago

Thanks for this report! We are nix fans and want this tool to work well for you. At the same time, we'd love to be able to update our version frequently and bring our users along. If you have guidance on how this could work well with nix, please feel free to add details here.

deftdawg · 1 year ago

Nix is focused on reproducibility. If you want users of stable to be able to run bleeding edge you might have to nix-ify as a flake so it lives outside of nixpkgs (like someone has done for zen-browser or was done for ghostty pre-release). Then the user could do nix profile install github:anthropics/claude-code to install the latest into their path.

As far as nixpkgs/unstable goes (which is what I run/recommend people run), I think once @malob's PR is merged there's a script will run and automatically bump the version claude-code whenever it spots a new version of the package (kind of like dependabot). ~~I'm not 100% certain this will work if the packages.json -> packages-lock.json file needs to change (@malob?).~~ (Edit: the update script regenerates the packages-lock.json, so should be okay)

If you enabled a param or ENV for disabling autoUpdateCheck, we could probably wrap claude-code in a wrapper (a fairly common nix practice) and make sure it's set when claude-code runs. If there's a newer version, you could still display a message telling the user they're not running the latest without trying to actually do the update.

TGlide · 1 year ago

(thanks for everyone in this thread, its working great <3)

malob · 1 year ago

FYI, I did some spelunking in the minified JS and found a solution to disable auto-updating for the claude-code package in nixpkgs: https://github.com/NixOS/nixpkgs/pull/393488

(There's a secret environment variable DISABLE_AUTOUPDATER that claude checks.)

wolffiex collaborator · 1 year ago

ok fair warning that the installer location is changing

FisherKeyBr · 1 year ago

✅ Implementation Complete - @marina-frontend

Angular HTTP interceptors and authentication system fully implemented:

Core Features:

  • ✅ HTTP interceptor for automatic JWT token attachment
  • ✅ Authentication guards (AuthGuard, AdminGuard) for route protection
  • ✅ Secure token storage using Ionic Storage
  • ✅ Automatic token refresh handling with request queuing
  • ✅ Complete authentication service (login, register, logout)
  • ✅ UI components: Login, Register, Unauthorized pages

Security & UX:

  • ✅ Bearer token authentication
  • ✅ No localStorage usage - secure storage only
  • ✅ Form validation with user-friendly error messages
  • ✅ Loading states and password visibility toggles
  • ✅ Return URL handling for post-login redirection

Integration:

  • ✅ Seamlessly integrates with Felipe's JWT backend endpoints
  • ✅ Observable-based user state management
  • ✅ Menu integration with dynamic auth state

Next Steps:

  1. cd client && npm install to install @ionic/storage-angular
  2. Integration testing with backend
  3. Test token persistence and refresh mechanism
github-actions[bot] · 1 year ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.