Skip to content
LabTether

Uninstall

Remove the agents first, then the hub. An agent left running keeps trying to reach a hub that is gone, and the hub refuses to delete a device while its agent is still connected.

Remove a device from the hub

  1. Uninstall the agent on the machine with the steps below.
  2. In the console, open the device and click the trash icon (Delete device). Type the device name to confirm.

Deleting a device revokes its agent tokens, so a copy of the agent that was missed can no longer connect with them.

Linux agent

The agent installer adds a labtether command. Run one of these on the machine:

# Remove the agent, keep its identity so it can enroll again later
sudo labtether agent uninstall

# Remove the agent and everything it kept
sudo labtether agent purge

Both stop and remove the labtether-agent service, the agent binary, /etc/labtether/agent.env and the hub's SSH key line in /root/.ssh/authorized_keys.

uninstall keeps the token, device key and hub CA in /etc/labtether, and the labtether command. purge also deletes /etc/labtether, the labtether command, and a copy of the hub CA in the system trust store if an older installer put one there.

Compose stacks you deployed from the hub are not touched. Their files stay in /var/lib/labtether/stacks and their containers keep running.

macOS app

  1. Click the LabTether menu bar icon, then Reset & Uninstall....
  2. Click Uninstall & Quit.
  3. Drag LabTether Agent from Applications to the Trash.

Reset & Uninstall stops the agent, removes the hub's SSH key line from ~/.ssh/authorized_keys, turns off launch at login, deletes the app's Keychain items (service com.labtether.agent), deletes ~/Library/Application Support/LabTether and clears the app's settings.

If the app no longer opens, do the same by hand: remove the SSH key line with the app's own agent, then delete the rest.

LABTETHER_TOKEN_FILE="$HOME/Library/Application Support/LabTether/agent-token" \
  "/Applications/LabTether Agent.app/Contents/Resources/labtether-agent" ssh-key remove
rm -rf "$HOME/Library/Application Support/LabTether"
defaults delete com.labtether.agent

Then delete the com.labtether.agent items in Keychain Access, and remove LabTether Agent under System Settings > General > Login Items.

Windows app

The Windows app ships as a ZIP and has no uninstaller.

  1. Open the tray app's Settings and turn off Start at Login.

  2. Quit the tray app.

  3. In PowerShell, from the folder you extracted, remove the hub's SSH key line:

    $env:LABTETHER_TOKEN_FILE = "$env:LOCALAPPDATA\LabTether\agent-token"
.\Assets\labtether-agent.exe ssh-key remove

  4. Delete the extracted folder and %LOCALAPPDATA%\LabTether.

  5. In Credential Manager > Web Credentials, remove the LabTether entries.

Windows agent service

For the standalone agent installed as a Windows service, open PowerShell as administrator:

Stop-Service LabTetherAgent
& "$env:ProgramFiles\LabTether\labtether-agent.exe" uninstall

uninstall removes the LabTetherAgent service and the hub's SSH key line. It does not stop a running service, so stop it first. It keeps the agent binary and C:\ProgramData\LabTether, which holds the token, device key and hub CA. To remove those too:

Remove-Item -Recurse -Force "$env:ProgramData\LabTether", "$env:ProgramFiles\LabTether"

Hub

These steps are for a hub installed with the install script or with Docker Compose. Take a backup first if you might want the data back.

From the install directory (./labtether unless you chose another):

cd labtether
docker compose --env-file .env.deploy -f docker-compose.deploy.yml down --volumes --remove-orphans --rmi all
cd .. && rm -rf labtether

down --volumes deletes the stack's containers, networks and volumes: the database, generated secrets, hub CA and agent downloads. --rmi all also deletes the images; leave it out to keep them. Deleting the directory removes .env.deploy and the release files.

Upgraded from v1.4.0? The upgrade kept your old database volume as a backup. List it with docker volume ls --filter dangling=true and delete it with docker volume rm once you are sure you no longer need it.

What stays behind

  • Backups and copies of .env.deploy you made.
  • Tailscale HTTPS for the console, if you turned it on. tailscale serve reset turns it off, along with any other tailscale serve settings on that host.
  • Reverse proxy entries you added for the console.
  • The hub CA, on any machine where you added it to the trust store yourself.
  • API keys saved in other tools, such as the LabTether CLI, an MCP client or the Home Assistant integration. Remove them there.