Added
- Delegation never blocks the caller (ADR-87).
delegateruns 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 isdelegate.maxConcurrent, or adapts to the machine: one per CPU and per GiB of reclaimable memory past a 1 GiB reserve, 1 to 8.delegatetakeswait: falseto 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_statuswith norun_idlists your session's runs.hnl run --detachqueues a run in the service andhnl run --listshows 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 --detachis 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 infinitycaptures 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 thehnlMCP server in~/.infinity/rap.json(disableremoves only that entry).hnl resumereconnects withinfinity --session <id>. With the communityinfinity-provider-models-devprovider on an Anthropic API key,hnl gateway connect infinityroutes its model calls through the gateway (runinfinity daemon restartafterwards) anddisconnectrestores 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 addskills anddelegatedon't apply to it.