Files, licence and support

Where Commander keeps things

What Mac Windows Linux
Settings ~/.cuberact/commander/ %APPDATA%\Cuberact\Commander\ ~/.cuberact/commander/
Logs and reports ~/Library/Application Support/Cuberact/Commander/ %LOCALAPPDATA%\Cuberact\Commander\ ~/.local/share/cuberact/commander/
Picture previews ~/Library/Caches/Cuberact/Commander/previews %LOCALAPPDATA%\Cuberact\Commander\previews ~/.cache/cuberact/commander/previews

Preferences ▸ Data opens each of these with a click.

The settings folder holds plain text files:

File What is in it
preferences.properties Your choices in Preferences
state.properties The window, the panels, every tab
places.properties Bookmarks and servers, and server passwords sealed for this computer if they are kept here
shortcuts.properties The keys you changed
execution.properties Your rules for opening files
known_hosts, known_certificates The servers you trusted
theme/ A folder for each theme
licence.txt Your licence
trial.properties The trial’s days, sealed

The key that seals server passwords lives with the logs, not with the settings: it belongs to this computer, so a copied settings folder doesn’t carry the passwords.

The files can be edited by hand while Commander is closed; they are read at the start.

Moving to another computer, starting over

  • To take your setup along, copy the settings folder to the same place on the other computer. Server passwords are asked once there, since they are sealed for the first computer.
  • To start over with default preferences, quit Commander and delete preferences.properties. Deleting the whole folder also takes your bookmarks, servers, shortcuts, rules, themes and licence, and ends the trial.

Logs

Commander writes a log of each run: one file per run, named by its start, such as commander-2026-11-14-093012.log. The ten newest runs are kept, at most 10 MB each.

  • A log names files, folders, servers and user names, never a password.
  • Help ▸ Show Log (Mac) opens the log folder in a new tab, with the cursor on this run’s log. On every system, Preferences ▸ Data ▸ Log folder does the same.
  • Preferences ▸ Data ▸ Log: Normal, Detailed or Everything. Normal is enough unless support asks for more.

Report a Problem

Report a Problem… (in the Help menu on a Mac, and in Preferences on every system) puts together what helps find a problem, and nothing is sent by itself.

  1. Make Report packs a zip: a summary of the system and the app, the logs, and after a crash, the Mac’s crash reports. Settings, bookmarks and servers are not included, and the licence shows only as its number.
  2. The zip appears as a tile: drag it into an email, copy it, or click it to see what is inside.
  3. Write Email opens a message to support@cuberact.com with the version and system filled in, and room for what happened.

You send the email yourself. Bug reports and ideas can also go on GitHub, as the Support page says.

After a crash

If Commander ever ends unexpectedly, or is ended while tasks run, the next start says so, and lists the tasks that were left unfinished: the file each was writing may be incomplete. After a crash, the window has a Report a Problem button.

Licence and trial

The trial: without a licence, Commander runs whole for 14 days from its first day. Nothing is ever limited.

  • In the last three days, a band at the top of the window counts down, with Enter Licence… and Buy.
  • After the trial, a window reminds you at the start, and at most every two hours. Its Continue waits a few seconds, one more each week, ten at most.
  • The window’s title says (Trial) or (Not licensed).

Entering a licence: open Enter Licence… (the Commander menu on a Mac) or Preferences ▸ Licence, paste the licence, and press Register. Pasting the whole email works too: the text around the licence is ignored. The page then shows who it is licensed to, the licence number and the date.

  • A licence is checked on your computer alone. Nothing is sent.
  • A 1.x.x licence covers every version 1. A Lifetime licence covers every version.

Updates

Commander checks for a new version once a day. Check for Updates… (the Commander menu on a Mac, and About everywhere) checks right away.

A new version shows in a window with its release notes:

  • Update downloads it and checks that it is genuine. Restart then installs it and opens the new version. Later waits.
  • Skip This Version stops the reminders about it.
  • If Commander can’t replace itself, for example when it runs from the disk image, Download opens the download page instead.

The check asks releases.cuberact.com for the newest version and the release notes. It names Commander and its version, and sends nothing about you, your computer or your files.

About

About (the Commander menu on a Mac, Preferences ▸ About everywhere) shows the version, Check for Updates…, Release Notes of this version and the ones before it, and Third-Party Licences: every part Commander is made of, its authors and its licence.

Quitting

Quit ⌘Q (Ctrl+Q) closes Commander. With tasks running, it lists them first: Commander quits when they are done, or Cancel all tasks stops them and quits now. Esc keeps everything running.

On a Mac, closing the window quits too, or only hides Commander with its tasks running on, as Preferences ▸ General ▸ Closing the window says.

For the curious

  • CUBERACT_COMMANDER_DIR set to a folder makes Commander use it for its settings: a clean profile to try something in.
  • RUST_LOG overrides the log level.