auto.relay70 Automations doff Contact Request

automations

Tools that keep long work moving.

This is where the automation tools built here get published. Each one is small, runs on your own machine, and does a job nobody should have to sit and watch. One is ready to show. More are on the way.

Request access See what doff does

The catalogue

Numbered as they ship. Empty slots are not decoration.

01 · doff

private testing

A session supervisor. It answers blocking prompts and nudges stalled agent sessions back into motion, across iTerm, any terminal, and the desktop app — without you watching the window.

How it works →

02

in the workshop

Being built and used daily before it goes anywhere near a release.

01 · doff

Session supervisor · macOS · command line, with a local dashboard

Long agent runs do not fail loudly. They stop on a confirmation prompt, or on a question nobody is in the room to answer, and then sit there. doff sweeps the sessions on your machine, works out which ones are genuinely stuck rather than merely quiet, answers what it can, and logs every decision it made on your behalf.

  • Sweeps in about 0.4 seconds; runs once, or on a loop until you stop it.
  • Reads a session with text in the composer as a person typing, not as idle.
  • Records the full question, every option offered, and what it chose, to a JSONL log.
  • An idle window bounds what it will touch, and warns when that window gets wide.
  • A local dashboard on a random port, bound to localhost, behind a one-time token.
  • Quits by itself when the machine has nothing left to supervise.

Request access

doff 
$ doff once
desktop 1/96 within 10m · iterm 3/4 live · 0.4s

→ local_9f2c…  blocked, 4m
   "Do you want to create tests/run_suite.py?"
   answered: Yes

→ iterm:sonolyst  idle, 21m
   nudged

$ doff run
watching · interval 30s · quits after 10m idle
status

macOS only. Built for Claude Code running in iTerm2, with a second leg for the desktop app. Tested against Claude Code 2.1.233 and desktop app 1.30096.5 — a desktop build can move the accessibility surface that leg depends on, so the versions are stated rather than implied. Distribution is a one-line install when testing finishes; until then, access is by request.

Ask for something

Access to what is here, a job you want automated, or a bug in something you are already running. All three go to the same place and get read.

Request access Suggest an automation