Remove the repeated setup.
An alias changes on the laptop. A package appears on the desktop. The machines slowly stop behaving the same way.
Tether brings configuration and package synchronisation into one command-line tool. A background process keeps the environment moving with the work.
Keep readable configuration local.
The shell needs ordinary configuration files. The remote repository should not need their plaintext contents.
Tether encrypts configuration before synchronising it. Git provides version history while local tools continue to read familiar files.
The repository documents the implementation and its security model. Encryption does not remove the need to protect the local machine.
Treat conflicts as part of the product.
Two machines can change the same file. Synchronisation needs a recovery path as well as a happy path.
Tether includes conflict handling, backups, and restore commands. Those controls matter more than hiding every operational detail.
Use the work to improve the tool.
Tether started with the repeated work of keeping my own environments consistent. Its scope follows those practical development needs.
The public source and launch account explain the choices. The current documentation covers supported platforms and installation.