TagHub Agent

Version 0.4.3 · built 2026-11-16 · 53247a9d

Prints TagHub labels on printers that TagHub cannot reach itself. The agent runs on a computer in your network, keeps one outbound connection to TagHub, and prints on the printers you set up on it.

Download

Windows64-bit (x64)Installer. Most PCs and serverstaghub-agent-0.4.3-win-x64-setup.exe · 64 MBWindowsARM64Installer. Windows on ARM devicestaghub-agent-0.4.3-win-arm64-setup.exe · 60 MBLinux64-bit (x64)Most servers and PCstaghub-agent-0.4.3-linux-x64.tar.gz · 32 MBLinuxARM64Raspberry Pi 4 and 5 (64-bit), ARM serverstaghub-agent-0.4.3-linux-arm64.tar.gz · 30 MBmacOSApple siliconM1 and latertaghub-agent-0.4.3-osx-arm64.tar.gz · 30 MBmacOSIntelMacs from before 2020taghub-agent-0.4.3-osx-x64.tar.gz · 32 MB

These builds are not code-signed. Windows SmartScreen and macOS Gatekeeper will warn about an unknown publisher. Check the file against the SHA-256 list at the bottom of this page before you run it.

Before you start

Set up

Windows
  1. Run the installer as an administrator. It puts the agent in C:\Program Files\TagHub Agent, starts it as a Windows service (restarted by Windows if it stops) and adds TagHub Agent to the Start menu. Silent: taghub-agent-…-setup.exe /S.
  2. Open TagHub Agent (the installer offers to), press Connect to TagHub… and paste the command or the code from TagHub.
  3. Add your printers with Add network printer… or Add Windows printer…, and try each with Print test label.

Everything the window does can also be done from a terminal with taghub-agent, see Printers below.

Who may change things: anyone logged on to the computer can open the window and look. Changing takes an administrator (the window has a Restart as administrator button) or membership of the local group TagHub Agent Operators, which the installer makes empty. Add the people who are to manage the agent; it counts from their next logon.

Upgrading: run the new installer over the old one. The connection and the printers are kept. Uninstalling (Windows' Installed apps) asks whether to remove them too.

The settings and the log are in C:\ProgramData\TagHub Agent, closed to ordinary users. The agent only makes outgoing connections: nothing listens on a network port.

Linux
  1. Unpack and put the program in place:
    tar -xzf taghub-agent-*.tar.gz
    sudo install -m 755 taghub-agent /usr/local/bin/taghub-agent
  2. Enroll with the command from TagHub, then add your printers (see Printers):
    sudo taghub-agent enroll XXXX-XXXX --server wss://<your TagHub address>/cloudprint/agent
  3. Run it as a service. Save this as /etc/systemd/system/taghub-agent.service:
    [Unit]
    Description=TagHub Agent
    After=network-online.target
    Wants=network-online.target
    
    [Service]
    Type=notify
    ExecStart=/usr/local/bin/taghub-agent run
    Restart=always
    RestartSec=5
    
    [Install]
    WantedBy=multi-user.target
    then:
    sudo systemctl daemon-reload
    sudo systemctl enable --now taghub-agent
    journalctl -u taghub-agent -f

The settings and the log are in /var/lib/taghub-agent, readable by root only. Linux serves network (ZPL) printers; print queues are Windows only.

macOS
  1. Unpack, and take the download mark off the file so it may run:
    tar -xzf taghub-agent-*.tar.gz
    xattr -d com.apple.quarantine taghub-agent
    sudo install -m 755 taghub-agent /usr/local/bin/taghub-agent
  2. Enroll, add your printers, and run it:
    sudo taghub-agent enroll XXXX-XXXX --server wss://<your TagHub address>/cloudprint/agent
    sudo taghub-agent run

The macOS builds are for trying the agent out: they have not been tested the way the Windows and Linux ones have, and there is no service set-up for macOS yet. The settings are in /Library/Application Support/TagHub Agent.

Printers

Printers are set up on the computer, never from TagHub. Each one you add shows up in TagHub within a few seconds, and the running service picks changes up without a restart.

On Windows the TagHub Agent window does all of this; the commands below are the same things from a terminal, and the only way on Linux and macOS.

A ZPL printer on the network

taghub-agent printer add --name "Dock" --host 10.0.0.5
taghub-agent printer test "Dock"

For printers that take ZPL on a network port (Zebra and compatible). Add only those: another printer may print the question it is asked.

A printer installed in Windows

taghub-agent printer queues
taghub-agent printer add --name "Office" --queue "Name from the list" --scale label
taghub-agent printer test "Office"

For printers with a Windows driver. TagHub sends the labels as pictures and the agent prints one label per page. --scale says how the picture is put on the page:

SettingThe labelThe page
fit (default)stretched over the whole pagethe driver's paper
actualat its own sizethe driver's paper
labelat its own sizethe size of the label, unless the label template names a paper the driver has

Use label for label printers. Change it later with taghub-agent printer scale "Office" fit.

Other commands

taghub-agent status              the enrollment and the printers
taghub-agent printer list
taghub-agent printer remove "Dock"
taghub-agent raw on|off          let TagHub send printer commands (calibration); off by default

If something is wrong

Check your download

SHA-256 of each file, also as SHA256SUMS. On Windows: Get-FileHash <file>. On Linux and macOS: sha256sum <file> or shasum -a 256 <file>.

FileSHA-256
taghub-agent-0.4.3-win-x64-setup.exea27370c2839ba4788c93d334f611295d73bff0433699554ff068f94cf282ea8f
taghub-agent-0.4.3-win-arm64-setup.exeb4d21847588a7b2df7729d0832ceb4a57e5951b8d8c036c88a0e5874bea61497
taghub-agent-0.4.3-linux-x64.tar.gz1e93ced374de7a95437d23ae46a691bd4d5a3755483ee1bbdd74132c91f070e2
taghub-agent-0.4.3-linux-arm64.tar.gz4b96e3a416ebe404f9d229e59626d48eb9b369679c5dfb9c80f4c4b134d4270b
taghub-agent-0.4.3-osx-arm64.tar.gz0ea1a50890d0cd3d08b7ed9f213f6c9fac73759fe5d8787d27a3e8e064b382c7
taghub-agent-0.4.3-osx-x64.tar.gzdcde2175fd1de123c70297f8a156fc3d4a3df41a31d62874aa392ad854bf24b0