Skip to content

Proactive reminders 1/3 follow-up: quiet hours, mute, waiting-too-long #469

Closed

Description

@Birfy

Follow-up to #353 (Proactive reminders 1/3). The first slice (owner decision 2026-10-20, option a) adds system notifications when my own Bots finish or fail a turn, next to the existing approval-waiting one, with one Notifications switch in Settings → General (on by default). These parts of #353 were deferred and are tracked here:

Deferred from #353

Needs the owner

Which of these come next and in what order, and the "waiting too long" threshold.

Links: #353, #349.

Activity

  1. added
    enhancementNew feature or request
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    area:uiWeb/desktop UI and copy
    area:automationScheduled tasks and automation
    on Oct 20, 2026
  2. Birfy commented on Oct 20, 2026

    @Birfy
    CollaboratorAuthor

    Maintenance triage (2026-10-20 09:56 Asia/Shanghai, main 465357e): still needs-human; no design conflict found. Question for the owner: what comes next after #353 slice 1 (PR #470)?

  3. Birfy commented on Oct 20, 2026

    @Birfy
    CollaboratorAuthor

    Owner decision (2026-10-20): option (a) as recommended — waiting-too-long approval reminder (default 15 min), per-type toggles for waiting/finished/failed notifications, coalesce duplicate notifications per chat. Quiet hours, mute, in-app notification list come later; friend/team notifications wait for #51.

  4. added
    agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a template
    agent-workingAn agent has claimed this issue (the claim comment names the branch)
    and removed
    needs-humanThe agent loop stopped; a person must decide (reason in the last comment)
    on Oct 20, 2026
  5. self-assigned this
    on Oct 20, 2026
  6. Birfy commented on Oct 20, 2026

    @Birfy
    CollaboratorAuthor

    Claimed by maintenance run (2026-10-20 11:55 Asia/Shanghai, main a7adfe0): developing on branch feat/469-waiting-reminder-toggles in Birfy/FlyBot, following the Owner decision above (first slice only).

  7. Birfy commented on Oct 20, 2026

    @Birfy
    CollaboratorAuthor

    Minor decisions made while implementing (PR #492, 2026-10-20 12:03 Asia/Shanghai):

    • The 15-min threshold is fixed for now (WAITING_TOO_LONG), no setting; one reminder per approval. For an approval that started before the window opened, the 15 min count from the window opening; the title shows the real minutes waited.
    • The reminder follows the Waiting for approval switch; there is no fourth switch.
    • The main Notifications switch stays; the three per-kind switches sit under it and are disabled while it is off. Only off values are saved (prefs.notify).
    • Collapse per chat: all notifications of one chat or group share one OS tag, so a newer one replaces the older (newest event's title), and the body counts the updates since the chat was last on screen or its notification clicked. The reminder of an approval already notified does not add to the count.
  8. added a commit that references this issue on Oct 20, 2026
    e974145
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

agent-readyMaintainer-approved spec: an agent may take it. Only maintainers set this; never in a templateagent-workingAn agent has claimed this issue (the claim comment names the branch)area:automationScheduled tasks and automationarea:uiWeb/desktop UI and copyenhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions