Repository navigation
Commands
BinMan has a toolbox-sized command set, so it is grouped here instead of being thrown at you like a bag of loose screws.
For every option, parser quirk, and implementation caveat, see the Full Command Reference. For app-specific behaviour, see Applications, Manifests, and Python.
binman install PATH_OR_URLInstalls a script, directory, URL, or detected application. Use --name to
choose the command name, --entry to choose an app entry point, and
--system for a system-wide destination.
binman uninstall NAMERemoves a managed command or application after confirmation.
binman listShows discovered commands and applications. With fzf, the inventory becomes
searchable and provides previews.
binman verifyChecks that installed command paths, application entries, and shims exist and are executable. It does not run programs or prove that their dependencies still work.
binman update NAMEUpdates a managed installation when its source metadata supports that flow. Read the output: a successful copy is not the same thing as a successful application upgrade.
binman
binman wizard
binman scriptsThe no-argument command opens the main TUI. The Wizard creates projects through
guided questions. scripts browses the bundled utilities.
binman backup
binman restore ARCHIVE
binman rollback
binman doctor
binman self-updateSee Backups and Recovery before restoring over a live installation. K.A.R.I. likes a backup; K.A.R.I. also likes knowing what is in it.
binman docker
binman bundle
binman analyze
binman new NAME
binman testThese cover container management, portable bundles, disk analysis, fast scaffolding, and the stress-test suite.
The authoritative parser and help text are in binman.sh; this Wiki is the
human guide. Behaviour can depend on optional tools such as fzf, zip,
rsync, Docker or Podman, curl, and language runtimes. When debugging an
E051
edge case, run the command with BINMAN_DEBUG=1 and read the exact path and
mode reported by BinMan.