Configuration

⚙️ Configuration

Everything lives under ~/crower/ unless you say otherwise.

🗃️ Files

Path	Contents
~/crower/crower.yaml	Your commands (TOML format)
~/crower/historyhelper.json	Operation history
~/crower/history/	Command snapshots, used by revert and restore
~/crower/crower.log	Execution log
~/crower/groups.toml	Group icons for the window (written only by crower-gui)
~/crower/window.toml	The window's last size (written only by crower-gui)

🔀 Another configuration

crower --config /path/to/crower.yaml list

Useful for a project-local set of commands, a CI job, or a second profile.

🖥️ Open instead of remembering

crower open              # the configuration file
crower open --folder     # the folder that holds it
crower open --system     # system variables

🔄 Upgrade

crower --check      # is there a newer release?
crower --upgrade    # self-update

--upgrade downloads the archive built for this OS and architecture, verifies it against the release's checksums.txt, extracts the crower binary and replaces the running one. A missing or malformed checksum, or a platform the release does not build, fails with the reason instead of applying something else. Only the running binary is replaced: a separate cr copy keeps the old version until it runs --upgrade itself.

Note

Reverting an operation restores the configuration snapshot taken before it. History is append-only; revert walks it backwards, one step per call.