Linux, macOS and Windows
The agent is one binary. The command from Add machine installs it for your user and keeps it running.
| Linux | macOS | Windows | |
|---|---|---|---|
| Binary | ~/.local/bin/tilder |
~/.local/bin/tilder |
%LOCALAPPDATA%\Programs\tilder\tilder.exe |
| Starts at | login (systemd user service) | login (LaunchAgent) | sign-in (Run key, with a monitor) |
| Its data | ~/.tilder |
~/.tilder |
%USERPROFILE%\.tilder |
| Its log | journalctl --user -u tilder-agent |
~/Library/Logs/tilder-agent.log |
%LOCALAPPDATA%\tilder\tilder-agent.log |
Linux
Any recent distribution on x86-64 or ARM64. With a systemd user session the agent is a user service; without one (a container, some minimal systems) it runs in the background and does not come back after a reboot. To keep it running after you log out:
loginctl enable-lingermacOS
macOS on Apple silicon or Intel. Install from a session on the Mac itself: a LaunchAgent needs a login session, which an SSH session does not have.
Windows
Windows 10 (1809) or later, x64 or ARM64. Open PowerShell (no administrator needed) and paste the Windows command. It checks the script's bytes in memory before running them, so nothing lands on disk for another program to swap.
Terminals open in PowerShell 7 if it is installed, otherwise Windows PowerShell. The agent stops when you sign out.
The Windows agent is not code-signed yet. The install command does not trigger SmartScreen, but Smart App Control blocks unsigned programs on Windows 11 PCs where it is on, and Microsoft Defender may flag remote-access tools. See Troubleshooting.
Updates
On Linux and macOS the agent updates itself to a newer release signed with tilder's release key, and goes back to the previous one if the new one does not start. Shells keep running through an update. On Windows, run the install command again to update.