Skip to content

Do Not Disturb: the buddy stays, and stops starting things #84

Closed

Description

@omesser

Depends on: #10, #18

Why

Do Not Disturb and hiding got conflated, and #83 built the wrong one. This separates them.

User story 27 in docs/SPEC.md says "I want the buddy to respect Do Not Disturb, so that it is quiet when I have said I want quiet." Quiet, not gone. A buddy that vanishes is already covered by the hotkey and by the fullscreen rule; what nothing covers is a buddy that stays on your screen and stops talking to you.

Oded's call, settling it on #83: "let's distinguish 'do not disturb' — which should make it go to sleep or suspend other interactions which in the future it may initiate — from 'go away' or something similar, which would make it visually disappear."

So there are two modes and they are not the same mode:

Do Not Disturb Go away
On screen Yes No
Initiates anything No —
Responds when you poke it Yes —
Owned by This issue #12, and the hotkey already does it

Scope

Do Not Disturb is a mode the user turns on, and it suppresses everything the buddy starts on its own:

  • No Director proposals. The Director is not woken, or its proposals are refused before they reach the Engine. Whichever is cheaper — the Engine already refuses proposals it does not recognise.
  • No dialogue the buddy started. Poke's react is a response to the user and stays; anything the buddy says unprompted does not.
  • Idle Behaviors quieten. The buddy settles rather than pacing — sleeping is the obvious reading of "go to sleep" in the decision above, but a still, awake buddy may read better. Worth trying both before choosing.

What it does not do:

  • It does not hide the Character. That is the hotkey and Hide rules and z-order #12's fullscreen rule.
  • It does not stop the user reaching the buddy. Grab, Throw, Poke and the menu all still work — the user initiating is the whole point of the exception.
  • It does not read macOS Focus state. See below.

The mode is set from the menu (#18) and persists across launches.

Why it is ai-buddy's own, not the OS's

#83 tried to read the desktop's Do Not Disturb and could not. macOS keeps live Focus state behind ~/Library/DoNotDisturb/DB/, which needs Full Disk Access, or INFocusStatusCenter, which opens a consent dialog on first ask — and DESIGN.md decision 9 forbids the Spatial Layer from spending a permission. The old com.apple.notificationcenterui key no longer exists on this OS.

Reading the OS switch is a possible v2 upgrade once something else in the product has already bought Full Disk Access. Until then the mode is ours, which also makes it work the same on every platform.

Acceptance criteria

  • Turning Do Not Disturb on leaves the Character on screen.
  • No Director proposal is applied while it is on.
  • The buddy says nothing unprompted while it is on.
  • Poke, Grab and Throw still work, and Poke still plays react.
  • Turning it off resumes proposals without a restart.
  • The setting survives a relaunch.

Tests

Engine tests with a fake Director: a proposal offered under Do Not Disturb is not applied, and the same proposal is applied once it is off. The verbs-still-work cases are Engine tests too. The menu entry and persistence are manual.

What moves out of #12

#12's hide rules keep the fullscreen condition and the hotkey. Desktop::do_not_disturb and its arm in hides() come out of #83 — Do Not Disturb is no longer a visibility rule at all. DESIGN.md:226 lists it among the hide conditions and needs correcting.

Activity

  1. omesser commented on Sep 2, 2026

    @omesser
    OwnerAuthor

    Sit, not sleep.

    This issue left idle quieten open: sleeping was the obvious reading of "go to sleep", but a still, awake Character might read better. The remaining gap after proposals were refused was a walk already under way — walk velocity outlives the Primitive that started it, so the Character kept pacing.

    #204 sits the Character down when Do Not Disturb turns on. Sleep-after-idle is unchanged. Poke, Grab, and Throw still work.

  2. added this to the V1 milestone on Sep 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions