poll

Input

Arguments: $ARGUMENTS

Task

biff is passive/pull. Incoming talk (invites + real-time messages) and /write mail are held on the biff server and surface by MUTATING the descriptions of the talk and read_messages tools. One command, three forms:

A. /biff:poll <duration> — start polling every <duration>

Trigger when $ARGUMENTS is a duration like 1m, 5m, 10m (parse the {N}m/{N}s interval the way /loop does).

1. Call mcp__plugin_biff_tty__set_poll_interval with interval set to <duration> — this sets the server-side poll cadence.
2. Schedule the recurring model check with a /loop job at the same cadence:
   • Call CronList; if any job's prompt field exactly matches /biff:poll, call CronDelete on it first (avoid duplicate loops).
   • Call CronCreate with:
     • cron: the interval as a cron expression (1m → */1 * * * *, 2m → */2 * * * *, 5m → */5 * * * *, 10m → */10 * * * *; sub-minute intervals use */1 * * * *, the 1-minute cron floor).
     • prompt: /biff:poll — the recurring job runs /biff:poll with NO argument (the no-arg check below). Do NOT put the duration in the loop body, or every fire would reschedule itself.
     • recurring: true
     • durable: true
3. Confirm what was set in one line: the poll interval, the loop job id from CronCreate, and the 7-day durable-loop expiry.
4. Then fall through and run one check now (section C).

B. /biff:poll n — stop polling

Trigger when $ARGUMENTS is n, off, or stop. Turn the server-side cadence off and remove the recurring model check.

1. Call mcp__plugin_biff_tty__set_poll_interval with interval set to n — this disables the server-side poll cadence.
2. Remove the recurring /loop job: call CronList; for any job whose prompt field exactly matches /biff:poll, call CronDelete on it.
3. Confirm in one line: polling disabled and the loop job removed. Do NOT fall through to a check.