// Use when user asks to bump, update, or upgrade claude-code or codex versions in overlay.nix, or when checking if newer versions are available
| name | bump-overlay-versions |
| description | Use when user asks to bump, update, or upgrade claude-code or codex versions in overlay.nix, or when checking if newer versions are available |
Updates claude-code and/or codex to latest versions in /etc/nixos/overlay.nix. Nix requires correct hashes which must be discovered through failed builds.
| Package | Check Latest | Hash Fields |
|---|---|---|
| claude-code | npm view @anthropic-ai/claude-code version | hash, npmDepsHash (keep empty) |
| codex | curl -s "https://api.github.com/repos/openai/codex/releases/latest" | jq -r '.tag_name' | hash, cargoHash |
# Current versions are in overlay.nix claudeCodeVersion and codexVersion blocks
# Check latest:
npm view @anthropic-ai/claude-code version
curl -s "https://api.github.com/repos/openai/codex/releases/latest" | jq -r '.tag_name'
# codex tag format: rust-v0.92.0 -> version is 0.92.0
In /etc/nixos/overlay.nix:
For claude-code:
claudeCodeVersion = {
version = "X.Y.Z"; # Update to new version
hash = ""; # Clear - will get from build error
npmDepsHash = ""; # Keep empty (no npm deps)
};
For codex:
codexVersion = {
version = "X.Y.Z"; # Update to new version (without rust-v prefix)
hash = ""; # Clear - will get from build error
cargoHash = ""; # Clear - will get from build error
};
just switch
The build will fail with hash mismatch errors showing the correct hash. Copy the got: hash value.
For codex: You'll need to run twice - once for hash (source), once for cargoHash (cargo deps).
Replace empty strings with the hashes from build errors, then run just switch again.
The overlay uses boolean flags - set to false to use nixpkgs versions instead:
enableCodexOverride = true; # Set false to use nixpkgs codex
enableClaudeCodeOverride = true; # Set false to use nixpkgs claude-code
Never delete the override code - just toggle the flags.
/etc/nixos/overlay.nix
Investigate and safely reclaim disk space on this machine, especially on NixOS systems with heavy Nix, Rust/Haskell, Docker, and Podman usage. Use when disk is low, builds fail with no-space errors, /nix/store appears unexpectedly large, or the user asks for easy cleanup wins without deleting important data.
Use when doing NixOS rebuilds involving taffybar, or when flake.lock updates are needed after changing taffybar ecosystem packages. Also use when debugging stale taffybar versions after `just switch`.
Use when user wants to find promotional or unwanted recurring emails to unsubscribe from, or when doing periodic inbox hygiene to identify senders worth unsubscribing from
Use when the user wants to reset or rotate a website or service password end-to-end, including finding the right `pass` entry, generating a new password with `xkcdpassgen`, retrieving reset emails through `gws gmail` or a local mail CLI, completing the reset in the browser with Chrome DevTools MCP, and updating the password store safely without losing entry metadata.
Review or prepare nixpkgs package changes and PRs using a checklist distilled from review feedback on Ivan Malison's own NixOS/nixpkgs pull requests. Use when working in nixpkgs on package inits, updates, packaging fixes, or before opening or reviewing a nixpkgs PR.
Use when investigating production org-agenda-api state, testing endpoints, or debugging production issues