LanQueue 0.8.1
See the version list below for details.
dotnet tool install --global LanQueue --version 0.8.1
dotnet new tool-manifest
dotnet tool install --local LanQueue --version 0.8.1
#tool dotnet:?package=LanQueue&version=0.8.1
nuke :add-package LanQueue --version 0.8.1

LanQueue
RAM and new hardware are expensive. Your old PCs are not. Plug them back in and give them work.
lanq is a small .NET global tool that sends builds, tests, log analysis and headless coding-agent jobs to the
other computers you already own. Your old machines can still help you get development done: all a worker needs is a
LAN connection, SSH, git and the toolchain for your jobs, and it joins your queue. No git on the old PC? Set
transfer: archive and it needs only SSH, tar and your toolchain. Your dev PC stays free for writing code.
Install
dotnet tool install --global LanQueue
dotnet tool update --global LanQueue
Requires the .NET 10 SDK on the machine you run lanq from, plus git and ssh on the PATH.
No .NET SDK? Each GitHub release also has a single-file native lanq for Windows (x64, Arm64), Linux (x64, Arm64,
glibc 2.27 and later) and macOS (Apple silicon), with SHA256SUMS, build-provenance attestations and a Scoop
manifest: https://github.com/jangolath/lanqueue#install
Quick start
- Write a starter
machines.ymlwithlanq init(or start from the example), list your machines, and make sure key-based SSH login works. - Check your setup and the fleet:
lanq doctor --remote, thenlanq health - Run a job from inside a git repository:
lanq run --needs dotnet,linux -- dotnet test -c Release - Bring results back: add
--fetch 'TestResults/**/*.trx'(repeatable) and the matching files land in.lanq/artifacts/<job id>/, whether the job passed or failed.
Onboarding a PC: lanq makeready --ssh user@old-pc.lan --os windows runs the read-only
lanq-makeready check over SSH (built in, sent on stdin, nothing written to
the PC) and suggests a machines.yml entry; lanq makeready --all checks every configured machine and prints one
summary table (--json for one object). lanq unlock <machine> clears slots left by a crashed run.
For scripts and coding agents, run, health, doctor, stats, makeready, init and wake take --json and
print one object with suggested nextSteps. lanq run --dry-run shows where a job would go without sending it,
lanq doctor --json lists each check with its fix, lanq stats --json gives pass rates and run times per machine and
per command, and --shards auto --target-minutes 10 sizes shards from earlier runs. See
docs/JSON.md and
AGENTS.md.
lanq picks the least loaded machine that has what the job needs, ships your current git state (including
uncommitted changes) to a throw-away worktree, runs the one allowlisted command, streams the log back and cleans up.
lanq's exit code is the job's own exit code; 2 means rejected by policy or bad arguments, 70 an infrastructure
error, 75 no eligible machine and 124 that the job ran past --timeout <minutes> (default 240) and was stopped.
A job that itself exits with 124 looks the same; the [lanq] TimedOut: ... status line on stderr tells them apart.
Setting up a pool for a team (one orchestrator, Windows 10/11 and Linux workers, low-RAM micro PCs, overnight family PCs)? Follow the team quick start.
What a worker needs
An SSH server, the toolchain your jobs use, and git (recommended, the default) or, with transfer: archive, just
tar (the built-in bsdtar on Windows 10 1803+; GNU tar or bsdtar plus gzip on Linux, busybox tar is refused). Nothing from lanqueue is installed on it, and it needs no GitHub
access. Setup steps for Linux and Windows: docs/WORKERS.md.
Lend it a shared or old PC
allowed_hoursper machine, by day:["Mon-Fri 22:00-07:00", "Sat,Sun 01:00-09:00"], on the worker's own clock. A job still running when the window ends is stopped after a grace period (exit 124,[lanq] WindowClosed).- Optional Wake-on-LAN per machine (
wake: {mac: "aa:bb:cc:dd:ee:ff"}):lanq runwakes one sleeping machine only when no awake one can take the job (needs--wait,--no-waketurns it off),lanq health --wakewakes sleepers, both only insideallowed_hourswith at leastmin_window_minutes+wait_secondsof the window left;lanq wake <machine> [--wait] [--json]wakes it on request. Needs Wake-on-LAN enabled in the BIOS/UEFI and the NIC driver, usually wired Ethernet; see docs/WORKERS.md. - A
PAUSEfile (Linux:PAUSEorpause) in the worker'swork_rootholds the machine; anyone at that PC can create or delete it. A job already running is not affected. - Jobs run at low priority by default (
nice/ioniceon Linux, BelowNormal on Windows);priority: normalturns it off. - Machines with little free memory are held (
min_free_mem_gb, Linux memory pressure), andlanq run --mem 4asks for a machine with at least 4 GB available. - Per-machine
env:(for exampleNODE_OPTIONS: "--max-old-space-size=2048") andpath_prepend:(for nvm, pyenv, rustup or sdkman tools a non-login SSH session cannot find).
Split long work across the pool
lanq run --shards 4 -- npx jest --shard={shard}/{shards} runs four pieces at once on free slots (--shards auto
uses every free slot that can take the job); each gets {shard}/{shards} in its arguments and LANQ_SHARD/
LANQ_SHARDS in its environment, and the snapshot is built once. Exit 0 only if every shard passed; --json prints
one object with a shards array. lanq health shows cores, total RAM, free slots and what each machine suits.
Recipes for .NET, Node, Python, Go and Rust:
docs/SHARDING.md.
Route jobs and run a whole plan
--min-size heavy or --size light,medium sends a job only to machines of that size (probed, or size: in
machines.yml), and --on big-01 only to named machines; every other rule still applies. A repository's lanq.yml
lists its jobs (build, unit tests, integration tests, a serial tail with after:), each one lanq run line, and
lanq run --plan runs them side by side on one snapshot with one result (--only, --dry-run, --json):
docs/PLANS.md.
Safe by default
- Key-only SSH with strict host-key checking; there is no password option.
- Only commands and directories you allowlist can run; arguments are quoted, never interpreted by a shell (Windows
workers never take arguments containing
"<>^%, nor&|unless the program is a native.exe, sincecmd.exeshims would re-parse them). - Worker output is untrusted: control, bidi and zero-width characters are shown as
?. --fetchtreats the worker as untrusted: regular files only (links never followed), sent as checksummed text (no archive is ever extracted), every path, size, count and hash checked again locally, files created new below.lanq/artifacts/<job id>/and never through a link. Fetch problems are reported but never change the exit code.- Best-effort secret scan of the command and uncommitted changes, plus the names of committed files (
.env,id_rsa,*.pemand similar) and the content of.npmrc,.pypircand.yarnrc.yml, before anything leaves your machine. - On git workers, git runs with hooks off, transports refused and the system and global git config ignored (git 2.32+), and a tampered cache is recreated; later jobs send only new commits.
- No daemon, no telemetry, and no network access except the SSH hosts you list.
More
MIT licensed.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net10.0 is compatible. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 0.12.0 | 99 | 11/14/2026 |
| 0.11.0 | 97 | 11/14/2026 |
| 0.10.1 | 92 | 11/14/2026 |
| 0.10.0 | 97 | 11/13/2026 |
| 0.9.2 | 91 | 11/13/2026 |
| 0.9.1 | 95 | 11/13/2026 |
| 0.9.0 | 93 | 11/13/2026 |
| 0.8.1 | 98 | 11/10/2026 |
| 0.8.0 | 87 | 11/10/2026 |
| 0.7.0 | 93 | 11/10/2026 |
| 0.6.0 | 88 | 11/10/2026 |
| 0.5.1 | 90 | 11/9/2026 |
| 0.5.0 | 90 | 11/9/2026 |
| 0.4.0 | 96 | 11/9/2026 |
| 0.3.1 | 91 | 11/9/2026 |
| 0.3.0 | 85 | 11/8/2026 |
| 0.2.0 | 98 | 11/8/2026 |
### Security
- The .NET SDK search behind `lanq doctor --remote` and `lanq makeready --add` no longer proposes `path_prepend` for a
folder other local users could plant code in, judged as lanq-makeready 0.3.0 does: only Administrators, SYSTEM,
TrustedInstaller (root), members of the local Administrators group and the build account may write the folder, its
`dotnet`, `sdk`, `host` and `shared` trees, and nobody else may rename or replace it through a parent folder (on Linux
the file modes; POSIX ACLs are not read). On a shared PC, a world-writable folder such as `C:\tools\dotnet` could
otherwise make every later .NET job run a planted program as the build account. Such a folder is skipped, and
`doctor --remote` and `--add` say so. The search now goes to the worker on stdin and runs from memory, like
`lanq makeready`, instead of on the command line.
### Behaviour changes
- `lanq makeready` runs lanq-makeready 0.3.0. On a Windows worker whose build account is denied WMI/CIM it now reports
memory, CPUs, the Windows version and disks instead of 0 GB and "unreadable", and no longer reports OpenSSH Server as
"installed but not running" when that account may not read the service status. Keys in a file `sshd_config` names
(such as a `Match User` block's central file) are found. The .NET SDK search covers the same folders `lanq doctor
--remote` searches, with the same ownership rule.
- The suggested `machines.yml` entry (text and `--add`) takes the script's `path_prepend` and `env: DOTNET_ROOT` when
the newest .NET SDK is in a folder that is not the `dotnet` on PATH. lanq takes it only as exactly one absolute folder
in printable ASCII with `DOTNET_ROOT` set to the same folder and none of `"` `\` `<` `>` `|` `?` `*` `;` `:`; anything
else is left out. A folder the report hides (under the user's home, redacted) is shown as a comment, and `--add` then
looks the SDK up itself as before. `--add` never writes a second `path_prepend:` or `env:` key or a second `dotnet`
capability. `--json` passes the script's `suggestedMachine` through as reported.
Full changelog: https://github.com/jangolath/lanqueue/blob/main/CHANGELOG.md