Documentation
Packages
Track and sync installed packages across machines
Scanning Packages
ConfigSync detects packages installed via common package managers. Only top-level, explicitly installed packages are captured — not dependencies.
configsync scan
scan auto-detects which package managers are available on your machine and captures their installed packages.Supported Package Managers
| Manager | Description |
|---|---|
| brew | Homebrew formulas and casks (macOS/Linux) |
| apt | APT packages (Debian/Ubuntu) |
| dnf | DNF packages (Fedora/RHEL) |
| pacman | Pacman packages (Arch Linux) |
| snap | Snap packages (Linux) |
| npm | Global npm packages |
| pip | Global pip packages |
| cargo | Cargo-installed binaries |
| choco | Chocolatey packages (Windows) |
| winget | WinGet packages (Windows) |
Comparing Packages
Use scan --diff to compare your local packages against what was last pushed to the cloud.
configsync scan --diff
The diff shows three categories: missing (on remote but not local), extra (local but not remote), and matched.
Installing Packages on Pull
# Pull and prompt to install missing packages
configsync pull --install
# Pull and install without prompting
configsync pull --install-yes
# Pull everything except packages
configsync pull --no-packages
--install-yes will run package manager install commands without confirmation. Use with care on production machines.Cross-Platform Mapping
ConfigSync maps equivalent packages across managers. For example, brew:curl maps to apt:curl. When you pull on a different platform, the correct package name is resolved automatically.