LanQueue 0.7.0

There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global LanQueue --version 0.7.0
                    
This package contains a .NET tool you can call from the shell/command line.
dotnet new tool-manifest
                    
if you are setting up this repo
dotnet tool install --local LanQueue --version 0.7.0
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=LanQueue&version=0.7.0
                    
nuke :add-package LanQueue --version 0.7.0
                    

LanQueue - your spare machines, back to work

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

  1. Write a starter machines.yml with lanq init (or start from the example), list your machines, and make sure key-based SSH login works.
  2. Check your setup and the fleet: lanq doctor --remote, then lanq health
  3. Run a job from inside a git repository: lanq run --needs dotnet,linux -- dotnet test -c Release
  4. 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_hours per 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 run wakes one sleeping machine only when no awake one can take the job (needs --wait, --no-wake turns it off), lanq health --wake wakes sleepers, both only inside allowed_hours with at least min_window_minutes + wait_seconds of 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 PAUSE file (Linux: PAUSE or pause) in the worker's work_root holds 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/ionice on Linux, BelowNormal on Windows); priority: normal turns it off.
  • Machines with little free memory are held (min_free_mem_gb, Linux memory pressure), and lanq run --mem 4 asks for a machine with at least 4 GB available.
  • Per-machine env: (for example NODE_OPTIONS: "--max-old-space-size=2048") and path_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.

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 " & | < > ^ %, which cmd.exe shims would re-parse).
  • Worker output is untrusted: control, bidi and zero-width characters are shown as ?.
  • --fetch treats 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, *.pem and similar) and the content of .npmrc, .pypirc and .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 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. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

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

### Agents and scripts

- `lanq doctor --json` (also with `--remote`): one object on stdout on every path, `{status, exitCode, message,
 remote, counts, checks, nextSteps}`. Each check is `{scope, machine, name, level, detail, fix, capability}`, so an
 agent can report the `fail` checks and their fix. Status `Ok` (0), `Warnings` (1), `Failing` (1), `Rejected` (2),
 `InfraError` (70) or `Cancelled` (130). The text lines go to stderr.
- `lanq stats --json`: one object with the totals, `logs`, `machines` (counts, median and p90 of completed jobs,
 `speedFactor`, `speedSamples`) and `commands` (runs, jobs, results, times, `lastShards` and `timing`: the work and
 per-shard overhead `--target-minutes` uses). At most 500 commands (`commandsMore` counts the rest). Times are UTC.
- `lanq run --dry-run --json` adds `shardCountWhy` and `shardTiming` (null when they do not apply); a `--shards`
 run with `--target-minutes` adds `shardTiming`.
- Agent docs: agents may run `lanq doctor --json`, `lanq doctor --remote --json` and `lanq stats --json`; on
 `InfraError` they run `lanq doctor --remote --json` and report the `fail` checks. Contract:
 https://github.com/jangolath/lanqueue/blob/main/docs/JSON.md

### Sharding

- `--shards auto --target-minutes M` (1 to 1440) picks N from earlier completed runs of the same command and `--dir`
 (the newest 10 of the last 90 days), so each shard takes about M minutes on the slowest machine it would go to,
 never more than the free slots. Without history it is plain `--shards auto`. The `--shards auto` line (and a
 `Timing:` line in `--dry-run`) says why. Plain `--shards auto` is unchanged. Timing history starts with 0.7.0 runs.
- Per-machine speed factors, learned from completed jobs in the job log (`x1.62` = 62% slower than typical; 5 jobs
 needed, else the median of machines of the same size, else 1).
- `lanq stats --target-minutes M` shows the shards M needs per command, without probing.
- Guide: https://github.com/jangolath/lanqueue/blob/main/docs/SHARDING.md (new: choosing N from history, and
 balancing shards by duration for pytest, Jest, Playwright, .NET and Go).

### Behaviour changes

- `jobs.jsonl` lines gain optional fields: `v`, `key`, `dir`, `shard`, `shards`, `runId` and `runSeconds` (the
 command's own run time). At 4 MiB the file moves to `jobs.1.jsonl`; lanq reads both, lanq 0.6 only the current file.
- `lanq stats` survives bad lines: a torn or unreadable line is skipped and counted, with one warning. It exits 70
 when the job log cannot be read.
- A locked `jobs.jsonl` no longer turns a finished job into `InfraError`: the append is retried, then skipped with a
 warning. Two lanq processes no longer collide on it.
- Doctor suggestions in `--json` output now carry `--json` (`lanq doctor --json`, `lanq doctor --remote --json`).
 Text output still suggests plain `lanq doctor`.
- Job logs in the state folder's `logs/` are pruned after a run, at most once a day: lanq's own logs older than
 `policy.keep_logs_days` (new; default 30, 0 = never) and the oldest beyond 5,000. A log modified in the last hour,
 other files and links are never deleted.
- `lanq doctor` prints one more line after `config`: `logs` with the count and size of the job logs (`WARN` over
 2 GB when `policy.keep_logs_days` is 0).
- `lanq stats` keeps its first lines, then adds a machine table (median, p90, last run, speed), the newest 20
 commands with a `timing:` line each, and a `logs:` line.

### Docs

- README: a Local state section (what `jobs.jsonl` and `logs/` hold, rotation and pruning; nothing leaves the
 machine): https://github.com/jangolath/lanqueue/blob/main/README.md#local-state

Full changelog: https://github.com/jangolath/lanqueue/blob/main/CHANGELOG.md