From 5bb41cecefe87420fc0ec4efa9e466c60be6fc2b Mon Sep 17 00:00:00 2001 From: teknium1 <127238744+teknium1@users.noreply.github.com> Date: Fri, 18 Sep 2026 04:33:44 -0700 Subject: [PATCH] fix(desktop): name the REST hide path in the hide-sweep comments The sweep and bot-state comments still said room member sessions are hidden through a core session.set_hidden RPC; the code hides them through the source primary's REST PATCH /api/sessions/{id} via host.setPersistedSessionHidden (a 404 prunes the seat). Comment-only. --- apps/desktop/src/plugins/hermes-bots/bot-state.ts | 2 +- apps/desktop/src/plugins/hermes-bots/session-sweep.ts | 5 +++-- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/apps/desktop/src/plugins/hermes-bots/bot-state.ts b/apps/desktop/src/plugins/hermes-bots/bot-state.ts index a478189ff8..a3000c4a0e 100644 --- a/apps/desktop/src/plugins/hermes-bots/bot-state.ts +++ b/apps/desktop/src/plugins/hermes-bots/bot-state.ts @@ -23,7 +23,7 @@ export const rosterWatermarks = new Map() // sessions are room plumbing — neither is a scratch conversation, and a // 6-member room would otherwise dump six identical "Group: ..." rows into // recents. Backed by the core generic `hidden` session flag (session.create -// hidden:true / session.set_hidden). Older gateways ignore the flag and the +// hidden:true / REST PATCH /api/sessions/{id}). Older gateways ignore the flag and the // sessions simply stay visible there. /** Bot the Routines tile is scoped to. Follows the live gateway profile diff --git a/apps/desktop/src/plugins/hermes-bots/session-sweep.ts b/apps/desktop/src/plugins/hermes-bots/session-sweep.ts index 0f032bc5e7..7f29f0ab1a 100644 --- a/apps/desktop/src/plugins/hermes-bots/session-sweep.ts +++ b/apps/desktop/src/plugins/hermes-bots/session-sweep.ts @@ -24,8 +24,9 @@ interface HideSweepContext { /** One-time reconciliation: Bot Mode sessions are always hidden, but rooms * and Bot Chats created before this policy (or while the old pref was off) * left visible rows behind. On every plugin load, sweep the session ids we - * own by id (each group room's member sessions) through the core - * session.set_hidden RPC, then run the TITLE-based ownership sweep for + * own by id (each group room's member sessions) through the source + * primary's REST PATCH /api/sessions/{id} (a 404 prunes the seat), then + * run the TITLE-based ownership sweep for * everything else — canonical Bot Chats are identified by name (the * registry row titled "Bot Chat"), so the title sweep is what hides them; * no stored-id pointer is consulted. Idempotent (the DB setter is a no-op