# Lane nudge: lanes that go quiet A lane can stop without failing. Its last job ends, the agent reports once and waits at the prompt, and nothing is set to wake it. `rh lanes cadence` notices, but only on the lane's delivery window (often a day), and only if something runs it. A check that nobody delivers is just prose. `harness/tools/lane-nudge/lane-nudge` delivers it. Run it every 30 minutes. For each tmux session named `PREFIX + owner_session`, it types one resume prompt into the pane when all of these hold: - the session's last real turn (a user or assistant message in its Claude Code transcript) is at least `--idle-min` minutes old (default 60); - the pane shows no running shell or agent; - `rh lanes cadence` reports WARN, STALLED or BROKEN for the lane, or the session has simply been idle that long; - the lane wasn't nudged in the last `--reask` seconds (default 2 hours). Lanes marked EXEMPT or UNCONFIGURED by cadence are never nudged, and neither are sessions in `--skip` (finished challenges, on-demand sessions, the conductor). `--dry` prints the decisions without typing. Lifecycle data lives in `RH_LANE_REGISTRY`, default `/REGISTRY.json` (`--lanes` for lane-nudge; `LAUNCH_LANE_ROOT/lanes`, then `LAUNCH_IDEA_ROOT/lanes`, then `RH_ROOT/lanes`, then `.runtime/lanes` for the repo launcher; `RH_ROOT/lanes` or `~/.local/share/research-harness/lanes` for the conductor tools). For example, `{"lanes":{"example":{"status":"retired","since":"2026-01-09","why":"owner closed the challenge","sessions":["example","exampleb"],"end":"2026-01-31"}}}`. Stored statuses are `active`, `retired` and `held`; an optional `end` is inclusive in the local calendar, so a lane becomes `ended` the following day regardless of its stored status. Lane-nudge logs and skips retired, ended and held lanes and all their session aliases before inspecting idle time or job outputs, even with no skip list or a failed cadence read. The repo launcher refuses their jobs (including resumes) before host checks or registration; hyphenated lane names and registered session aliases resolve to the same lane. `asks-waiting` and the conductor relay hooks keep retired and ended asks/reports under `retired`, with the reason, without demanding a reply or relay; held lanes can still need a decision. A missing default registry leaves unregistered lanes active; an explicitly configured missing file or malformed registry is an error. Put the same data on each host or point each consumer at the shared registry; no scheduler skip list is needed for retirement. A renamed lane can retain its old name as a directory symlink, such as `bio -> open-source`. Harness lane listings count only real directories; commands accept either name and write to the canonical lane's ledgers. Dangling aliases are reported and skipped when listing lanes. In the registry, put `"aliases": ["bio"]` on the `open-source` entry so session names, job prefixes and retirement reasons use the same canonical lane. Aliases and sessions cannot belong to different entries. Existing ledger records retain their original labels. ```sh harness/tools/lane-nudge/lane-nudge --skip conductor,on-demand-lane --dry # cron: */30 * * * * /path/to/lane-nudge --skip conductor ``` Where it sits in the enforcement ladder (architecture > compiler > CI/lint > bot rules > prose): the "lanes never stop" rule used to be prose in each lane's instructions, plus a lint the operator had to remember to run. This moves it into a scheduled script that acts. The prompt is plain text in the pane, so the agent still decides what to do next; the script never chooses work for it. Idle is never the transcript's mtime. From 11-08 to 11-11 every lane slept: Claude Code's idle compaction and the session metadata it rewrites while idle touched each transcript about hourly, so no pane ever looked idle and nothing was nudged for three days. Compaction boundary and summary rows, meta rows and untimestamped metadata rows are skipped; a peer message or a task notification is a real turn. Each Mac that hosts lane sessions runs its own copy against its own tmux. Under launchd pass `--tmux` (or `TMUX_BIN`) and `--rh` as full paths; `--log` (or `LANE_NUDGE_LOG`) appends each nudge to a file. Limits: it only sees tmux-hosted Claude Code sessions, and it detects "running" from the pane's status line, which can change between Claude Code versions. Tests: `tests/test_lane_nudge.py`. A cadence read that fails is never read as all clear. If `rh lanes cadence` cannot run or prints no JSON, lane-nudge prints `CADENCE READ FAILED`, runs `--alert COMMAND` (or `LANE_NUDGE_ALERT`) with the message once per failure streak and again on recovery, and still nudges quiet lanes, as "cadence unknown". One installation called a bare `rh` from launchd, whose PATH did not include it; every read failed for eight hours and every lane read as fine. Pass `--rh` (or `RH_BIN`) as a full path when a scheduler runs it. A paused lane has one place for its pause: `lanes//HOLD`, whose first line says who paused it and why. `tools/launch.sh` refuses the lane's jobs, `rh sweep --all` skips it, `rh lanes cadence` reports it HELD rather than STALLED, and lane-nudge leaves it alone. Only the conductor removes it. friends, 11-11: paused by its owner, and still nudged twice to start the next round. A result that lands while a lane waits is a nudge of its own. With `--outputs` (globs of finished-job files such as `_codex/{lane}_*.last.md`, `{lane}` filled in), a file newer than the session's last real turn and at least 15 minutes old wakes the lane even though a watcher shell is running, once per file, with a message that names the file and asks it to fix the watcher rule that missed it. math, 11-12: its review finished at 16:18Z and it sat until 21:05Z, because the watcher it waited on watched other files and a running shell made the pane look busy. A lane waiting on a decision only the owner can make writes `lanes//BLOCKED`, with the decision and where it was sent on the first line, and deletes it when answered. While it is under 12 hours old the idle nudge stays quiet (a job result landing still wakes the lane); after that it lapses, so a forgotten marker cannot silence a lane, and a lane still blocked rewrites it. friends, 11-13: seven owner-only decisions pending, every in-brief job done, and nudged three times in a night to keep working on something else. A pause the owner sets is HOLD, not BLOCKED.