# HarnessLink 17.12.0 release notes

2 changes, released Nov 8, 2026.

### Added

- **Delegation never blocks the caller (ADR-87).** `delegate` runs are supervised by the HarnessLink service and keep going when the calling session ends. Past the machine's capacity they wait in a queue (`status: "queued"`, `position`) and start in order as slots free, instead of being refused. Capacity is `delegate.maxConcurrent`, or adapts to the machine: one per CPU and per GiB of reclaimable memory past a 1 GiB reserve, 1 to 8. `delegate` takes `wait: false` to return the run id at once, and each result is shown once at the start of the caller's next turn (the Claude Code and Codex prompt hook, the omp and pi extensions); `delegate_status` with no `run_id` lists your session's runs. `hnl run --detach` queues a run in the service and `hnl run --list` shows every run on the machine. On Linux under systemd each delegated harness runs in its own user scope, outside the service's memory limit. When no service accepts the connection, and always on Windows (the service takes no delegations there because another local user could claim its named pipe and receive your environment), delegation runs in the caller's relay as before and says so; a service that accepted the request but did not answer may have queued it, so the run is never started a second time. `hnl run --detach` is not available on Windows. The service watchdog no longer counts or kills delegated harnesses.
- **Infinity Code is a supported harness (ADR-87).** `hnl cloud harnesses enable infinity` captures the prompts you type in Infinity Code (`infinity`), uploads each session's thread moments after it changes with spawned child threads as sub-agents, banks every finished turn into memory, and registers HarnessLink's memory tools as the `hnl` MCP server in `~/.infinity/rap.json` (`disable` removes only that entry). `hnl resume` reconnects with `infinity --session <id>`. With the community `infinity-provider-models-dev` provider on an Anthropic API key, `hnl gateway connect infinity` routes its model calls through the gateway (run `infinity daemon restart` afterwards) and `disconnect` restores the provider's command exactly; Bedrock traffic is not routed. Infinity keeps no prompt times, so a prompt is timed when HarnessLink first reads it. Infinity Code has no hooks, tool-permission hook, skills folder or one-shot answer mode, so context hooks, org policy rules, `hnl add` skills and `delegate` don't apply to it.

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.12.1](https://harnesslink.sh/releases#v17.12.1) · [Older: 17.11.0](https://harnesslink.sh/releases/17.11.0) · [All releases](https://harnesslink.sh/releases) · [Atom feed](https://harnesslink.sh/releases.atom)
