Releases: michaelou/RemoteFlow
Release list
RemoteFlow 0.6.2
RemoteFlow 0.6.2, covering everything merged since v0.6.1.
What's changed
- No pull requests were merged in this range.
Landed without a pull request
- feat: the connections panel is a stack of cards, and its pane can be closed
- docs: cut 0.6.2 in the changelog
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.6.2-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.6.2-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.6.2-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.6.2-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The
installers are per-user, need no elevation, and leave your connections and settings in place when
you uninstall unless you ask for them to be removed.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.6.2-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is
unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell
the difference.
Full changelog: v0.6.1...v0.6.2
RemoteFlow 0.6.1
RemoteFlow 0.6.1 is a bug-fix release for the embedded terminal. Everything in it is a fix; there are no
new features and nothing to migrate.
Fixed
Every terminal in the tab layout works again, not just the last one. Selecting any tab other than the
last left a blank panel that could not be typed into. A session that is not on screen keeps its place in
the workspace at full size — a remote desktop cannot survive being re-hosted — but its tile also kept
painting over the whole area and swallowing clicks, so the tiles stacked in tab order and the last one
buried the rest. Switching to the grid and back made it obvious, because a new terminal is added at the end
and selected, so it always looked right until you went back to an older tab.
Output on Linux no longer walks off to the right. The terminal was created with newline translation
switched off, so a line feed from the shell moved the cursor down a row without returning it to the first
column and every line of ls began where the previous one ended. The same fault left the shell's line
editor counting columns the screen did not have, which is what redrew the line you were typing over the
wrong one and repeated characters as you typed or pasted. Windows was unaffected, because its console
renders the screen itself.
A new terminal on Linux and macOS starts your own shell, not a stripped one. bash was launched in a way
that suppressed the prompt, the aliases and the colours from your own configuration, while PowerShell on
Windows kept its profile — so the same application looked configured on one platform and bare on the other.
A shell profile you have already saved keeps the arguments it was created with; clear it under
Settings → Terminal to pick up the new default.
Commits
- fix: the terminal stops staircasing, and every tab works
- docs: cut 0.6.1 in the changelog
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.6.1-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.6.1-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.6.1-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.6.1-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The
installers are per-user, need no elevation, and leave your connections and settings in place when
you uninstall unless you ask for them to be removed.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.6.1-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is
unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell
the difference.
Full changelog: v0.6.0...v0.6.1
RemoteFlow 0.6.0
RemoteFlow 0.6.0 adds automatic backup, and finally opens the credential vault it needed to keep a passphrase in.
Automatic backup
Backup has been manual since it existed, which means the archive you have is the one you last remembered to make — usually the one from before the change you now want to undo.
Turn it on under Backup → Automatic. Every change to a connection, folder or tag writes a fresh archive about thirty seconds after you stop editing, so a rename, a retag and a move produce one backup rather than three.
- The destination is a place you already configured. A folder on this computer, or an SFTP connection or storage account from your own connection list — not a second place to set up a server.
- Archives include your saved credentials, encrypted with a passphrase you set once and which is kept in your system credential store, never in RemoteFlow's database. Without it a restored backup gives you back a list of hostnames and nothing you can sign in with. If no passphrase is set, RemoteFlow writes nothing and says so rather than quietly making an archive you cannot restore from.
- You choose how many to keep. Older ones are removed after each successful run, and files RemoteFlow did not write are never touched — a manual export sitting in the same folder is safe.
- Failures wait for you on the Backup page rather than interrupting what you are doing. It reports when the last run happened, where it went, and what went wrong, and retries at the next change and the next launch.
The credential vault now opens
On a computer with no system keyring RemoteFlow can use — most often Linux without libsecret — saved passwords and keys live in an encrypted file of its own. Nothing ever opened that file, so on those machines credentials silently could not be saved or read at all.
If that describes your machine, RemoteFlow now asks for a vault passphrase when it starts: once to choose one the first time, with a confirmation box and a warning that nothing else holds a copy, and once to recall it on later launches. A wrong passphrase can be retyped. Declining leaves RemoteFlow running without saved secrets rather than failing to start, and the Backup page offers a way back in without restarting.
Machines with a working keyring — Windows, macOS, and Linux with libsecret — are untouched and see no prompt.
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.6.0-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.6.0-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.6.0-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.6.0-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The installers are per-user, need no elevation, and leave your connections and settings in place when you uninstall unless you ask for them to be removed.
Four Linux artefacts, in two shapes. The Debian packages use Debian's own naming because apt and dpkg expect it:
| File | What it is |
|---|---|
remoteflow_0.6.0_amd64.deb |
Debian/Ubuntu package for Intel and AMD machines. |
remoteflow_0.6.0_arm64.deb |
The same for ARM machines. |
RemoteFlow-0.6.0-linux-x64.tar.gz |
Portable build for Intel and AMD machines. |
RemoteFlow-0.6.0-linux-arm64.tar.gz |
The same for ARM machines. |
Install the package with sudo apt install ./remoteflow_0.6.0_amd64.deb.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.6.0-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell the difference.
Full changelog: v0.5.0...v0.6.0
RemoteFlow 0.5.0
RemoteFlow 0.5.0, covering everything merged since v0.4.0.
What's changed
- No pull requests were merged in this range.
Landed without a pull request
- feat: the file browsers are compact, and the SFTP panes measure the same
- feat: Transfers sits below Storage in the sidebar
- feat: the explorer's toolbar is glyphs, and every protocol has its own colour
- docs: cut 0.5.0 in the changelog
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.5.0-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.5.0-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.5.0-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.5.0-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The
installers are per-user, need no elevation, and leave your connections and settings in place when
you uninstall unless you ask for them to be removed.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.5.0-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is
unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell
the difference.
Full changelog: v0.4.0...v0.5.0
RemoteFlow 0.4.0
RemoteFlow 0.4.0, covering everything merged since v0.3.0.
What's changed
- No pull requests were merged in this range.
Landed without a pull request
- feat: the SFTP page is dual-pane, and the local pane remembers where it was
- docs: cut 0.3.1 in the changelog
- docs: cut 0.4.0, not 0.3.1
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.4.0-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.4.0-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.4.0-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.4.0-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The
installers are per-user, need no elevation, and leave your connections and settings in place when
you uninstall unless you ask for them to be removed.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.4.0-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is
unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell
the difference.
Full changelog: v0.3.0...v0.4.0
RemoteFlow 0.3.0
RemoteFlow 0.3.0 adds cloud object storage. Amazon S3 and Azure Blob Storage are connection types like
any other, with a page that puts your own files beside the bucket and a transfer engine built for objects
in the gigabytes.
It is also the first release built end to end by CI on both platforms: the Linux .deb and tarball used
to be produced on a maintainer's machine and attached by hand.
What's new
S3 and Azure Blob accounts save as connections. Choose the protocol and the editor asks for what that
provider needs — an access key ID and a region for S3, a storage account name for Azure. Host and port
fill themselves in and stop doing so the moment you type over them, which is how a sovereign-cloud account
is reached. Keys go into the platform keychain like every other RemoteFlow credential, never into the
database or a plaintext backup. A custom endpoint and path-style addressing make the S3 protocol work
against MinIO, Ceph, Backblaze B2, Cloudflare R2 and Wasabi.
A Storage page, with your own files beside the bucket. Local filesystem on the left, bucket or
container on the right, transfer queue along the bottom. Select and press Upload or Download, drag
between the panes, or press Enter. Double-clicking an S3 or Azure Blob connection opens it here. The
queue is the same one the Transfers page shows, not a second one.
Two things it will not pretend to do. "Starts with" is not a search — both providers narrow a listing by
prefix and neither searches by substring. And a listing stops at 10,000 rows with "of many shown" rather
than inventing a total, because S3 cannot cheaply count a prefix.
Objects in the gigabytes transfer in parallel chunks. Uploads split into parts and downloads into
ranges, sized from the object — an 8 MiB part for a 4 GiB object, 64 MiB for a 500 GB one — four in flight
at a time. Memory stays flat regardless of object size and the progress bar never goes backwards. A failed
part retries on its own rather than restarting the transfer, and cancelling aborts the incomplete upload so
its parts are not left behind and billed.
RemoteFlow cannot promise that after a crash or a power cut, so set a lifecycle rule on the bucket — S3's
AbortIncompleteMultipartUpload at seven days — as the durable backstop. Azure needs nothing: uncommitted
blocks expire on their own.
Before you upgrade
Your database moves to schema version 2. Once this build has opened it, RemoteFlow 0.2.6 and earlier
will refuse it with a message telling you to upgrade, rather than failing part-way through opening the
connections page. Existing databases are stamped on first launch and need no action from you.
The same applies in one direction to backups: an archive written by this release that contains an S3 or
Azure Blob connection cannot be imported by 0.2.6 or earlier. Backups containing only SSH, SFTP and RDP
connections are unaffected both ways.
Downloads
Windows artefacts and the portable Linux builds, named for the version and the runtime identifier:
| File | What it is |
|---|---|
RemoteFlow-0.3.0-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.3.0-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.3.0-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.3.0-win-arm64-setup.exe |
Per-user installer for ARM64. |
RemoteFlow-0.3.0-linux-x64.tar.gz |
Portable Linux build for Intel and AMD machines. |
RemoteFlow-0.3.0-linux-arm64.tar.gz |
Portable Linux build for ARM machines. |
The Debian packages follow Debian's own naming, because apt and dpkg expect it:
| File | What it is |
|---|---|
remoteflow_0.3.0_amd64.deb |
Debian/Ubuntu package for x64. |
remoteflow_0.3.0_arm64.deb |
Debian/Ubuntu package for ARM64. |
Every build is self-contained: the .NET runtime is inside it, so a clean machine needs nothing installed
first. The Windows installers are per-user, need no elevation, and leave your connections and settings in
place when you uninstall unless you ask for them to be removed. Install the .deb with
sudo apt install ./remoteflow_0.3.0_amd64.deb rather than dpkg -i, so dependencies are resolved.
Verifying your download
checksums.txt lists the SHA-256 of all eight files.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.3.0-win-x64.zip -Algorithm SHA256Nothing here is code-signed. Windows SmartScreen will warn that the publisher is unknown, and the Linux
artefacts have no detached signature and no apt repository behind them. That is expected and is not a sign
of a corrupted download; the checksum is how you tell the difference. It proves the file arrived intact
and says nothing about who built it.
Full changelog: v0.2.6...v0.3.0
RemoteFlow 0.2.6
RemoteFlow 0.2.6 is the first release you can install on Linux, and it carries a dependency security fix that affects every platform.
Highlights
A Debian package for Linux. remoteflow_0.2.6_amd64.deb installs to /opt/remoteflow, puts remoteflow on your PATH, and registers a launcher entry and icons, so RemoteFlow shows up in your application menu like anything else you installed. Uninstalling keeps your connections, settings and host keys — everything RemoteFlow writes follows the XDG base directory spec and lives under $HOME, which dpkg never touches. Remote Desktop stays Windows-only; an RDP connection on Linux points you at FreeRDP or Remmina.
SSH.NET moves to 2026.0.0, which fixes GHSA-q939-rpr3-3284 (HIGH): ScpClient's recursive download let server-controlled filenames escape the destination directory. RemoteFlow has never referenced ScpClient — SFTP is the only file transfer path — so the vulnerability was not reachable here. It is still worth updating for.
Two test suites that had been lying. Six tests asserted Windows path semantics through the host's path APIs and failed on Linux and macOS. Separately, 63 of 270 Windows UI tests were failing as a single race rather than 63 bugs: Avalonia's RoutedEvent.Register writes into a plain Dictionary, so two threads running a type initialiser at once corrupt it. Nothing in the application changed for either.
Nothing about how RemoteFlow behaves on Windows is different in this release.
Downloads
Linux
| File | What it is |
|---|---|
remoteflow_0.2.6_amd64.deb |
Debian/Ubuntu package for Intel and AMD machines. |
remoteflow_0.2.6_arm64.deb |
Debian/Ubuntu package for ARM machines. |
RemoteFlow-0.2.6-linux-x64.tar.gz |
Portable build, any distribution. |
RemoteFlow-0.2.6-linux-arm64.tar.gz |
Portable build for ARM machines. |
sudo apt install ./remoteflow_0.2.6_amd64.debUse apt rather than dpkg -i so dependencies are resolved rather than merely reported. On other distributions, unpack the tarball and see docs/building.md for the desktop entry.
The Linux artefacts are built on a maintainer's machine, not by CI, so they carry none of the guarantees the Windows jobs provide. The amd64 package was installed and launched before release; arm64 was compiled but never run.
Windows
| File | What it is |
|---|---|
RemoteFlow-0.2.6-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.2.6-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.2.6-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.2.6-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The installers are per-user, need no elevation, and leave your connections and settings in place when you uninstall unless you ask for them to be removed. Each was built and launched on a runner of its own architecture.
Verifying your download
checksums.txt lists the SHA-256 of all eight files.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.2.6-win-x64.zip -Algorithm SHA256These builds are not code-signed, and the .deb carries no GPG signature. Windows SmartScreen will warn that the publisher is unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell the difference. A checksum proves the file arrived intact, not who built it.
Full changelog: v0.2.5...v0.2.6
RemoteFlow 0.2.5
RemoteFlow 0.2.5, covering everything merged since v0.2.4.
What's changed
- No pull requests were merged in this range.
Landed without a pull request
- feat: RemoteFlow installs the update it finds
- docs: cut 0.2.5 in the changelog
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.2.5-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.2.5-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.2.5-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.2.5-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The
installers are per-user, need no elevation, and leave your connections and settings in place when
you uninstall unless you ask for them to be removed.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.2.5-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is
unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell
the difference.
Full changelog: v0.2.4...v0.2.5
RemoteFlow 0.2.4
RemoteFlow 0.2.4, covering everything merged since v0.2.3.
What's changed
- No pull requests were merged in this range.
Landed without a pull request
- fix: a keyboard copy keeps its selection, and terminal colours come from the scheme
- docs: cut 0.2.4 in the changelog
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.2.4-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.2.4-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.2.4-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.2.4-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The
installers are per-user, need no elevation, and leave your connections and settings in place when
you uninstall unless you ask for them to be removed.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.2.4-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is
unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell
the difference.
Full changelog: v0.2.3...v0.2.4
RemoteFlow 0.2.3
RemoteFlow 0.2.3, covering everything merged since v0.2.2.
What's changed
- No pull requests were merged in this range.
Landed without a pull request
- feat: the terminal workspace can show every session at once
- docs: cut 0.2.3 in the changelog
Downloads
Four Windows artefacts, named for the version and the runtime identifier (win-x64 or win-arm64):
| File | What it is |
|---|---|
RemoteFlow-0.2.3-win-x64.zip |
Portable build for Intel and AMD machines. |
RemoteFlow-0.2.3-win-arm64.zip |
Portable build for ARM machines. |
RemoteFlow-0.2.3-win-x64-setup.exe |
Per-user installer for x64. |
RemoteFlow-0.2.3-win-arm64-setup.exe |
Per-user installer for ARM64. |
The zips are self-contained: they run on a clean Windows with no .NET runtime installed. The
installers are per-user, need no elevation, and leave your connections and settings in place when
you uninstall unless you ask for them to be removed.
Verifying your download
checksums.txt lists the SHA-256 of every file above.
sha256sum --check --ignore-missing checksums.txtOn Windows without sha256sum:
Get-FileHash .\RemoteFlow-0.2.3-win-x64.zip -Algorithm SHA256These builds are not code-signed, so Windows SmartScreen will warn that the publisher is
unknown. That is expected and is not a sign of a corrupted download; the checksum is how you tell
the difference.
Full changelog: v0.2.2...v0.2.3