You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Planning (ADR-0008): settings still own Director on/off and the inspectable
Character Prompt. They do not own a fixed wake-frequency slider. Ambient session
wakes back off and stay off while the display is asleep; a user may disable
ambient wakes or the Director entirely.
Reduced from this scope: launch at login and auto-update wait on a packaged
build (#132) and now live as #199 and #200. Tray and settings stay here.
Why
The sprite is not a reliable way to reach configuration.
Scope
Tray or menu bar icon reaching settings and quit.
Settings: character selection, Instance management, Director on/off, whether
ambient session wakes are allowed, the inspectable Director payload, Memory
location, edit and wipe, excluded applications, hide-rule toggles, hotkey
binding.
WindowPet's tray code is MIT and can be lifted. Record the attribution.
Acceptance criteria
Settings is reachable without finding the sprite.
The Director payload panel shows the last user turn (what SPEC inspects).
Ambient wakes can be disabled without turning the whole Director off, or the
Director can be turned off and Static weights keep the life.
Memory can be opened in an external editor and wiped from settings.
Tests
Manual.
Spec: docs/SPEC.md · ADR-0008 · migrated from docs/issues/0018-shell-tray-settings.md
The tray menu defined here is now also the sprite's right-click menu. #6 was updated to
say so: one definition, two entry points, so the two cannot drift apart.
Nothing changes in this issue's scope — it already owns the menu. What changes is that
the Menu verb in #6 lands when this does, rather than separately. The other four
verbs (Grab, Throw, Poke, Summon) do not wait on it.
Worth knowing when sequencing: this issue depends on #12 and #13, so right-clicking the
sprite is further out than dragging it.
The Hide rules submenu needs a Do Not Disturb toggle, and it is ai-buddy's own.
Oded's call, made while reviewing #83: "if we can't access the OS's DND, let's make our own. It should be something we can select in some menu (right click on the character, or on the app icon)."
#83 built a Do Not Disturb hide rule and could not read the condition — macOS keeps live Focus state behind Full Disk Access or a consent dialog, and DESIGN.md decision 9 forbids the Spatial Layer from spending a permission. Rather than descope the rule, it becomes a mode the user sets here. Recorded on #12.
So the menu sketch in this issue gains one entry:
Characters ▸
Instances ▸
Director [on]
Hide rules ▸
Do Not Disturb [off]
Hotkey…
────────────────────────
Memory…
Settings…
Quit ai-buddy
Three constraints this inherits rather than invents:
One definition, two entry points. This issue already owns that: right-clicking the Character (The five interaction verbs #6's Menu verb) and clicking the tray icon open the same menu, so the toggle cannot drift between them.
It must persist across launches. A quiet mode that forgets itself on restart is worse than no quiet mode. The settings surface in this issue's scope is where that lives.
It is checkable state, not a command. The menu has to show whether it is on, the way Director [on] does.
This is the only thing standing between #83's rule and it doing something. Until this lands, Desktop::do_not_disturb is set by nothing and the hotkey is the only way to put the Character away.
One decision left open
As #83 built it, ai-buddy's Do Not Disturb and the hide hotkey do the same thing — both take the Character off screen and both outlast the desktop. If Do Not Disturb is instead meant to be quiet rather than gone (no dialogue, no Director proposals, still on screen), that is a different rule, and it is what user story 27 at docs/SPEC.md:120 actually asks for. Worth settling before the menu entry is written, because the label and the submenu it belongs under both depend on the answer.
Correcting my comment above: that is two menu entries, not one. Oded split the mode in half.
"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 Do Not Disturb is no longer a hide rule and does not belong under Hide rules ▸. It is the buddy staying on screen and not starting anything — filed as #84. Hiding is the other mode, and this menu needs it too, because the hotkey is currently the only way to reach it.
Characters ▸
Instances ▸
Director [on]
Do Not Disturb [off] ← #84: stays on screen, stops initiating
Go away ← #12: off screen now, same as the hotkey
Hide rules ▸
Hide in fullscreen apps [on]
Hotkey…
────────────────────────
Memory…
Settings…
Quit ai-buddy
Three things that follow from the split:
Both persist across launches. A quiet mode that forgets itself on restart is worse than no quiet mode, and a buddy that comes back on its own after you sent it away is the behaviour Take the Character off screen when it is in the way #83 already went out of its way to prevent.
"Go away" is a toggle, so the entry has to say which way it is pointing. It is the same state the hotkey flips, so the menu and the hotkey read and write one flag or they will disagree. Whether it reads better as Go away / Come back or as a checkable Hidden [off] is a wording call, not a mechanism one.
Do Not Disturb is checkable state, like Director [on]. It is a mode, not a command.
The label for the second one is Oded's to pick — "go away or something similar". Go away is used above because it is what he said, not because it was chosen.
Still true from the comment above
One definition, two entry points: right-clicking the Character (#6's Menu verb) and the tray icon open the same menu, so neither toggle can drift between them. That is already this issue's scope.
Reopening.#190 used Closes #18, but this issue’s acceptance is not fully met, and the leftover is still this ticket’s job (with packaging and platform follow-ups already filed).
No new implementation in this comment. Close again only when the acceptance above is honest on main (or leftover is clearly moved to those follow-ups and this parent is intentionally retired).
Tray and settings landed in #190. Launch at login and auto-update were reduced out of this issue — they need a signed bundle and a release channel from #132, so they now live in #199 and #200.
Closing as done for the remaining tray/settings scope.
Activity
Migrate v1 issues from markdown to GitHub Issues
Drop scaffolding the overlay never used
omesser commentedon Aug 29, 2026
The tray menu defined here is now also the sprite's right-click menu. #6 was updated to
say so: one definition, two entry points, so the two cannot drift apart.
Nothing changes in this issue's scope — it already owns the menu. What changes is that
the Menu verb in #6 lands when this does, rather than separately. The other four
verbs (Grab, Throw, Poke, Summon) do not wait on it.
Worth knowing when sequencing: this issue depends on #12 and #13, so right-clicking the
sprite is further out than dragging it.
Start the Character you name, not the first one
Meet Chip first, whatever sorts first
omesser commentedon Aug 30, 2026
The Hide rules submenu needs a Do Not Disturb toggle, and it is ai-buddy's own.
Oded's call, made while reviewing #83: "if we can't access the OS's DND, let's make our own. It should be something we can select in some menu (right click on the character, or on the app icon)."
#83 built a Do Not Disturb hide rule and could not read the condition — macOS keeps live Focus state behind Full Disk Access or a consent dialog, and DESIGN.md decision 9 forbids the Spatial Layer from spending a permission. Rather than descope the rule, it becomes a mode the user sets here. Recorded on #12.
So the menu sketch in this issue gains one entry:
Three constraints this inherits rather than invents:
Director [on]does.This is the only thing standing between #83's rule and it doing something. Until this lands,
Desktop::do_not_disturbis set by nothing and the hotkey is the only way to put the Character away.One decision left open
As #83 built it, ai-buddy's Do Not Disturb and the hide hotkey do the same thing — both take the Character off screen and both outlast the desktop. If Do Not Disturb is instead meant to be quiet rather than gone (no dialogue, no Director proposals, still on screen), that is a different rule, and it is what user story 27 at
docs/SPEC.md:120actually asks for. Worth settling before the menu entry is written, because the label and the submenu it belongs under both depend on the answer.omesser commentedon Aug 30, 2026
Correcting my comment above: that is two menu entries, not one. Oded split the mode in half.
So Do Not Disturb is no longer a hide rule and does not belong under
Hide rules ▸. It is the buddy staying on screen and not starting anything — filed as #84. Hiding is the other mode, and this menu needs it too, because the hotkey is currently the only way to reach it.Three things that follow from the split:
Go away/Come backor as a checkableHidden [off]is a wording call, not a mechanism one.Director [on]. It is a mode, not a command.The label for the second one is Oded's to pick — "go away or something similar".
Go awayis used above because it is what he said, not because it was chosen.Still true from the comment above
One definition, two entry points: right-clicking the Character (#6's Menu verb) and the tray icon open the same menu, so neither toggle can drift between them. That is already this issue's scope.
Leave being quiet to a mode that is not hiding
Start the Character you name, not the first one
Meet Chip first, whatever sorts first
feat(shell): Run several Character Instances at once
feat(menu): implement context menu on right-click (#155)
feat(shell): Tray, settings, launch at login, and updates (#18)
docs: Add the shared menu grab for the #18 review
docs: Add the settings window grab for the #18 review
feat(shell): Tray, settings, launch at login, and updates (#18) (#190)
omesser commentedon Sep 2, 2026
Issue hygiene after #190 (merged to main)
Reopening. #190 used
Closes #18, but this issue’s acceptance is not fully met, and the leftover is still this ticket’s job (with packaging and platform follow-ups already filed).On main via #190 (macOS)
Still open against this issue’s acceptance
show_settingsstub elsewhere; follow-ups already open: #193, #194, #195, #196, #197, #198No new implementation in this comment. Close again only when the acceptance above is honest on main (or leftover is clearly moved to those follow-ups and this parent is intentionally retired).
[-]Tray, settings, autostart, updater[/-][+]Tray, settings[/+]omesser commentedon Sep 2, 2026
Tray and settings landed in #190. Launch at login and auto-update were reduced out of this issue — they need a signed bundle and a release channel from #132, so they now live in #199 and #200.
Closing as done for the remaining tray/settings scope.
[-]Tray, settings[/-][+]Tray and settings[/+]