# HarnessLink 17.19.0 release notes

7 changes, released Nov 13, 2026.

### Added

- `hnl uninstall` — undoes exactly what installing did: stops and removes the background service, puts every harness config back as it was (hooks, MCP entries, gateway base URLs), removes system-level managed settings, and deletes the `hnl` command and its PATH shim. Prints the plan first and asks; `--dry-run`, `--yes`, `--purge` (`--purge` deletes `~/.hnl` behind its own confirmation). Running it twice is a no-op.
- `hnl prune` now covers everything HarnessLink leaves behind, by category: payloads for other machines, update leftovers, logs, config backups, caches and the source maps in the packages it installs. `--only <category>` narrows it, `--dry-run` lists, `--yes` deletes; your sessions, memories and databases are named as untouchable and never selected. The same sweep runs automatically after installs and updates and once after the service starts, and `hnl doctor` reports and fixes a category over its bound (ADR-100).

### Fixed

- The installers leave nothing behind when they fail or are interrupted: every scratch path in `install.sh` is registered and removed on EXIT/INT/TERM/HUP (a SIGTERM mid-verify used to leave a file in $TMPDIR), `install.ps1` removes its scratch directory in a `finally`, and the release manifest is copied then renamed so an interrupted copy cannot leave a half manifest.
- Uninstalling a context hook no longer leaves an empty `hooks.json` or `extensions/` directory, and mcp.json writes end with a newline so a user's file round-trips unchanged.
- `~/.hnl/logs` is bounded as a directory, not per process: a machine that ran the CLI 470 times kept 470 files, most of them one line. Now 5 days, 40 files and 16 MB of finished runs, with the near-empty files a short-lived command leaves dropped the next day.
- Config backups no longer accumulate: a restore keeps the newest two of each file and removes the rest as it writes.
- A `code_map` index records its project root, so an index for a folder you deleted is dropped instead of waiting to age out.

Update HarnessLink and every installed harness to its current release:

hnl update

New machine? Install with:

curl -fsSL https://harnesslink.sh/install.sh | bash

[Newer: 17.20.0](https://harnesslink.sh/releases/17.20.0) · [Older: 17.18.0](https://harnesslink.sh/releases/17.18.0) · [All releases](https://harnesslink.sh/releases) · [Atom feed](https://harnesslink.sh/releases.atom)
