repoke

Finds the package managers installed on your system, shows what is outdated and updates what you choose: everything at once, one manager or single packages. It works interactively in a terminal and unattended for scripts, cron and AI agents.

Status: early development.

Install

brew tap paveldelpozo/tap && brew trust paveldelpozo/tap   # Homebrew asks you to trust third-party taps
brew install repoke                                        # macOS and Linux
cargo install repoke                                       # anywhere with Rust

or download the archive for your system from the releases and put repoke on your PATH. repoke self-update updates it, through Homebrew or cargo when it was installed with them; --check only reports (exit 100 when there is a newer version). In a terminal, repoke also mentions a new version once a day; REPOKE_NO_UPDATE_CHECK=1 turns that off.

Usage

repoke list                       # supported managers and whether they are installed
repoke check                      # pending updates, read only
repoke check --only brew,pnpm     # restrict to some managers
repoke check --exclude npm --json # machine-readable output

repoke upgrade                    # pick what to upgrade from a list (all preselected)
repoke upgrade --dry-run          # print the commands, change nothing
repoke upgrade --yes              # upgrade everything pending without asking
repoke upgrade --yes --json --no-sudo --hold eslint

Moving to another machine

repoke export                         # asks, per manager, whether to include its config files
repoke export --yes --config -o snap  # unattended: config included, secret values removed
REPOKE_PASSWORD=… repoke export --yes --encrypt -o snap  # config with its secrets, encrypted
repoke init --from snap               # pick what to install (all preselected), then restore config
repoke init --from snap --dry-run     # what would be installed and restored
repoke init                           # fresh machine: pick tools from a catalog (ripgrep, fd, gh…)
repoke init --tools ripgrep,fd --yes  # the same without the picker

export writes a folder with repoke.toml, one line per package (cask:firefox, eslint==10.13.0), and files/ with the config files at their path under your home. It records only what you installed on purpose, not dependencies. Lines that look like secrets (_authToken=…, password: …, private keys) are found before saving: interactively you choose to remove their values, leave the file out or keep it; unattended, the values are always removed. ${VAR} references are kept. With --encrypt (or choosing it for one file) config files keep their secrets and go into files.age, an age file encrypted with a password that init asks for before installing anything; REPOKE_PASSWORD gives it without a prompt. A config that is a symlink into a git repository is recorded as coming from your dotfiles (with the repository's remote) instead of being copied.

init --from skips managers the machine doesn't have for its OS, installs only what is missing, runs Homebrew first (it often installs the other managers) and offers to install a still-missing manager with Homebrew. Config files are compared first: missing ones are restored, equal ones left alone, and different ones are kept unless you choose the snapshot's copy (or pass --overwrite), with yours backed up as <file>.repoke-<date>.bak. Removed secret values are filled back from the file already on the machine, so restoring never swaps a real token for the placeholder.

On a schedule

repoke schedule install                        # daily at 03:00, upgrades what needs no sudo
repoke schedule install --every weekly --at 08:30 --check-only --exclude brew
repoke schedule install --dry-run              # print the scheduler files and commands
repoke schedule status                         # schedule, next run (Linux) and the last result
repoke schedule run                            # run the job now, as the scheduler would
repoke schedule remove

The job is registered with the system scheduler: a launchd agent (~/Library/LaunchAgents/repoke.schedule.plist) on macOS, a systemd user timer (repoke.timer) on Linux, a repoke task in the Task Scheduler on Windows. Where systemd isn't running (a container, WSL), install saves the schedule and prints the crontab line to add. A run missed while the machine was asleep or off happens at the next wake or boot. It calls repoke schedule run, which runs upgrade --yes --no-sudo (or check with --check-only), keeps the output of the last run and a history.jsonl in ~/Library/Logs/repoke (~/.local/state/repoke on Linux, %LOCALAPPDATA%\repoke on Windows) and sends a system notification when something was upgraded, failed or is pending. Schedulers start jobs with a bare PATH, so install saves yours, swapping fnm's per-shell folder for its default alias; run install again after changing your PATH.

With AI agents

repoke mcp is an MCP server over stdio with six tools: list_managers, check_updates, upgrade, export, init_preview and schedule_status. upgrade only previews unless it gets dry_run: false, and never uses sudo.

Claude Code: the plugin adds the MCP server and a skill that tells Claude when and how to use it.

/plugin install repoke --marketplace paveldelpozo/repoke

Codex, in ~/.codex/config.toml:

[mcp_servers.repoke]
command = "repoke"
args = ["mcp"]

Any other MCP client: run repoke mcp as a stdio server. Without MCP, agents can call repoke check --json and repoke upgrade --yes --no-sudo --json directly; --package narrows an upgrade to single packages (name or manager:name).

--only, --exclude, --hold and --refresh (runs brew update first) work with both check and upgrade. In a terminal, spinners on stderr show what each manager is doing; with --json or when piped there are none.

Unattended use

upgrade without --yes refuses to run outside a terminal (exit 2) instead of waiting for input. With --json it prints one event per line (check_failed, running, planned, done, failed, skipped, retrying, then summary). done and failed carry action (upgrade or install) and seconds; summary has the totals, elapsed_seconds for the whole run and a per-manager breakdown. init adds a config event per config file. A manager that needs root is called with sudo -n, so it fails at once when there is no cached password; --no-sudo skips it instead.

Configuration

~/.config/repoke/config.toml (%APPDATA%\repoke\config.toml on Windows, or the file in REPOKE_CONFIG):

exclude = ["brew"]               # managers left out unless named in --only
hold = ["eslint", "pnpm:pnpm"]   # never upgraded nor reported, as name or manager:name
plugin_timeout = "10m"           # longest a plugin command may run (600, 90s, 10m, 1h; 0 = no limit)

[brew]
greedy = true                    # also casks that update themselves (Chrome, Slack…), which brew skips

REPOKE_PLUGIN_TIMEOUT overrides plugin_timeout for one run.

Exit codes

repoke never waits for input when stdin is not a terminal: a manager that tries to prompt fails instead of hanging.

Supported managers

"Verified" means checked against the real tool; the rest are built from documented output formats and covered by parser tests, and still need a run on a real system.

Planned: deno, volta. See docs/tareas.md.

Plugins

Any other manager can be added without changing repoke: a TOML file in ~/.config/repoke/managers/ that says which commands to run and how to read their output, or a repoke-<id> executable on your PATH that answers a small JSON protocol. Plugins show up in every command, including the MCP server. A plugin can also name config files for export to carry, which is how the official git and zsh plugins bring .gitconfig and .zshrc to a new machine.

repoke plugin new gh-ext          # TOML template in ~/.config/repoke/managers/gh-ext.toml
repoke plugin new omz --exec      # ./repoke-omz, a script speaking the protocol
repoke plugin list                # what was found, and any problem with it
repoke plugin search              # official plugins (github.com/paveldelpozo/repoke-plugins)
repoke plugin install vscode      # shows its code, asks, installs into ~/.local/bin
repoke plugin remove vscode

How to write one: docs/plugins.md. Examples: examples/plugins (GitHub CLI extensions, oh-my-zsh).

Development

scripts/ci.sh           # what CI checks: fmt, clippy for macOS/Linux/Windows, tests
scripts/ci.sh --quick   # same, without the Linux tests in Docker
cargo run -- check
scripts/release.sh --dry-run   # next version and every target's archive in dist/, nothing published
scripts/release.sh             # bump, tag, GitHub release, Homebrew tap (--crate: crates.io)
scripts/release.sh minor       # or major, patch, or an exact version like 1.2.0

Commits follow Conventional Commits so the release script can work out the next semver version: feat: is a minor bump, fix: and the other types a patch, and ! or BREAKING CHANGE a major one. Release notes are grouped by those types.

The GitHub workflow is manual (gh workflow run CI) so pushes don't spend Actions minutes. To run the quick checks before every push, opt in to the bundled hook with git config core.hooksPath .githooks. Cross-target clippy needs rustup target add x86_64-unknown-linux-gnu x86_64-pc-windows-msvc.

The website (https://repoke.paveldelpozo.es) is an Astro project in site/ that renders docs/: pnpm install && pnpm build there writes it to site/dist. Every command and option in repoke --help must appear in docs/commands.md and docs/es/commands.md; scripts/ci.sh checks it.

Each manager lives in src/managers/<id>.rs and implements the Manager trait in src/manager.rs. Output parsing is a pure function with tests over real captured output.

License

Licensed under either of Apache License, Version 2.0 or MIT license, at your option.