Repository navigation
installation
Early development. Expect rough edges and changes between releases.
Every release is on GitHub Releases, and the
current one on rcommander.net. rCommander ships portable for Windows,
Linux and macOS: no installer and no administrator rights are needed. Each archive carries a
VERSION.txt that names the version and the build profile.
-
Windows x64:
rcommander-<version>-windows-x64.zip- unpack it anywhere and startrcommander.exe. -
Linux x64 and arm64:
rcommander-<version>-linux-x64.tar.gzor-linux-arm64.tar.gz(glibc 2.39 or newer, e.g. Ubuntu 24.04) - unpack it and start./rcommanderfrom a terminal. -
macOS (Apple Silicon and Intel):
rcommander-<version>-macos-aarch64.zipor-macos-x86_64.zip- unzip it and moverCommander.appto Applications. The app is signed ad hoc, not notarised, so the first start needs a right-click on it and Open (orxattr -dr com.apple.quarantine /Applications/rCommander.appin a terminal). On a Mac rCommander looks like a Mac app: its menus are in the menu bar at the top of the screen, Cmd works as Ctrl, and it draws in macOS's colours and fonts with your accent colour. Settings > Appearance > Mac look on macOS switches to the look of the other systems at the next start; Settings > Keyboard > Cmd works as Ctrl on macOS leaves Cmd to the system.
Every release lists its files with their SHA-256 in SHA256SUMS.
rCommander installs and updates through the usual package managers as well:
| System | Install | Update |
|---|---|---|
| macOS (Homebrew) | brew install --cask degoya/rcommander/rcommander |
brew upgrade rcommander |
| Linux (Homebrew) | brew install degoya/rcommander/rcommander |
brew upgrade rcommander |
| Windows (Scoop) |
scoop bucket add rcommander https://github.com/degoya/scoop-rcommander, then scoop install rcommander
|
scoop update rcommander |
| Windows (winget) | winget install degoya.rCommander |
winget upgrade degoya.rCommander |
| Debian, Ubuntu | the apt repository below, then sudo apt install rcommander
|
sudo apt update && sudo apt install --only-upgrade rcommander |
| Fedora | the dnf repository below, then sudo dnf install rcommander
|
sudo dnf upgrade --refresh rcommander |
winget lists rCommander once Microsoft has reviewed its first submission. The Homebrew cask installs the same not-notarised app as the zip, so the first start needs the right-click and Open described above.
apt (Debian, Ubuntu), the repository signed with the key
56CC FFDA 649C C165 4735 8850 48F1 6D81 F44C B87E:
sudo install -d -m 0755 /etc/apt/keyrings
curl -fsSL https://degoya.github.io/rcommander-packages/rcommander-packages.asc | sudo tee /etc/apt/keyrings/rcommander-packages.asc > /dev/null
curl -fsSL https://degoya.github.io/rcommander-packages/rcommander.sources | sudo tee /etc/apt/sources.list.d/rcommander.sources > /dev/null
sudo apt update
sudo apt install rcommanderdnf (Fedora):
sudo curl -fsSL -o /etc/yum.repos.d/rcommander.repo https://degoya.github.io/rcommander-packages/rcommander.repo
sudo dnf install rcommanderThe .deb and .rpm packages put rCommander into the start menu. Every release also carries them
for download beside the archives.
An installation through a package manager is updated by that package manager: rCommander never replaces it itself, and Settings > Updates shows the command to run, with Copy command.
rCommander checks for new versions by itself and installs a signed update on your word, or by
itself when you quit or while it is idle - see Updates. To replace the files
by hand, close rCommander first, and close an MCP client (Claude Desktop, Claude Code) that
started rcommander mcp without a window running: that process runs the same file until its
client ends.
All settings, the connection tree and the encrypted vault are kept in one database file,
rcommander.db, in your user profile (on Windows under %APPDATA%). Removing rCommander means
deleting the program folder and, if you want, that file. A master password exists only if you
store passwords or keys; see Connections.
The source is on GitHub, degoya/rCommander. rCommander is
developed in WSL2 on Windows and cross-built for Windows with cargo-xwin. In short, inside a
WSL2 Ubuntu or Debian:
sudo apt install build-essential clang cmake lld llvm nasm ninja-build pkg-config
cargo install cargo-xwin --version 0.23.1 --locked
git clone https://github.com/degoya/rCommander.git
cd rCommander
scripts/run-windows.sh # builds, copies the .exe to %LOCALAPPDATA%\rcommander-dev\ and starts it
scripts/package-windows.sh # builds the zip under artifacts/windows/rustup must be installed; the pinned Rust version and the Windows target are installed
automatically on the first build. scripts/check.sh runs the formatting, lint and test checks;
the repository's scripts/README.md lists every script.
Bug reports and ideas are welcome as issues. The
GitHub repository is an export of the development repository, refreshed at every release: a pull
request is a proposal the maintainer applies by hand, with credit. The repository's
CONTRIBUTING.md explains how, and SECURITY.md how to report a vulnerability privately.
Getting started
Using rCommander
- Panels
- Themes
- Connections
- Workspaces
- Button bar
- Own commands and Start menu
- Terminal
- Archives
- Tools
- Backup and restore
- Plugins
- Updates
Developing
Reference