LanQueue 0.10.0

There is a newer version of this package available.
See the version list below for details.
dotnet tool install --global LanQueue --version 0.10.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.10.0
                    
This package contains a .NET tool you can call from the shell/command line.
#tool dotnet:?package=LanQueue&version=0.10.0
                    
nuke :add-package LanQueue --version 0.10.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.

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. Since 0.10.0 --on, --size and --min-size narrow every job of a plan (never widen one), --plan-timeout M or plan_timeout: limits the whole plan, and lanq.yml may only lower the fetch limits (fetch_max, fetch_max_files); only your own --fetch-max, --fetch-max-files and --fetch-dir raise them or pick the folder.

Per-job options

  • --env NAME=VALUE sets a variable for one job, for names you list in policy.allowed_env (none by default); a deny table (loader, runtime startup, toolchain, profile, GIT_* and SSH_* variables) wins over that list. Settings only, never secrets.
  • --exclusive takes every slot of the machine, so nothing else runs there; it waits for an idle machine.
  • --baseline reruns a failed job at the base commit (the merge-base with the default branch, or --baseline-ref) and says whether the failure is new or preexisting; the exit code stays the job's.

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, since cmd.exe shims would re-parse them).
  • 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

### Added

- **Whole-plan timeout.** `lanq run --plan --plan-timeout M`, or a top-level `plan_timeout: M` in `lanq.yml` (1 to
 10080 minutes; the command line replaces the file's value; `plan_timeout:` is judged by `--plan-timeout`'s own
 parser). The clock starts after the command-line checks and the snapshot. It covers waiting for slots, the jobs and
 the baseline reruns. When the time runs out lanq prints `[lanq] plan_timeout: 60 min reached; stopping N started
 job(s)`, and then:
 - running jobs are stopped and cleaned up, and end `TimedOut` (124);
 - jobs waiting for a slot end `TimedOut`;
 - jobs not started yet are `Skipped` ("not started: plan_timeout reached");
 - unfinished baselines are `inconclusive`;
 - `jobs.jsonl` records the stopped jobs as `TimedOut`, never `Cancelled`.

 The plan is `TimedOut` (124) unless a `Failed` or `Rejected` job decides it, also when nothing was running (between
 `after:` waves, or with every job waiting). A job's own `timeout:` still applies, and Ctrl+C before the limit still
 ends the plan `Cancelled` (130). `--json` adds the conditional `planTimeoutMinutes` and `planTimedOut: true`
 (whenever the limit came due before the plan finished its work, a `--fail-fast` hold included; not when it came
 only during the last cleanup). The dry run shows the limit on a `Timeout:` line and warns when history's expected
 critical path is longer.
 `--plan-timeout` without `--plan` is refused (exit 2). The `fix_code` step says where to look and that raising
 the limit is the developer's decision. It never suggests a command.
- **Narrowing a plan from the command line.** `--on`, `--size` and `--min-size` now work with `--plan`, where they
 were refused before. They narrow every selected job and never widen one:
 - a job's own `on:` is intersected with `--on`, or `--on` applies alone when the job has none;
 - its size classes are intersected with the command line's.

 The dry run prints each job's narrowed `lanq run` line. An unknown `--on` name is refused before any network (exit
 2). A job the narrowing leaves with no machine ends the plan before the snapshot, with nothing sent: `NoCapacity`
 (75, `retryable: false`), for example "--on big-01 leaves job 'unit-windows' no machine (its on: [micro-01])". Its
 `nextSteps` are `ask_developer`, then `fix_command`: the same command with `--only` set to the jobs that can still
 run, leaving out every job that starts after a narrowed-out job (directly or not), so no job runs without its
 prerequisite. That `--only` replaces any `--only` given, the narrowing is kept, and the step is not safe to run
 unattended (its dry run is). Without these options a plan behaves
 exactly as before.
- **Plan fetch limits and folder.** `lanq.yml` gains `fetch_max` and `fetch_max_files`, on a job or in `defaults:`
 (where they apply to the jobs that fetch). They are `--fetch-max` and `--fetch-max-files`, and **may only lower** the
 200 MB / 500-file defaults: a larger value is refused (exit 2) with "lanq.yml may lower fetch limits (at most 200M /
 500 files); a larger limit is the developer's choice: lanq run --plan --fetch-max 1G". `fetch_dir` is not a
 `lanq.yml` key: it is refused with a hint to `--fetch-dir`. With `--plan`, the developer's `--fetch-dir`,
 `--fetch-max` and `--fetch-max-files` (refused with `--plan` before) apply to every selected job that fetches. They
 replace the file's values, up to the 2 GB / 5,000-file ceiling, and are refused when no selected job fetches. There
 is no plan-wide total: at worst a plan writes the fetching jobs times the per-job limit (6.4 GB for 32 jobs at the
 defaults).
- **`lanq stats` by plan job.** Plan jobs in `jobs.jsonl` now carry `planFile`, the plan file's full local path (`v`
 stays 2). `lanq stats` groups plan jobs by plan file and job name, with one run per plan run:
 - completed when all N shards were recorded and each one's last attempt completed (a shard that `--fail-fast` or
   Ctrl+C cancelled leaves no record, so such a run is other);
 - failed when any failed;
 - other otherwise.

 The wall time runs from the first start to the last end. `--json` always carries `planJobs` (`planFile`, `job`,
 `runs`, `completed`, `failed`, `other`, `medianSeconds`, `p90Seconds`, `lastRunUtc`, `lastShards`). It is capped at
 500 like `commands`, with the conditional `planJobsMore`. The text adds a "Plan jobs" table. Records written before
 0.10.0 group under `planFile: null`. Clones of one repository in different folders count separately; on Windows a
 path that differs only in case is the same plan file. Baseline reruns are left out.

### For coding agents

- An agent may narrow a plan with `--on`/`--size`/`--min-size`. The suggested `fix_command` rerun after a narrowing
 leaves jobs out, so it is never `safeToRunUnattended` (only its dry run is): the agent asks the developer before
 running it, and then reports the jobs it left out. It never edits `lanq.yml` (`on:`, `size:`, `min_size:`) to widen
 a job.
- A plan with `planTimedOut: true` is reported with where it was slow. Raising `--plan-timeout` or `plan_timeout:` is
 the developer's decision, never a way to make a plan pass.
- An agent never raises `--fetch-max` or `--fetch-max-files`, never adds `fetch_max` to `lanq.yml` and never picks a
 `--fetch-dir` the developer did not name to get files through. It reports `fetchSkipped` instead.

### Project

- `scripts/smoke-workers.ps1` scenario 8 now runs on a 0.10 binary (an older one is N/A):
 - `--plan-timeout 1` must end a plan `TimedOut` (124), with its job cleaned up;
 - `--plan --on` must put every job on the machine named;
 - a narrowing that leaves a job no machine must be `NoCapacity` (75, `retryable: false`) with a rerun `--only`.

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