Two panels. Your theme. Nothing half-written.

No. It runs on any Linux distribution with kernel 6.8 and glibc 2.34 or later, so Ubuntu 24.04, Debian 13, Fedora 40 and their successors as well as Arch, in any truecolor terminal; it needs no library beyond glibc. The kitty keyboard protocol, which Ghostty, foot, Alacritty and Kitty speak, adds the Ctrl+M and Ctrl+1 to Ctrl+9 chords; kitty graphics or Sixel add sharper pictures than halfblocks. The live theme reads Omarchy's palette. Elsewhere, --theme-file points it at any colors.toml, and without one it uses the terminal's own colours. The Hyprland binding above is Omarchy's way to launch it; any other desktop binds a terminal command its own way. Other palettes and fallbacks

It is a terminal program. It starts at once, runs over ssh and inside tmux, and takes the keys your hands know from Total Commander and mc. There is no icon grid and no drag and drop; it shows one picture at a time, in the quick view, and lists everything else as text you can filter, mark and act on.

The two panels, Tab between them, Insert to mark, the F-keys from F3 view to F8 delete, Alt+F7 to find, Ctrl+D for the directory hotlist, Ctrl+M for multi-rename, and a command line under the panels. F1 inside the app shows the whole keymap. The keymap

The guarantees rest on four kernel features: statx mount IDs to tell filesystems apart, renameat2 for an overwrite that never truncates, copy_file_range for copies the filesystem can accelerate, and syncfs error reporting, so a move across filesystems deletes its source only after the copy is known to be on disk. The project tests on 6.8 and later, where statx reports the unique mount ID. The same calls exist from Linux 5.8 on, with the older reusable mount ID, and the program makes no version check; that path is not verified yet, so the promise stops at 6.8. Durability

Not yet. Every release carries one binary, for Linux x86-64; an aarch64 release is planned. Until then, build from source with cargo; the code has no x86-64-only parts, but the project tests x86-64 only. Build from source

A file you can see under its real name is complete. A copy is written under a temporary name and renamed into place; an overwrite replaces the old file in one step; a move across filesystems keeps the file in at least one complete place at every moment. That holds on ext4, btrfs and xfs. A filesystem without hard links or RENAME_NOREPLACE, such as some FUSE mounts, and a server without hard links, get direct writes instead, and the app says so. What each operation guarantees

No. manycommander opens no network connection except the SFTP server you cd to, through your own ssh. It has no update check and no telemetry; omarchy update and mise handle updates. This site loads nothing from a third party and sets no cookie; a theme you pick here stays in your browser's local storage.

Not published yet. Each release builds and checks the package manycommander-bin, but the AUR accepts no new accounts at the moment, so the project has no account to publish it from. On Arch, install with mise or a release. The AUR

A table in the docs reads each project's own documentation for the things manycommander does differently: the two panels and F-keys, archives and servers as panels, the copy and trash guarantees, and the live theme. Compared with other terminal file managers