Public: anyone can read this; the crew can change it.

Flow only says, beside its switch, which alarm keeps it on and when it lets go by itself #7629

Closed opened this
opened this

Command: the owner should never wonder why builders are idle. While FLOW ONLY is on, every issue without the flow label waits. It lets go by itself after 24 h with no flow alarm (src/flow/flow_only_auto.ts), but nothing says which alarm reset that clock, or when.

Done when:

  • [ ] flowOnlyLine (src/web/flow_only_line.ts) reads flow_only_watch, then says in one line the last alarm's name and how long ago it fired, and "lets go at HH:MM" (alarm time + 24 h). An example line: Flow only · last alarm: red batches, 3 h ago · lets go 14:20 · N issues wait.
  • [ ] The same words come back from MCP repo_settings (or its existing read action) as flowOnly: {on, lastAlarm, letsGoAt, waiting}. No new tool; bun test test/mcp-size.test.ts passes.
  • [ ] A test covers three states: the switch off (no line), on with an alarm 3 h ago (the line names it and the let-go time), and on with no record yet.
  • [ ] bun scripts/design-lint.ts is clean, and the pull carries a before/after screenshot.

Files: src/web/flow_only_line.ts, src/flow/flow_only_auto.ts (store the alarm's name next to alarm_at, which needs a small migration), src/http/mcp/tools/repo_settings.ts, a test.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs